Outlook breaks signatures more than any other email client

Outlook Email Signature:
The Complete Guide

If you've ever spent an hour perfecting an email signature — picked the fonts, lined up the logo, added your socials — only to paste it into Outlook and watch it completely fall apart... you're not alone. This guide explains exactly why Outlook does this, and how to make a signature that actually holds together.

Create an Outlook-Proof Signature — FreeNo account needed. Free forever.

Here's a scenario that probably sounds familiar. You build a beautiful email signature in a tool, or maybe you copy one from a colleague who works in Gmail. It looks great in the preview. Colors are right, the logo is crisp, the spacing is clean. You paste it into Outlook's signature settings and hit Save.

You send a test email to yourself. You open it. The font has changed to something you didn't choose. The logo is missing — or worse, it's shown as a paperclip attachment at the bottom. The columns have collapsed into a vertical stack. The colors are off. And somehow there are mysterious extra spaces between every line.

This isn't bad luck. It's Outlook being Outlook. The problem is so well-known in email development circles that it has its own dedicated complaints section in every email HTML guide ever written. Outlook's behavior with HTML signatures is genuinely inconsistent, often counterintuitive, and has barely changed despite years of complaints.

The reason it happens — and the fix for it — all comes down to one thing: Outlook renders HTML using Microsoft Word's engine, not a proper web browser. Once you understand that, everything else makes sense. And once you build your signature with that constraint in mind (or use a tool like NeatStampthat already accounts for it), you'll stop fighting Outlook and start getting consistent results.

This guide covers: why Outlook breaks signatures at a technical level, how to set up signatures in every version of Outlook (2016, 2019, 2021, Microsoft 365, new Outlook, Outlook Web, and Outlook Mobile), the most common problems and exactly how to fix them, and what you can and can't do with HTML in Outlook.

Why Outlook breaks your email signature

To understand why Outlook mangles HTML signatures, you need to understand a decision Microsoft made back in 2007 that email developers have been cursing ever since: they switched Outlook's rendering engine from Internet Explorer to Microsoft Word.

The Word engine problem

Classic Outlook (2007 through current desktop versions) renders HTML content using the Microsoft Word rendering engine — specifically, the same code that Word uses to display documents. Word was designed to render Word documents, not web pages. It supports a small, inconsistent subset of HTML and CSS, and ignores everything else without warning.

What does this mean in practice? Here's a non-exhaustive list of things Outlook either ignores completely or handles incorrectly:

CSS flexbox and grid

Completely ignored. Layout collapses.

CSS position: absolute/relative

Not supported. Elements jump.

border-radius

Partially broken — rounded corners disappear.

background-image in CSS

Stripped entirely.

max-width / min-width

Inconsistent behavior across versions.

Base64 encoded images

Converted to attachments.

Web fonts (@font-face)

Falls back to system fonts silently.

CSS variables (--custom)

Not supported at all.

External stylesheets

Stripped by most email clients.

padding on div elements

Ignored; use tables instead.

Then there's the DPI scaling problem. Outlook renders images at 96 DPI by default, regardless of what your screen or the image file specifies. If you have a high-DPI (Retina) image and don't set explicit pixel dimensions with width and height attributes directly on the img tag, Outlook will display it at the wrong size — typically much larger than intended.

The base64 image problem is particularly frustrating. Most modern web-based signature generators embed images as base64 data URIs because it makes the signature self-contained. That works fine in Gmail, Apple Mail, and Outlook Web. But Outlook Desktop sees base64 image data, doesn't know what to do with it, and turns it into a file attachment. Recipients then see a blank signature with a mysterious attachment called something like "image001.png". Not ideal.

The only layout approach that reliably works across all versions of Outlook is HTML tables — the same technique used to build websites in the late 1990s. Table cells accept inline CSS (with limitations), images with explicit dimensions behave predictably, and the overall structure doesn't collapse. It's not glamorous code, but it's what actually works. This is exactly what properly built HTML email signatures use under the hood.

