Fix HTML Email Signature Issues: 7 Proven Fixes for Outlook, Outlook Classic & Gmail

How to Fix HTML Email Signature Issues in Outlook, Outlook Classic, and Gmail

Most broken email signatures come down to one of three causes: the email client rewrites or strips your HTML, the image is hosted somewhere unreliable and eventually stops loading, or the way the image is linked makes spam filters suspicious of the whole message. Fixing this properly means addressing all three, not just re-uploading the logo and hoping it sticks this time.

This guide covers how signatures behave differently across Outlook desktop (classic), the new Outlook, Outlook on the web, and Gmail, and, just as importantly, where you should actually be hosting your signature images so they don’t break in six months or get your emails quietly filtered into spam.

Why HTML Signatures Break in the First Place

Outlook Desktop Doesn’t Render HTML Like a Browser Does

The classic Outlook desktop app doesn’t use a normal browser engine to display HTML email. It uses Microsoft Word’s rendering engine instead, which has existed since Outlook 2007 and has never fully caught up to modern web standards. This is why signatures that look perfect in a browser-based email preview tool often show broken spacing, missing background colors, or oddly shifted logos once they land in actual Outlook desktop.

Copy-Pasting a Signature Introduces Hidden Formatting

When a signature is copied from a Word document, a design tool, or another email and pasted directly into the Outlook or Gmail signature box, it often carries invisible formatting, extra <span> tags, inline styles from the source program, or broken table structures. These usually aren’t visible until the signature is viewed in a different client than the one it was built in.

Images Hosted in the Wrong Place Eventually Disappear

A logo that works today but shows as a broken image icon a few months later is almost always a hosting problem, not a signature problem. If the image lives on a personal Google Drive link, a free anonymous image host, or gets deleted/moved without anyone updating the signature, every email sent afterward shows a broken image, including in messages sent months ago that recipients might reopen.

Some Signature Setups Actively Trigger Spam Filters

This is the one most people don’t think about. Certain ways of linking or embedding signature images make spam filters more suspicious of an email, not less. We’ll walk through exactly which practices cause this further down.

Fixing HTML Signatures in Outlook Classic (Desktop App)

1. Open File > Options > Mail > Signatures.
2. If you’re pasting a pre-built signature, paste it using the plain “Keep Text Only” option first, then rebuild formatting inside Outlook’s own editor rather than pasting rich formatting directly. This avoids carrying over broken external styles.
3. For a signature with a logo or headshot, use Insert Picture rather than copy-pasting an image, since copy-pasted images can sometimes embed as a Word object instead of a proper image, which renders inconsistently.
4. Avoid background images and avoid CSS techniques like flexbox or CSS Grid entirely; Outlook desktop’s Word-based engine does not support them and will collapse your layout. Table-based HTML with inline styles is still the only truly reliable method for consistent rendering here.
5. Keep font choices to widely available system fonts. A custom web font will simply fall back to Times New Roman in classic Outlook, which is rarely what anyone intended.
6. After saving, send yourself a test email and open it from a different device if possible, spacing issues are far more visible on a second screen or resolution than on your own.

Fixing HTML Signatures in New Outlook and Outlook on the Web (OWA)

The new Outlook and Outlook on the web use a modern browser-based rendering engine, closer to how Gmail or a normal webpage displays HTML. This generally means fewer layout-breaking issues than classic desktop Outlook, but a few problems still show up regularly:

• Go to Settings > Accounts > Signatures (new Outlook) or the gear icon > View all Outlook settings > Mail > Compose and reply (OWA).
• If a signature built for classic Outlook looks slightly different here, that’s expected, this is a different rendering engine. Don’t assume something is broken just because spacing looks marginally different than in the desktop app; check both before making changes.
• Confirm the setting for whether the signature is automatically added to new messages, replies, and forwards, since these are separate toggles and a common source of “my signature isn’t showing up” tickets that isn’t actually a formatting problem.
• If your organization manages signatures centrally through an admin policy (Exchange transport rules or a signature management add-in), a locally saved signature may be silently overridden. Check with an administrator before spending time troubleshooting a signature that’s controlled centrally.

Fixing HTML Signatures in Gmail

1. Go to Settings (gear icon) > See all settings > General, and scroll to the Signature section.
2. Gmail’s signature editor supports a reasonable subset of HTML/CSS through its formatting toolbar, but if you’re pasting in signature HTML built elsewhere, paste it into the signature box and then manually verify spacing and alignment, Gmail sometimes strips certain inline styles it considers unnecessary.
3. For a logo or image, use the image icon in the signature editor and choose to either upload the image directly (Gmail hosts it on its own infrastructure) or insert it via a web address. Uploading directly through Gmail’s own image tool is generally the more stable option for Gmail specifically, though it won’t help consistency across other email clients.
4. If the signature was built for Outlook and includes table-based layout code, it will typically still work in Gmail, since Gmail’s renderer is more forgiving than Outlook’s, but double-check image alignment specifically, as this is the most common visual difference.
5. Gmail mobile apps (iOS/Android) use a separate signature setting from Gmail on desktop. A signature added on desktop will not automatically appear on mobile unless configured separately in the app’s own settings.

Where It’s Actually Safe to Host Signature Images

This is the part most guides skip, and it’s the part that causes the most long-term problems.

