This is the technical reference for teams designing and deploying email signatures at scale. 50 atomic questions, each answered with the direct fact, the context behind it, and the cross-client behavior where it matters. Updated as client behaviors change. If a question you need is not answered here, send it to [email protected] and we will add it.
For centralized signature management across your team or organization, see SyncSignature for Teams. For technical deployment details, see the directory sync guide.
Sizing and dimensions
What is the maximum recommended length for an email signature line?
About 70 characters per line. Longer lines wrap awkwardly on mobile clients (which render at roughly 320 to 375 pixels wide) and break visual hierarchy on narrow message panes. Stick to 50 to 70 characters for body lines and shorter for the name and title lines. The 4-line baseline rule covers most professional cases: name, role plus company, contact information, optional disclaimer or call to action.
What is the maximum recommended height for an email signature in pixels?
About 200 pixels maximum total height. Above that, the signature pushes message content below the fold on desktop preview panes and becomes visually overwhelming on mobile. Most professional signatures land between 100 and 150 pixels. Reserve the full 200 only when an essential banner image or compliance-required disclaimer block needs the additional vertical space.
What is the maximum recommended file size for an email signature including images?
About 50 KB total signature weight is the safe target. Above 100 KB, signatures meaningfully slow loading on slow connections and contribute to Gmail clipping. Gmail clips messages over 102 KB and shows a "View entire message" link, which hurts open and click metrics. Optimize images aggressively before embedding and avoid large GIFs.
How wide should an email signature image be in pixels?
600 pixels is the standard maximum width for the full signature container. Most email clients render content within roughly a 600 pixel wrapper for desktop compatibility. Within that width, headshots typically run 80 to 120 pixels wide, logos 100 to 200 pixels wide, and banner images at the bottom can use the full 600 pixels. Author at 2x for Retina displays and let HTML width attributes scale down.
What aspect ratio works best for an email signature banner?
4:1 or 5:1 aspect ratios work best, which translates to dimensions like 600x150 or 600x120 pixels. Banners that are too tall, such as 3:1 or square, compete with message content for visual attention and feel like ad blocks. Wide-and-short banners read as branding and event reinforcement, not as a content interruption.
How many lines of text should a professional email signature contain?
4 to 7 lines is the practical range. Less than 4 lines reads as incomplete, often just name and email. More than 7 lines reads as cluttered and gets visually skipped. The 4-line baseline is name, title plus company, contact information, and optional disclaimer or CTA. Add lines for credentials, social links, or a banner only if they earn their visual weight.
What is the recommended pixel width for an email signature on mobile?
320 to 375 pixels is the rendered width on most mobile clients. Design at 600 pixels desktop width and let it scale down responsively. Use single-column layouts where possible. Two-column desktop signatures combining a headshot with text collapse to vertical stacking on mobile, which usually reads fine if image alignment is set correctly with align="left" on the headshot table cell.
How does signature width affect rendering on Outlook desktop vs Gmail web?
Outlook for Windows respects fixed pixel widths within roughly 600 pixels, while Gmail web is fluid within the message container. Setting <table width="600"> works in both clients but Outlook honors absolute pixel dimensions more strictly. Avoid percentage widths like width="100%" for signatures because Outlook for Windows will sometimes render them at the full window width, which breaks the layout.
Image specs and embedding
What image formats are supported in email signatures across major clients?
PNG and JPEG render universally. PNG-24 with transparency is the default for logos and headshots. JPEG is preferred for banners and photos at smaller file size. GIF, both static and animated, renders in most clients but plays only the first frame in Outlook for Windows. WebP and AVIF are not reliably supported. SVG is not reliably supported. Stick to PNG and JPEG for cross-client safety.
Should email signature images be inline or hosted externally?
Hosted externally via a CDN URL referenced through <img src="https://...">. Inline base64 images bloat email size dramatically and are stripped or flagged by some clients. Hosted images load on demand, keep email weight low, and let you update the image without editing every signature. Use HTTPS URLs and a stable CDN with high uptime.
What is the maximum recommended file size for a logo in an email signature?
About 10 to 20 KB per logo. PNG-24 with transparency typically lands in this range for a 200x60 logo. Compress with tools like TinyPNG or ImageOptim before embedding. Larger logo files waste signature weight without improving visual quality at the rendered display size.
Why do some email signature images appear as attachments in Outlook?
Outlook for Windows treats inline images with Content-Disposition: inline as either inline or attachment depending on rendering mode and recipient client behavior. Hosted images via <img src="https://..."> avoid this issue entirely. If you must embed, use Content-ID references and accept that some recipients see the image as both inline rendered and as an attachment in their attachment list.
How do animated GIFs render in email signatures across clients?
Animated GIFs play in Apple Mail, Gmail (web and mobile), iOS Mail, and Outlook on the web. They render only the first frame in Outlook for Windows 2007 and later, because Microsoft uses Word's rendering engine which does not animate GIFs. If you use animated GIFs, design them so the first frame stands alone meaningfully for the Outlook desktop audience.
Do SVG images work in email signatures?
No, not reliably. Gmail, Apple Mail, and most other clients strip SVG from message bodies for security reasons. Use PNG with appropriate dimensions for logos and icons. SVG support has not improved meaningfully in the last decade and is unlikely to become reliable for email use.
What DPI should email signature images be exported at?
Export at 2x the rendered display size to support Retina displays. An image authored at exactly the display size renders blurry on Retina screens. Author at 2x and let the HTML <img width> and <img height> attributes scale them down to display size. For example, render a 100x100 headshot at 200x200 pixels in the source file.
Font support
What fonts render reliably in email signatures across all major clients?
Arial, Helvetica, Georgia, Times New Roman, Verdana, Trebuchet MS, Tahoma, and Courier New. These are pre-installed on Windows, macOS, iOS, and Android. Custom web fonts from Google Fonts or Adobe Fonts do not load reliably in email. Use them only as the first option in a fallback stack with email-safe fonts as the fallback.
What is the email-safe font fallback stack?
font-family: Arial, Helvetica, sans-serif; for sans-serif text. font-family: Georgia, "Times New Roman", serif; for serif text. Always end with the generic family name (sans-serif, serif, or monospace). Custom fonts can be the first entry in the stack but the email-safe options must follow as fallbacks for Outlook for Windows and other strict clients.
Do custom web fonts work in email signatures?
Inconsistently. Apple Mail, iOS Mail, and some Outlook configurations honor <link> and @import web font requests. Gmail, Outlook for Windows, and Outlook on the web typically strip web font requests for security. Even when honored, font loading delay can cause visible flicker. Default to email-safe fonts and use custom fonts only as the first option in a fallback stack.
What is the recommended font size for email signature text?
12 to 14 pixels for body text. 14 to 16 pixels for the name. Below 11 pixels reads as fine print and is hard to scan on mobile. Above 16 pixels feels oversized in the message context. Use font-size in pixels rather than points (pt) for predictable cross-client rendering, since pixel sizing is honored more consistently.
How do email signature fonts render on iOS Mail vs Outlook for Windows?
iOS Mail respects the full CSS font specification including custom fonts loaded via @font-face, with some limitations. Outlook for Windows uses the Word rendering engine and ignores @font-face, falling back to the next entry in the font stack. Outlook for Windows also handles font weights inconsistently. Bold renders as bold but font-weight: 600 may not render the way you expect.
What is the smallest readable font size for an email signature footer?
10 to 11 pixels is the practical floor for legal disclaimers and footer text. Below 10 pixels, mobile rendering becomes hard to read and may trigger accessibility warnings. If the disclaimer must be longer than fits at 11 pixels, reduce the disclaimer text rather than the font size. Most regulatory requirements care about presence and clarity, not visual weight.
Deliverability impact
Do email signatures affect email deliverability?
Yes, marginally. Spam filters score messages on multiple factors including HTML complexity, image-to-text ratio, link count, and total weight. Heavy signatures with many images and tracking pixels can shift borderline messages into spam folders. Well-formed signatures with reasonable weight, modest image use, and clean HTML are not a primary deliverability factor for most senders.
Do large signature images trigger spam filters?
Total message size impacts spam scoring more than image size specifically. A 200 KB signature on every message contributes to a higher overall message weight and to a higher image-to-text ratio. Both increase spam score marginally. Keep signature image weight under 50 KB total and the image-to-text ratio below 60 percent for safer inbox placement.
How does HTML signature complexity affect inbox placement?
Heavily nested tables, inline styles, and complex layouts can increase spam scores in some filters. The Gmail clipping behavior at 102 KB shows the "View entire message" link, which negatively impacts open and click metrics even though it does not directly affect deliverability. Keep HTML lean: simple table structure, minimal inline CSS, no JavaScript, no embedded videos.
Do tracking pixels in email signatures affect deliverability?
Tracking pixels (1x1 transparent images that load from a tracking server) are a flagged pattern for some filters. Most mainstream filters do not block tracking pixels outright but assign a small spam score increase. Apple Mail Privacy Protection, introduced in 2021, preloads images server-side, which corrupts tracking pixel accuracy without affecting deliverability of the underlying message.
What is the SPF and DKIM impact of using a third-party signature deployment tool?
None for client-side stamping tools. SyncSignature writes signatures into Gmail or Outlook before send. The message originates from your normal mail server with your normal SPF, DKIM, and DMARC records. Server-side stamping tools like Exclaimer or Letsignit on certain plans route mail through their cloud, which requires SPF and DKIM record updates to authorize the third-party sender.
Does adding a banner image to every email signature increase the spam score?
Marginally. A 600x150 banner adds roughly 10 to 30 KB depending on optimization. Spam filters consider image-heavy messages slightly more spammy than text-heavy ones. If the banner is well-optimized and the signature is otherwise clean, the impact is negligible. If the banner pushes total signature weight above 100 KB, deliverability impact becomes meaningful.
Mobile rendering
How do email signatures render on Gmail mobile (iOS and Android)?
Gmail mobile honors most HTML and CSS used in signatures including images, fonts (with web font caveats), tables, and inline styles. Gmail mobile renders messages in a fluid container and scales fixed-width tables down to fit the viewport. Profile images and signatures both render at their intended sizes assuming the source HTML uses standard table-based layouts and inline styles.
How do email signatures render on Outlook mobile?
Outlook mobile (iOS and Android) uses the same Microsoft Office rendering engine as Outlook on the web. Web fonts, modern CSS, and image rendering all work in Outlook mobile. It is more permissive than Outlook for Windows desktop. Signatures designed to render correctly on Outlook desktop will also render correctly on Outlook mobile and Outlook on the web.
Why do email signatures appear differently on iOS Mail vs Gmail?
Different rendering engines. iOS Mail uses WebKit (the Safari engine). Gmail mobile uses Google's Gmail-specific renderer. iOS Mail typically honors more of the modern CSS specification. Gmail strips or modifies certain CSS properties for security and consistency reasons. Test signatures on both platforms before deploying widely, since edge cases like background images can differ noticeably.
Should mobile email signatures be different from desktop signatures?
Usually no. Design once at 600 pixel desktop width with single-column layouts and let responsive behavior handle mobile rendering. Some teams ship a shorter mobile signature with just name, title, and contact information, but maintaining two signatures per person doubles the management burden and benefits less than expected. A single well-designed signature works on both surfaces.
How does email client dark mode affect signature rendering?
Most clients invert background colors and adjust text colors automatically when dark mode is enabled. Signatures with hardcoded background colors, especially white or near-white, often render with the original background, creating a "stuck on white" effect against the dark message body. Use transparent backgrounds where possible and avoid hardcoded background colors on signature container elements.
What is the best practice for handling signature images in dark mode?
Use PNG with transparency for logos and graphics. White or light logos on transparent backgrounds disappear in dark mode, while black or dark logos disappear in light mode. Provide a logo with a subtle colored outline, a logo with a drop shadow, or use the @media (prefers-color-scheme: dark) CSS selector to swap a dark-mode variant. Dark mode media queries are honored by Apple Mail and some Outlook configurations.
Compliance and disclaimers
Where should the legal disclaimer appear in an email signature?
At the bottom, after all contact information and any banner. Disclaimers are typically rendered in a smaller font (10 to 11 pixels) with reduced visual weight (gray color, italic style, or thin font weight). The disclaimer should not compete visually with the active signature content. Most readers ignore well-styled disclaimers, which is the intended outcome for evidentiary disclaimers.
What is the recommended length for a confidentiality disclaimer in an email signature?
1 to 2 sentences for routine confidentiality. 3 to 4 sentences if multiple regulatory jurisdictions require explicit notice. Above 4 sentences, the disclaimer dominates the signature visually and recipients tune it out. Keep the language tight and link to a hosted full disclaimer page if more text is required for regulatory completeness.
Are email signature disclaimers legally enforceable?
Generally limited. Email confidentiality disclaimers attached at the bottom of messages have weak case-law precedent for enforcement against unintended recipients. They serve mainly as evidentiary support that the sender intended the message to be confidential, and as a regulatory requirement in some jurisdictions for specific industries (financial, legal). They are not a substitute for proper distribution controls, encryption, or access management.
Can email signatures be used to satisfy GDPR information requirements?
Partially. GDPR Articles 13 and 14 inform-the-data-subject obligations are typically met through privacy notices and explicit consent flows, not signatures. Signatures can surface the Data Protection Officer contact and a link to the privacy policy. They do not substitute for the formal privacy notice mechanism required by the regulation. For compliance-driven signature deployment, see the SyncSignature compliance posture.
What is the difference between an email signature and an email disclaimer?
A signature is the structured block at the end of an email containing the sender's identity: name, title, contact information. A disclaimer is the legal notice typically appended below the signature stating confidentiality, intended-recipient limitations, or regulatory compliance. Signatures are universal practice. Disclaimers are context-dependent, common in regulated industries (financial, legal, healthcare) and multinational organizations subject to multiple jurisdictions.
Deployment mechanics
How does Microsoft 365 Centralized Deployment of an Outlook add-in work?
A Microsoft 365 global admin approves an add-in once in the Microsoft 365 admin center, targets it to all users or a specific Entra ID group, and Microsoft propagates the add-in silently to every targeted user's Outlook on desktop, web, and mobile within 6 to 12 hours. The end user does nothing. The add-in installs without per-user authorization or installation prompts. See Microsoft 365 deployment details.
How does Google Workspace sendAs profile signature deployment work?
A Google Workspace super-admin authenticates the third-party tool via OAuth with the Gmail sendAs scope. The tool writes the rendered signature directly into each user's Gmail "send mail as" profile through the Gmail API. The signature appears the next time the user composes mail. No browser extension, no user action, no per-user authorization beyond the initial admin OAuth grant. See Google Workspace deployment details.
Can email signatures be deployed without an admin OAuth grant?
Not at the Google Workspace or Microsoft 365 level. Both platforms require admin authorization for organization-wide deployment. Per-user manual installation is always possible (the user pastes the signature into Gmail or Outlook settings themselves), but this does not scale and creates drift as users edit or remove the signature. Centralized deployment requires admin consent at the tenant level.
How fast does an email signature update propagate after a directory change?
5 to 10 minutes for the signature management tool's own sync cycle on top of whatever the directory itself takes. Google Workspace directory updates are near-instant. Microsoft Entra ID changes can take a few minutes to settle. End-to-end, a name or title change in your HRIS typically reaches every signature within an hour, often within 15 to 30 minutes. See centralized signature management.
Do email signatures sync between Gmail web and Gmail mobile automatically?
Yes. Gmail uses one sendAs profile per email account, which is honored on Gmail web, Gmail iOS, Gmail Android, and any third-party client connecting via the Gmail API. A signature written into the sendAs profile shows up across all surfaces. The same is not true for Apple Mail on iOS, which maintains its own per-device signature setting independent of the Gmail account configuration.
What is the difference between server-side and client-side email signature stamping?
Client-side stamping injects the signature inside the user's mail client, such as Gmail web, Outlook desktop, or the Outlook add-in, before the message is sent. The message originates from the user's normal mail server with the signature already attached. Server-side stamping routes outbound mail through a third-party server which appends the signature in transit. Client-side keeps mail flow native; server-side adds a third party to the mail path.
Common errors
Why does my email signature show as plain text in some replies?
Plain-text mode in the recipient's reply client. Some recipients reply in plain text by default, which is the default in Outlook for Windows depending on user preferences. This strips the HTML signature on the reply chain but does not affect the original message. The original signature renders correctly in the recipient's inbox. Only the reply shows the plain text version.
Why does my email signature image not load for some recipients?
Three common causes. First, the recipient's client blocks external image loading by default, which is the default in Outlook desktop and Apple Mail in some configurations. Second, the image URL returns 404 or is hosted on a CDN the recipient's network blocks. Third, corporate firewalls block image-loading requests to certain domains. Always include alt text so the layout does not collapse if images fail.
Why does my email signature appear twice in some emails?
Two systems are stamping signatures simultaneously. Common pattern: the user has a signature configured in Gmail or Outlook directly AND a signature management tool is also deploying a signature. Disable the user's local signature, or ensure the management tool is the single source of truth. This is one of the first things to audit when migrating between signature platforms.
Why are signature images not appearing in Outlook desktop?
Outlook for Windows blocks external images by default for messages from senders not in the Safe Senders list. The recipient sees a placeholder until they click "Download Pictures." Hosted images on HTTPS-served domains are more reliably loaded than HTTP. Make sure the image URLs are stable, served over HTTPS, and hosted on a CDN with high uptime. The first time a user adds a sender to Safe Senders, images load automatically thereafter.
Why does the email signature look broken when forwarded?
Forwarded messages re-render the signature within the new email body. Some clients re-process HTML during forward and strip styling, especially Outlook for Windows. Signatures designed with table-based layouts and inline styles survive forwarding better than signatures using <div> elements and external stylesheets. Test forward behavior on Outlook for Windows specifically as part of signature QA.
Why does my email signature look different to me than to recipients?
The sender's compose view renders the signature in their own client's editor, which may use different CSS defaults than the rendered email in the recipient's inbox. Always test by sending the signature to a separate email account on a different client to see the actual rendered output. The compose view is not a reliable preview of how the signature will appear to recipients.
Looking for centralized email signature management?
SyncSignature handles all of this for your team. Directory sync from Google Workspace or Microsoft 365. Group-based templates by department, role, or office. Banner campaigns with click analytics. Disclaimer text deployed centrally and updated firm-wide in minutes. 100+ modern templates with regular updates.
Start a 7-day free trial. No card required. 5-seat minimum on the Teams plan. Or see pricing and book a 15-minute setup call.
For the deeper reference content, see the SyncSignature compliance posture and the directory sync guide.
Share this post