How to create an Outlook-proof email signature

The approach that works consistently is: build your signature in a tool that understands Outlook's constraints and generates table-based HTML with hosted images and inline CSS. Then copy the rendered output (not raw HTML code) and paste it into Outlook. Here's how to do it with NeatStamp.

1Open NeatStamp and fill in your details

Go to NeatStamp's free editor. Enter your name, job title, company, phone number, email address, and website. Upload your profile photo if you want one — NeatStamp hosts it on its CDN automatically, which is what makes it work in Outlook (no base64 problems). Add your company logo the same way.

2Choose a template and set your colors

Pick from NeatStamp's templates — all of them use table-based HTML that survives Outlook's renderer. Set your brand colors. Everything you see in the preview is what you'll get in Outlook, because the preview respects the same CSS limitations Outlook does. This is different from tools that show you a beautiful preview but generate code Outlook can't handle.

3Click "Copy Signature"

NeatStamp's Copy Signature button copies the rendered signature as rich text (not raw HTML code) to your clipboard. This is important: you're copying the formatted output, not source code. When you paste this into Outlook, it goes in as a formatted signature — not as literal HTML characters. Think of it like copying a formatted table from Word and pasting it somewhere else.

4Paste into Outlook's signature editor

Open Outlook, navigate to the signature settings (exact path depends on your version — see the section below), create a new signature, click inside the signature body area, and press Ctrl+V. The signature should appear with formatting intact. Give it a name, set it as your default for new messages, and optionally set a different or no signature for replies and forwards.

5Send a test and check on multiple devices

Send a test email to yourself and to a Gmail address. Check how it looks at different window widths. If you can, check it on your phone too. The signature from NeatStamp includes a mobile-responsive fallback so it doesn't look too wide on small screens — even though Outlook itself doesn't support CSS media queries, the table structure collapses gracefully.

How to add your signature in every version of Outlook

Outlook has more versions and flavors than almost any other email client, and the signature settings are in a different place in each one. Here's exactly where to go.

Outlook Desktop — Classic (2016, 2019, 2021, Microsoft 365)

This is the traditional Outlook app on Windows. The path is the same across Outlook 2016, 2019, 2021, and the Microsoft 365 version of Outlook Desktop.

  1. 1Open Outlook and click File in the top-left menu bar.
  2. 2Click Options in the left sidebar.
  3. 3In the Outlook Options dialog, click Mail.
  4. 4Under the Compose messages section, click Signatures…
  5. 5In the Signatures and Stationery dialog, click New to create a new signature.
  6. 6Give it a name (e.g., 'Main Signature') and click OK.
  7. 7Click inside the large text area on the right side — this is the signature editor.
  8. 8Press Ctrl+V to paste your signature from NeatStamp.
  9. 9Under 'Choose default signature', set your email account, and select your new signature for both New messages and Replies/forwards.
  10. 10Click OK to save.
Shortcut: In any compose window, go to the Insert tab → Signature → Signatures… — this takes you directly to the Signatures dialog without going through File → Options.

New Outlook for Windows

The "new Outlook" is a redesigned app Microsoft rolled out from late 2023. It looks and works more like a web app. The signature settings are in a completely different location.

  1. 1Open the new Outlook app.
  2. 2Click the gear/Settings icon in the top-right corner.
  3. 3In the Settings panel, click Accounts in the left sidebar.
  4. 4Click Signatures.
  5. 5Click the + New signature button.
  6. 6Enter a name for your signature.
  7. 7Click inside the signature editor area.
  8. 8Press Ctrl+V to paste your NeatStamp signature.
  9. 9Use the dropdowns to set this signature as default for new messages and replies.
  10. 10Click Save.

Outlook Web (OWA — Outlook.com and Microsoft 365 webmail)