Don’t Use Free, Anonymous Image Hosts

Services designed for casual image sharing aren’t built for embedding in outbound business email. Many either block “hotlinking” (displaying the image directly in another context instead of on their own site), have unpredictable uptime, or carry a domain reputation that’s been used by spam campaigns in the past, which can quietly lower the trust score of any email referencing that domain.

Don’t Embed Images as Base64 Data

It’s technically possible to embed an image directly into the HTML using a Base64-encoded string instead of linking to it externally. This avoids a broken-link problem, but it significantly increases the email’s file size, and several spam filtering systems specifically flag large embedded data blocks as a spam indicator, since legitimate transactional and conversational email rarely does this. Avoid this method for signatures.

Host Images on Your Own Domain

The most reliable and safest option is hosting signature images on infrastructure tied to your own business domain, for example a dedicated assets. or cdn. subdomain with a valid HTTPS certificate. This keeps the image’s URL aligned with your actual sending domain, which is a positive trust signal rather than a neutral or negative one, and gives you full control over uptime, so the image doesn’t disappear because a third-party free service changed its policies or shut down.

A Proper CDN Is the Better Long-Term Option

For businesses that want a more scalable and reliable setup, using a content delivery network under your own domain, such as Cloudflare, Amazon S3 with CloudFront, or a similar service, provides fast image loading, high uptime, and a stable URL that isn’t tied to any single employee’s personal storage account.

Keep the Image Itself Lightweight

Regardless of where it’s hosted, a signature image should be a small, optimized file, ideally under 30-50 KB, in PNG or JPG format, sized to its actual display dimensions rather than a large image scaled down with HTML width/height attributes. Oversized images slow down load time and, in some corporate filtering systems, contribute to spam scoring based on overall message size.

Signature Practices That Increase Spam Risk

• Using URL shorteners in signature links (bit.ly, tinyurl, etc.). These are heavily associated with spam and phishing campaigns, and many corporate spam filters flag them automatically regardless of where they actually point.
• A display link that doesn’t match its real destination (for example, text that reads “linkedin.com” but actually links elsewhere). This is one of the clearest phishing indicators filters look for.
• Large embedded promotional banners. A small logo and clean contact details read as a normal business signature. A large promotional image with marketing copy starts to resemble a newsletter or advertisement, which changes how filtering systems classify the message.
• Tracking pixels from third-party signature or marketing tools. Some signature management platforms insert invisible tracking images to measure opens. Depending on the tool and how it’s implemented, this can trigger the same detection logic used to flag marketing emails, which is not what you want for everyday one-to-one business correspondence.
• Broken or missing alt text on the logo image. This isn’t a spam trigger by itself, but it does affect accessibility and how the email renders when images are blocked by default, which is the default setting in many corporate inboxes.

A Quick Signature Health Checklist

• Signature displays correctly in Outlook classic desktop, new Outlook, Outlook web, and Gmail
• Built using table-based HTML with inline CSS, not modern layout CSS
• Images hosted on your own domain or a proper CDN, not a free/anonymous image host
• No Base64-embedded images
• No URL shorteners in any signature link
• Display text for every link matches its actual destination
• Image file size is optimized and reasonably small
• Alt text is set on the logo/headshot image
• Tested on both desktop and mobile versions of each email client in use at your organization

When to Call a Professional

If your organization needs the same signature deployed consistently across dozens or hundreds of mailboxes, centrally managed through Exchange rather than set individually, or if you suspect signature-related spam flagging is affecting deliverability more broadly, this is worth handing to an experienced Microsoft 365 or Google Workspace administrator rather than troubleshooting client by client.

Get Help Fixing Your Email Signatures

If your team’s signatures look different across Outlook and Gmail, keep breaking after updates, or you’re not sure whether your current image hosting setup is hurting deliverability, we can standardize and deploy a signature that actually works consistently across every client your team uses.

Talk to Our IT Support Team →

Frequently Asked Questions

Why does my HTML signature look fine in Gmail but broken in Outlook? Outlook desktop renders HTML using Microsoft Word’s engine rather than a browser engine, so modern CSS layouts that work in Gmail often collapse or misalign in Outlook. Table-based HTML with inline styles is the most reliable format across both.

Is it safe to host signature images on Google Drive or Dropbox? Generally no. These services aren’t designed for direct image embedding in outbound email, links can expire, get rate-limited, or break entirely if sharing settings change, leaving every past and future email with a broken image icon.

Does embedding my logo directly into the HTML avoid broken image problems? It avoids broken links, but Base64-embedded images increase the email’s size significantly and are flagged by some spam filtering systems as a risk indicator, so this isn’t a safe substitute for proper external hosting.

Can a signature actually cause my emails to be marked as spam? Yes. URL shorteners, mismatched display links, embedded tracking pixels, and oversized promotional banners in a signature can all raise a message’s spam score, even if the email’s actual content is completely normal.

Where should I host my company logo for email signatures? On your own domain or a dedicated subdomain/CDN with HTTPS, ideally something like assets.yourdomain.com. This keeps the image’s trust signal aligned with your sending domain and avoids relying on a free third-party host that could change or disappear.

A companion video walkthrough covering related Fix HTML Email Signature Issues: 7 Proven Fixes for Outlook, Outlook Classic & Gmail is available here: YouTube. This article was written independently and does not reproduce content from that video.