In a 2020 survey of more than 750 global marketers and business owners, 62% said their companies used email signatures for marketing, while 82% named branding as the main objective. Wave Connect's survey data makes the point clearly: an email signature isn't just a sign-off. It's a small, repeated marketing surface that also carries identity, accessibility, compliance, and deliverability risks.
The mistake is treating it like a miniature poster. A reliable signature uses live text, restrained HTML, accessible images, useful links, and a plain-text fallback. It should look intentional in Gmail, survive Outlook's rendering quirks, remain readable on a phone, and pass a screen-reader check before you roll it out across a team.
Table of Contents
- What a Modern Email Signature Actually Needs
- HTML vs Plain Text and Which to Use When
- Images, Hosting, and Responsive Layout
- Setting Up Signatures in Gmail, Outlook, Apple Mail, and Mobile
- Accessibility and Legal Disclosure Essentials
- Testing and Troubleshooting Common Signature Problems
- Ready-to-Use Templates and a Maintenance Routine
What a Modern Email Signature Actually Needs
A professional signature answers one question quickly: who sent this, how can I contact them, and what should I do next? Build around that sequence instead of adding every credential, social profile, campaign banner, and corporate disclaimer available.
The shift toward marketing use is already established. The same Wave Connect survey found that 45% of companies used signatures regularly and 18% used them occasionally. That makes consistency important, but consistency doesn't mean forcing every employee into an overloaded block.
Start with the identity block
Required: name and company.
Recommended: role or department.
Optional: pronouns, professional designation, or one relevant credential.
Use the name people know you by, followed by a role that explains your responsibility. Avoid stacking several job titles, internal committees, and honorary labels. A recipient should understand your position without decoding an organizational chart. Pronouns can be useful when they reflect your preference or help recipients address you correctly, but they're not mandatory for every sender.
Add direct contact details
Required: one dependable contact route, usually a company website or business email.
Recommended: direct phone number and website.
Optional: booking link, support portal, or location-specific contact.
Use live text for phone numbers and addresses. Don't put contact details inside a single image, because blocked images and assistive technology can make the information disappear. Add a booking link only when it serves the recipient. A sales representative may need it, while an internal finance mailbox probably doesn't.
The company row should include the company name, an optional logo, and a readable website URL. Social icons are optional. Include only platforms the sender actively maintains, and link each icon directly to the relevant profile. A row of unused networks makes the business look less credible, not more visible.
Keep compliance proportional
A physical business address may be required by your organization's legal or regulatory process, and bulk marketing messages need their own identification and opt-out handling. A confidentiality notice can make sense in legal-heavy industries, but it shouldn't bury the identity and contact information in every ordinary reply.
For teams managing many signatures, treat the file as a controlled business asset. A task board such as Kanban Tasks for Gmail can help coordinate approvals, campaign swaps, and ownership without turning every update into an email thread.
Practical rule: Build the useful version first. Add legal or campaign content only when a real business or regulatory requirement justifies the extra lines.
Aim for a five-line rule on mobile: identity, role and company, direct contact, website or booking link, and one focused action. You can include a logo or social row if it remains compact, but every added element must earn its space.
HTML vs Plain Text and Which to Use When
HTML gives a signature visual hierarchy. You can use a logo, styled links, a compact table layout, and social icons that feel like part of the brand system. It also introduces failure points. Different clients interpret HTML differently, remote images may be blocked, and a signature packed with markup, images, or tracking pixels can create unnecessary deliverability risk.
Plain text is less attractive, but it works almost everywhere. Screen readers can process it cleanly, recipients see the contact details even when images are disabled, and the message carries less formatting overhead. The trade-off is straightforward: you lose logos, visual buttons, and icon-based navigation.
| Criterion | HTML Signature | Plain-Text Signature |
|---|---|---|
| Branding | Supports logos, colors, tables, and styled links | Depends on wording and simple text structure |
| Compatibility | Varies across Gmail, Outlook, Apple Mail, and mobile clients | Highly consistent |
| Images | Can display logos and icons, but remote images may be blocked | No image support |
| Accessibility | Requires careful alt text, contrast, and structure | Naturally lightweight, but still needs readable wording |
| Deliverability | Excessive markup, images, and tracking pixels add risk | Minimal formatting overhead |
| Best use | Client-facing correspondence and selected marketing contexts | Internal replies, transactional mail, and high-volume sending |
Use the sender's context as the decision rule
External client-facing senders should usually maintain both versions. Use HTML when the recipient benefits from a richer identity block, and preserve a plain-text alternative for clients, workflows, or message modes that strip formatting.
Sales teams running campaigns need extra discipline. A prominent CTA can support a legitimate next step, but every link and image also adds another element to test. Avoid turning every email into a promotional panel. One clear destination is easier to understand and less likely to look like a template inserted by an automated system.
Purely internal reply chains can default to plain text, especially when people exchange short operational messages. Transactional and high-volume senders should keep the signature plain text with one relevant link to a hosted contact card or help page. A rich signature rarely improves a receipt, alert, or system notification.
Don't solve the problem by exporting the entire signature as one image. The recipient may see a blank space, an attachment, or a filename instead of usable identity and contact information. Live text remains the safer foundation, whether the surrounding design is HTML or deliberately plain.
Images, Hosting, and Responsive Layout
Images cause many signature failures because people design them for a browser and paste them into an email client as if the two environments behaved the same way. Build for constrained rendering from the start.
Use this checklist:
- Serve images over HTTPS: Secure image URLs reduce mixed-content problems and prevent clients from treating the asset as unsafe.
- Use stable hosting: A persistent CDN endpoint should continue working when recipients reply, forward, or archive the message.
-
Set explicit dimensions: Add pixel width and height attributes to every image. Outlook can ignore CSS such as
max-widthandheight:auto, then render an image at its intrinsic size, as University of Maryland accessibility guidance explains. - Keep assets light: Exclaimer's deliverability guidance recommends keeping each image around 50 KB or less. Compress logos and icons rather than relying on the recipient's client to do the work.
- Write useful alt text: A logo needs a meaningful description, not a filename. Decorative images can use an empty alt attribute when the surrounding text already conveys the information.
Build for narrow screens
Use a compact wrapper and a table-based structure rather than a modern web layout. A 600-pixel maximum width is a practical email convention, but keep the actual content narrower when the signature contains only identity and contact details. Tables remain useful because Outlook's Word-based rendering engine handles them more predictably than many CSS layouts.
A single-row structure can work well for a logo beside live text. Stacked sections are easier to read when the signature includes a longer legal notice, but they consume more vertical space. Choose the structure based on content, not on a web mockup.
Social icons should have text equivalents when images might be blocked. A short “LinkedIn” link is more useful than an icon that renders as an empty square. Don't depend on lazy-loading banners either. Most email clients won't honor lazy-loading behavior consistently, so the banner may never appear.
Before deployment, run the finished HTML through a checker such as this HTML email checker. Inspect the source for duplicated styles, broken URLs, missing dimensions, and links that point to staging pages.
Setting Up Signatures in Gmail, Outlook, Apple Mail, and Mobile
The design is only half the job. Each client has its own editor, default behavior, and limitations, so the same signature can look different after installation.
Gmail on the web
Open Gmail, select Settings, choose See all settings, and stay on the General tab. Find Signature, select Create new, name the signature, and paste the formatted version into the editor.
Choose the signature for new emails and replies or forwards separately. If Gmail manages more than one account or address, check the per-account defaults instead of assuming the first signature applies everywhere. Gmail's image insertion can also strip or mishandle alt text, so inspect the resulting HTML and test the received message rather than trusting the editor preview.
Paste the plain-text alternative into a separate workflow or keep it available for clients that don't preserve the formatted version. Save changes at the bottom of the page before closing settings.
Outlook desktop and Outlook on the web
In Outlook desktop, use File, Options, Mail, then Signatures. Create the signature, select the account, and choose whether it applies to new messages, replies, and forwards.
Outlook desktop uses Word-based HTML rendering. That's why a layout that looks perfect in a browser can shift, expand, or lose spacing in Outlook. Use tables, inline styles, explicit image dimensions, and web-safe fonts. For a detailed Outlook installation walkthrough, this guide to creating a professional email signature is a useful companion.
Outlook on the web has a lighter editor. Open Settings, search for signature, create or paste the signature, then set the defaults for new messages and replies. Test the web version separately from the desktop application. They aren't interchangeable rendering environments.
Apple Mail on macOS
Open Mail, select Mail, then Settings, and choose Signatures. Select the account, create a signature, and paste the formatted content. Turn off the option that uses the default message font if your signature relies on specific font sizing, then send a test to a separate inbox.
Apple Mail can preserve formatting well, but that doesn't guarantee Outlook or Gmail will display the same structure. Always inspect the received output.
iPhone, iPad, and mobile apps
On iOS, go to Settings, Mail, Signature, then choose the account and enter the signature. The mobile override is most dependable as plain text. HTML may stick only when the signature is managed through the All Signatures area, so verify the actual sent message instead of relying on the composer.
Gmail for Android and iOS generally offers a mobile signature setting separate from the web signature. Keep it short, and don't assume the web HTML version will appear in the app. The Outlook mobile app also has its own signature setting under account preferences. For inline images, use publicly accessible HTTPS-hosted assets because mobile composers may not embed local files reliably.
Teams should centralize approved templates where possible. Google Workspace templates, Outlook account defaults, and a signature manager can reduce manual drift. Assign one owner for brand, legal, and campaign changes, then require a client and mobile test after each update.
Accessibility and Legal Disclosure Essentials
Accessibility belongs in the build specification, not a final polish pass. University of Maryland's email accessibility guidance recommends readable text, left alignment, descriptive alt text, and a contrast ratio of at least 4.5:1 for text elements. These choices determine whether recipients can understand the signature with low vision, a screen reader, or images turned off.
Keep the name, title, phone number, company, and website as live text. A logo can strengthen recognition, but it cannot replace the identity block. An image-only signature may appear blank or expose an unhelpful filename to assistive technology. It also removes a small marketing surface when image loading fails, because the recipient loses the sender's identity, contact path, and call to action together.
Make the structure understandable
Set a logical reading order. Tables can provide dependable alignment, but a maze of meaningless cells makes screen-reader output harder to follow. Keep text left-aligned, use readable sizing, and give each meaningful image descriptive alt text.
Use 12-point readable fonts and 4.5:1 contrast for text elements. Exclaimer's accessible email signatures guide also highlights semantic structure and plain-text fallbacks. Avoid a long row of pipe characters as a substitute for structure. Screen readers may announce the punctuation awkwardly, while visual readers may struggle to see which details belong together.
Separate legal needs from decorative boilerplate
The signature should identify the sender and business clearly. Marketing messages may need appropriate opt-out handling, while regulated organizations may require registration details, license information, VAT details, or industry-specific disclosures. Confirm the requirement with legal or compliance staff instead of copying a generic paragraph from another company.
Confidentiality language may suit legal or regulated correspondence, but it should not bury practical contact information. For guidance on wording and placement, review this resource on disclaimers in emails.
Use this approval checklist:
- Identity: The recipient can identify the person and organization without loading images.
- Accessibility: Images have useful alternatives, text contrasts clearly, and the reading order makes sense.
- Compliance: Required registration, licensing, address, privacy, and opt-out details appear for the relevant message type.
- Fallback: Plain text remains understandable when HTML is removed.
Testing and Troubleshooting Common Signature Problems
“Send yourself a test email” isn't a complete verification process. A signature can look fine in the composer and fail after transport, client conversion, image blocking, or mobile scaling.
Start with a small seed list covering Gmail, Outlook, Apple Mail, and a mobile inbox. You can use separate test accounts or a service such as Mail Tester. Send the same message from the actual account and inspect both the visible rendering and the full source.
Use a repeatable verification pass
- Inspect the source: Confirm the signature is part of the message body, not a suspicious attachment or malformed fragment.
- Open multiple environments: Check desktop webmail, desktop clients, and mobile. Look for line breaks, oversized images, clipped content, and dead links.
- Disable images: Verify that the name, role, company, phone, and website remain usable.
- Run a screen-reader pass: VoiceOver on macOS or iOS and NVDA on Windows can expose awkward reading order, missing alt text, and meaningless link labels.
- Check links and redirects: Open every destination and confirm it uses the intended production URL.
A signature isn't approved when the sender likes the preview. It's approved when the recipient's client, device, and accessibility tools can use it.
Diagnose the failure instead of patching symptoms
Raw HTML usually means the message is in plain-text mode or the client stripped the tags. Broken images often come from an HTTP asset inside an HTTPS message. Fix the image URL and dimensions rather than telling recipients to enable unsafe content.
Oversized blocks usually come from banners, excessive divider lines, or intrinsic image dimensions that Outlook interprets differently. A tracking pixel or a link to a newly registered domain can also make an otherwise ordinary signature look suspicious to filters. Remove unnecessary tracking, simplify the markup, and retest.
| Client | Known Signature Quirks |
|---|---|
| Gmail web | Image insertion can affect alt text, and account defaults need separate checking |
| Outlook desktop | Word-based rendering can ignore some CSS and expand images without explicit dimensions |
| Outlook on the web | Uses a lighter editor with behavior separate from desktop Outlook |
| Apple Mail | May preserve local formatting that other clients reinterpret |
| Gmail mobile | Has its own mobile signature setting rather than simply inheriting the web version |
| Outlook mobile | May not embed local images reliably, so hosted assets are safer |
If a long message gets clipped, review this troubleshooting guide about truncated email messages. Then shorten the signature itself before adding more CSS.
Ready-to-Use Templates and a Maintenance Routine
A good template is deliberately boring at the code level. Use inline styles, live text, tables for layout, and clear links. The examples below are starting points, not permission to skip client testing.
Minimal plain-text version
Use this for transactional mail, first-touch outreach, or any workflow where reliability matters more than visual branding.
Name Surname
Role, Company Name
Phone: +1 000 000 0000
Website: https://example.com
LinkedIn:
Keep the phone number and website as actual text. If your mail system automatically converts URLs into links, recipients can still reach the intended destination without relying on an image or button.
Compact HTML version
This version uses a table, live contact details, and one linked logo. Replace the example values and confirm that the hosted asset has useful alt text.
|
Extended campaign version
Use an extended block only for a sender whose message context supports a campaign CTA. Keep the promotional line separate from the identity information, include alt text, and provide an unsubscribe destination for marketing communication.
|
Name Surname Role, Example Company name@example.com · Book a meeting |
|
| Unsubscribe from marketing emails |
For broader campaign planning, these actionable email tips for small businesses are useful beyond the signature itself.
Maintain it on a schedule
Review the signature at least as part of your regular brand-control cycle. MySignature's survey data reports that 44.4% of users update signatures two to four times per year, while 31.6% update them only once every few years. Those figures show why ownership matters: a stable template still needs someone responsible for link checks, campaign expiry, and client revalidation.
Run this maintenance routine:
- Check links: Test phone, website, booking, social, CTA, and unsubscribe destinations.
- Check hosting: Confirm every image still loads over HTTPS from a stable endpoint.
- Refresh assets: Replace outdated logos, campaign banners, and low-resolution images.
- Review accessibility: Recheck alt text, contrast, reading order, and plain-text output.
- Retest clients: Recheck Gmail, Outlook, Apple Mail, and mobile after meaningful changes.
- Record approval: Keep the approved HTML, plain-text fallback, legal copy, and owner together.
Before rollout, confirm the anatomy, choose HTML or plain text by sender context, verify image hosting, install through the correct platform path, complete accessibility and legal review, and run the full render matrix. Teams that make this a repeatable release process avoid the usual scramble when a phone number changes or a campaign ends.
CleanMyList helps email teams verify addresses before campaigns and keeps bad data from undermining carefully tested messaging. Use the CleanMyList service to check a list before sending, or use its signature generator when you need formatted and raw HTML versions ready for Gmail, Outlook, or Apple Mail.