Outlook Web Access (OWA) is the browser version of Outlook, accessible at outlook.office.com or outlook.com. It has its own signature settings, separate from the desktop app.

  1. 1Go to outlook.office.com (for work) or outlook.com (personal) and sign in.
  2. 2Click the Settings gear icon in the top-right corner.
  3. 3At the bottom of the Settings panel, click View all Outlook settings.
  4. 4Go to Mail → Compose and reply.
  5. 5Scroll down to the Email signature section.
  6. 6Click inside the signature editor and press Ctrl+V to paste your signature.
  7. 7Check the box to automatically include the signature on new messages.
  8. 8Optionally check the box for replies and forwards.
  9. 9Click Save.
OWA uses a web renderer so HTML signatures generally work better here than in classic Outlook desktop. Images load properly, and more CSS is supported.

Outlook on Mac

Outlook for Mac is a separate app from the Windows version and has a different rendering engine. Signatures generally behave better on Mac Outlook than Windows Outlook, but the setup path is different.

  1. 1Open Outlook for Mac.
  2. 2In the top menu bar, click Outlook → Settings (or press Cmd + ,).
  3. 3In the Preferences window, click Signatures.
  4. 4Click the + button to add a new signature.
  5. 5Give it a name.
  6. 6Click in the signature editing area on the right.
  7. 7Press Cmd+V to paste your NeatStamp signature.
  8. 8Close the Preferences window — changes save automatically.
  9. 9To set a default, go to the Accounts tab in Preferences, select your account, and choose your signature from the Default signature dropdown.

Outlook Mobile (iOS and Android)

Outlook Mobile is its own separate app and only supports plain text signatures. If you need a professional-looking signatureon mobile, you have two options: use a plain text version, or use your phone's native mail app which handles HTML better.

  1. 1Open the Outlook app on your phone.
  2. 2Tap your profile picture or initials in the top-left corner.
  3. 3Tap the Settings gear icon at the bottom.
  4. 4Scroll down and tap Signature.
  5. 5Toggle the Per Account Signature if you want different signatures for different accounts.
  6. 6Type your signature text in the box. Plain text only — no formatting.
  7. 7Tap the back arrow to save.
Note:If you use iPhone's native Mail app with your Microsoft 365 account, you can add an HTML signature through iOS Settings → Mail → Signature. This gives you a much richer signature experience than Outlook Mobile allows.

Common Outlook signature problems — and how to fix them

These are the problems that come up again and again. If you're troubleshooting a specific issue, find it here.

Images are showing as attachments, not in the signature

This is the single most common Outlook signature complaint. You add a logo or photo to your signature, it shows fine on your end, but recipients see a blank space and a file attachment.

Why it happens:The image in your signature is encoded as a base64 data URI (a long string of characters that represents the image data directly in the HTML). Outlook Desktop doesn't support base64 images and converts them to email attachments.

The fix: Your images need to be hosted at a public URL and referenced with a standard src="https://..."tag. NeatStamp hosts your uploaded images on its CDN automatically. If you're building HTML by hand, upload images to an S3 bucket, your company website, or any publicly accessible hosting, and link to them.

Signature loses formatting in replies and forwards

You reply to an email, your signature appears — but it's in a smaller font, the colors are wrong, or the layout has shifted.

Why it happens:Outlook applies its own default font and size settings when you compose in "plain text reply" mode, or when corporate email settings force a specific font on replies. Some Outlook configurations also compress or strip inline CSS in quoted replies.

The fix:In Outlook Desktop, go to File → Options → Mail → Stationery and Fonts. Set "When replying and forwarding" to "Use the same as my current theme" or specify your preferred font. Also make sure you're composing in HTML format (not Plain Text). Check File → Options → Mail → "Compose messages in this format" should be set to HTML.

Signature looks different on the recipient's end

Your signature looks correct in Outlook but the person receiving it sees something different — wrong font, missing bold, different spacing.

Why it happens:If you're using a web font or a font that isn't installed on the recipient's computer, their email client falls back to a system font. Corporate security gateways sometimes also strip or modify HTML. And if the recipient uses Gmail or Apple Mail, they render HTML differently than Outlook does.

The fix: Stick to web-safe fonts: Arial, Helvetica, Georgia, Times New Roman, Verdana, Trebuchet MS. These are installed on virtually every operating system. Also specify fallback fonts in your font-family declaration: font-family: Arial, Helvetica, sans-serif;. NeatStamp uses web-safe fonts by default.

Can't paste a rich text signature — it pastes as plain text

You copy the signature, paste it into Outlook, and it comes in as plain text with no formatting — just raw characters.

Why it happens:Either you're pasting raw HTML source code instead of the rendered signature, or you're composing in Plain Text mode (which doesn't support formatted content), or you're using Ctrl+Shift+V (paste without formatting) instead of Ctrl+V.

The fix:First, make sure you're using NeatStamp's "Copy Signature" button, not copying raw HTML from the source. Second, make sure your compose format is set to HTML: File → Options → Mail → Compose messages in HTML format. Third, use Ctrl+V (standard paste) when pasting into the signature editor — not right-click, as some context menus default to plain text paste.

Signature not showing at all

You created and saved a signature but it doesn't appear when you compose a new email.

Why it happens:Usually the signature exists but hasn't been set as the default. Or it's assigned to the wrong email account. This is especially common when you have multiple accounts in Outlook.

The fix:Go to File → Options → Mail → Signatures. In the "Choose default signature" section, make sure you've selected the correct email account from the "E-mail account" dropdown, then set your signature in both the "New messages" and "Replies/forwards" dropdowns. Each account has its own signature assignment.

Signature is too wide on mobile screens

Your signature looks great on desktop but on mobile it extends past the screen edge, requiring horizontal scrolling.

Why it happens: The signature table has a fixed pixel width (e.g., width="600") that doesn't adapt to smaller screens. Outlook doesn't support CSS media queries, so standard responsive design techniques don't work.

The fix: Keep your signature width at or below 500px. Use a single-column layout rather than multi-column for critical information. NeatStamp signatures are designed to be narrow enough to display reasonably on most mobile screens without CSS media queries. If you're seeing this issue with a NeatStamp signature, try a more compact template from the signature editor.

The technical truth about Outlook signatures

If you're the type who wants to know exactly what's happening under the hood, here's the full picture. This section is for developers or technically inclined folks who want to understand the constraints rather than just work around them.

/* What actually works in Outlook */

<table width="480" cellpadding="0" cellspacing="0" border="0">
  <tr>
    <td style="font-family: Arial, sans-serif; font-size: 14px;
               color: #1a1a1a; padding-right: 16px;">
      <img src="https://cdn.example.com/logo.png"
           width="120" height="40" alt="Logo" />
    </td>
    <td style="font-size: 13px; color: #555555;
               line-height: 1.5; border-left: 2px solid #0078d4;
               padding-left: 16px;">
      <strong>Jane Smith</strong><br />
      Senior Account Manager<br />
      [email protected]
    </td>
  </tr>
</table>

The table approach above is essentially the only layout method that works reliably. Here's a precise breakdown of what Outlook supports and ignores:

CSS that works in Outlook

  • font-family (web-safe only)
  • font-size, font-weight, font-style
  • color (hex values)
  • background-color on table cells
  • padding (on td, not div)
  • border (solid, specified fully)
  • text-align, vertical-align
  • line-height
  • text-decoration

CSS ignored by Outlook

  • display: flex / grid
  • position (relative/absolute)
  • border-radius
  • background-image
  • CSS variables
  • @font-face / web fonts
  • @media queries
  • transform, animation
  • box-shadow (mostly)

One more technical gotcha: Outlook adds its own styles on top of yours. It applies a default 10pt Times New Roman font inside the compose window, and when your signature is inserted, Outlook's own stylesheet can override yours unless you explicitly specify every style property with inline CSS. This is why you should always specify font-family, font-size, and color directly on every text element, never rely on inheritance from a parent element.

If you want to dig deeper, the HTML email signature technical guidecovers the full spec of what's safe to use across all major email clients, not just Outlook.

Outlook vs Gmail: signature compatibility

A question that comes up a lot: if I create my signature in Outlook and someone with Gmail receives it, will it look right? And what about the reverse — if someone creates a signature in Gmail and I receive it in Outlook?

Outlook → Gmail

If your Outlook signature uses table-based HTML with inline CSS and hosted images, Gmail will display it correctly. Gmail's renderer is much more capable than Outlook's — it handles most HTML and CSS properly. Your Outlook-safe signature will look fine in Gmail, and probably even better than it does in Outlook.

The one exception: Gmail strips style blocks in the <head>section, but since Outlook-safe signatures use inline CSS anyway, this doesn't matter.

Gmail → Outlook

This is where problems occur. Gmail signature builders often use CSS that looks great in web browsers but fails in Outlook. Flexbox layouts, CSS gradients, CSS animations, web fonts — all of these will break when the email arrives in Outlook Desktop.

If you receive a broken-looking signature from a Gmail user, that's why. It's not a problem you can fix on your end — the sender needs to update their signature to use Outlook-compatible code.

The safest approach if you communicate with a mixed audience (some on Outlook, some on Gmail, some on Apple Mail) is to build to the lowest common denominator — which means building to Outlook's constraints. A signature that works in Outlook will work everywhere. A signature that only works in Gmail will break for Outlook users.

This is exactly the philosophy behind NeatStamp's templates. They look good in every client, including Apple Mail, Yahoo Mail, and even older email clients, because they're built to the strictest compatibility standard first. That's also why it's worth using a dedicated tool rather than building your signature in Gmail's editor and hoping it survives the trip to Outlook.

Quick cross-client compatibility tips

  • Keep images under 100KB each — large images load slowly and some clients block them
  • Always set alt text on images so recipients see something if images are blocked
  • Use hex colors (like #0078d4) rather than CSS color names or rgb()
  • Keep total signature width under 500px for best mobile compatibility
  • Test by sending to a Gmail address and a Outlook address before deploying
  • Avoid animated GIFs — Outlook shows only the first frame

Related guides

Signature Editor

Build your signature free

Read guide

Gmail Signatures

Complete Gmail guide

Read guide

Outlook 365 Signatures

Microsoft 365 specific

Read guide

Apple Mail Signatures

Mac & iOS setup

Read guide

HTML Email Signatures

Full technical breakdown

Read guide

Business Signatures

Team & brand guide

Read guide

Signature with Logo

Logo setup tips

Read guide

Professional Signatures

Best practices

Read guide

Stop fighting Outlook. Let NeatStamp handle it.

NeatStamp generates table-based HTML with hosted images — the only format Outlook actually respects. Free forever. No account required.

Create Your Outlook Signature Free

Frequently asked questions about Outlook signatures

The questions that come up most often from people setting up Outlook signatures for the first time — or the fifth time after it breaks again.

What's the difference between classic Outlook and new Outlook for Windows?

Classic Outlook (also called Outlook Desktop) uses Microsoft Word as its rendering engine, which is why it breaks HTML signatures. New Outlook for Windows, rolled out from 2023 onwards, uses a web-based rendering engine similar to Outlook Web Access. Signatures behave better in new Outlook, but the installation process is different. In classic Outlook go to File → Options → Mail → Signatures. In new Outlook go to Settings (gear icon) → Accounts → Signatures.

Does an Office 365 subscription give you a different version of Outlook?

Not necessarily. Microsoft 365 (formerly Office 365) subscribers get access to the latest version of Outlook, but you might still be running classic Outlook desktop or the new Outlook depending on your settings. The distinction is between the app architecture (classic vs. new), not the subscription tier. You can tell which version you have: classic Outlook shows a File menu in the top-left; new Outlook shows a gear/settings icon in the top-right corner, more like a web app.

How do I add an HTML email signature to Outlook?

You can't paste raw HTML code directly into Outlook's signature editor — that's one of Outlook's biggest frustrations. Instead, you need to copy the rendered signature (not the code) and paste it. In NeatStamp, click 'Copy Signature' which copies the formatted version to your clipboard. Then go to Outlook's signature settings and paste with Ctrl+V. The formatting comes across without you ever touching HTML. For advanced cases, you can also edit the .htm files stored in %APPDATA%\Microsoft\Signatures\.

Why do my signature images show as attachments in Outlook?

This happens when images are embedded as base64 data URIs, which Outlook strips out and converts to attachments. Outlook desktop (classic) does not support base64-encoded images in signatures at all. The fix is to host images on a public URL and reference them with a standard <img src='https://...'> tag. NeatStamp handles this automatically — your logo and photo are hosted on NeatStamp's CDN so Outlook can load them properly.

Why does my signature look fine when I compose but broken when the recipient sees it?

There are a few causes. First, the recipient might be using a different email client that renders HTML differently. Second, some corporate email security gateways strip or modify HTML content. Third, if your signature uses CSS that Outlook ignores (like flexbox), it might look fine in your preview but fall apart when sent. Table-based layouts with inline CSS are the only truly safe approach for Outlook-to-Outlook and Outlook-to-Gmail scenarios.

My Outlook signature disappeared after an update. What happened?

Outlook updates, Windows updates, and profile migrations can all reset signature settings. Signatures are stored in %APPDATA%\Microsoft\Signatures\ and the registry key HKCU\Software\Microsoft\Office\[version]\Common\MailSettings. After an update, Outlook sometimes loses the pointer to your signatures even though the files are still there. Go back to File → Options → Mail → Signatures and re-select your default signature for new messages and replies.

Can I deploy the same signature to my whole team in Outlook?

Yes, but it requires admin work. For Microsoft 365 organisations, you can use Exchange transport rules to append a server-side signature or disclaimer to all outbound emails. For Outlook desktop, IT admins can push signatures via Group Policy using the registry key approach. NeatStamp Pro lets each team member generate their own correctly-formatted signature using a shared template, which is often simpler than server-side deployment for smaller teams.

Why doesn't Outlook support CSS properly?

Classic Outlook renders HTML emails using the Microsoft Word engine — specifically, the same engine that renders Word documents. Word was never designed to be a web browser, so it supports only a subset of HTML and CSS. It ignores most modern CSS including flexbox, grid, position:absolute, border-radius (partially), and CSS variables. It also has quirks around padding, margins, and font rendering. This is a deliberate design choice by Microsoft, not a bug, and it has been a source of frustration for email developers for over 15 years.

How do I set a signature on Outlook Mobile (iOS/Android)?

Outlook Mobile has its own separate signature settings, completely independent from Outlook Desktop. On iOS or Android, open the Outlook app, tap your profile picture, go to Settings → Signature. You'll get a plain text editor — Outlook Mobile doesn't support rich HTML signatures. For a basic formatted look, you can type your name, title, and contact details. For a proper HTML signature on mobile, consider using your phone's native mail app instead, which handles HTML signatures better.

Can I paste a rich text signature into Outlook's signature editor?

Yes, as long as you copy the rendered output (not raw HTML). When you use NeatStamp's 'Copy Signature' button, it copies the signature as rich text to your clipboard. Outlook's signature editor accepts this paste. If your paste comes out as plain text or broken, make sure you're pasting with Ctrl+V (not Ctrl+Shift+V or 'Paste as plain text'). Also check that you're pasting into the signature editor body area, not the name field.

Ready to create a signature that actually works in Outlook?

NeatStamp is free, requires no account, and generates Outlook-compatible signatures in 60 seconds. Every template is tested across Outlook 2016, 2019, 2021, Microsoft 365, and Outlook Web.

Create Your Free SignatureMicrosoft 365 specific guide →

No account. No credit card. Free forever.