Stop Using Plain Text — Outlook *Does* Support HTML Signatures (Here’s How)

The first thing most people do when they paste an HTML signature into Outlook is copy-paste it directly into the signature editor. That almost always breaks links, images, and formatting — especially if they’re using the new Outlook app or Outlook on the web. I’ve seen this trip up even experienced users who’ve built clean HTML footers for years in Gmail or Apple Mail.

The Short Version

Method	Where It Works	Pros	Cons
Outlook Desktop Signature Editor	Classic Outlook (2016/2019/365)	No coding needed. Built-in image upload. Works offline.	Strips inline CSS. Ignores <style> blocks. Breaks relative paths.
HTML File + Insert as Text	Classic Outlook only (not new Outlook or OWA)	Preserves full HTML/CSS. Supports background colors, flex layouts, icons.	Requires manual file management. Fails silently in new Outlook. Images must be embedded or hosted externally.
Outlook Web App (OWA) + Paste as Plain Text	Outlook on the web (office.com), new Outlook (Windows)	Fast. No file handling. Works across devices.	Only basic HTML survives. No tables, no <div>, no custom fonts. Images must be pasted in separately.
Exchange Admin Center (EAC) Signatures	Enterprise only (Microsoft 365 E3/E5)	Centrally managed. Applies to all replies/forwards. Supports dynamic fields (e.g., %displayName%).	Requires admin rights. No per-user customization. Not available in business plans.

Method 1: Outlook Desktop Signature Editor

This is the method you’ll find in File > Options > Mail > Compose messages > Signatures.... Click New, give it a name like "Marketing Team – HTML", then paste your HTML code into the editing box. Don’t do that. Instead: open your HTML file in a browser (like Edge or Chrome), select the entire rendered signature, and copy it as visible text — not the source code. Then paste it into the Outlook editor. This bypasses Outlook’s aggressive sanitization of raw HTML tags. This works because Outlook doesn’t parse HTML — it treats the signature field like a rich-text editor. So what you paste is interpreted as formatted text, not code. You lose <style> blocks and JavaScript, but you keep bold, links, line spacing, and even basic tables. It supports images — but only if you insert them via the Insert > Picture button inside the editor. Pasting an <img src="logo.png"> tag won’t work. And yes, this takes longer than Ctrl+V — but it’s the only way to get consistent results in classic Outlook without breaking everything. One surprising tip: if you need a colored background behind part of your signature, don’t use CSS background-color. Use a 1×1 pixel GIF with that color, stretched to width/height, inserted as an image. Outlook renders those reliably — even in replies.

Method 2: HTML File + Insert as Text

This method works only in classic Outlook (2016, 2019, and older Microsoft 365 desktop apps). It does not work in the new Outlook app or Outlook on the web. First, save your signature as a plain HTML file — say, marketing-signature.html. Make sure all images are either embedded as base64 (yes, Outlook accepts those) or hosted on a reliable CDN. Then go to File > Options > Mail > Compose messages > Signatures..., click New, and instead of typing anything, click Insert > File (or press Ctrl+K and choose “Insert as Text”). Navigate to your HTML file. Outlook reads the file and imports it as rich text — preserving tables, inline styles, and even @media queries (though they’re ignored on mobile clients). You’ll notice Outlook adds extra spacing above headings. That’s normal. To fix it, edit the HTML file and add margin-top: 0; to your <h3> or <p> tags. This took me three days to figure out originally. Limitation: every time you update the signature, you must re-import the file. There’s no auto-sync. And if you switch to the new Outlook app? Your signature vanishes — replaced by a generic plain-text fallback.

Method 3: Outlook Web App + Paste as Plain Text

In Outlook on the web (outlook.office.com) or the new Outlook for Windows, go to Settings (gear icon) > View all Outlook settings > Compose and reply > Email signature. Paste your HTML-rendered signature there — but only after viewing it in a browser and copying the visible output (right-click → “Copy” or Ctrl+A, Ctrl+C). Don’t paste source code. This method strips <table>, <div>, and most class attributes. What survives: links, bold/italic, line breaks, and basic lists. You can paste images separately — just drag them in or click the image icon. Surprising fact: Outlook on the web handles emoji better than desktop Outlook. If your signature includes 📞 or 📍, they render cleanly — no boxes or question marks. Also: the new Outlook app (released late 2023) uses the same backend as OWA, so signature behavior is nearly identical. But — and this is critical — it doesn’t let you set different signatures for new messages vs. replies/forwards. That option exists only in classic Outlook.

Which Should You Choose?

Use this table to pick the right method based on your setup. Check off your situation, then follow the recommendation.

Your Situation	Best Method	Why
You use classic Outlook desktop (2019 or older 365)	HTML File + Insert as Text	Gives you full control over layout, colors, and responsive elements.
You’re on the new Outlook app or OWA only	Paste as visible text in Settings	No other option works reliably — and it avoids broken markup.
You manage 50+ users and have M365 E3/E5	Exchange Admin Center (EAC)	Ensures brand consistency and updates all users at once.
You switch between desktop and web daily	Desktop Signature Editor + manual sync	Build once in desktop, then copy-paste the rendered version into OWA settings.
You send mostly internal emails (no external clients)	HTML File + Insert as Text	Internal Exchange servers handle richer HTML better than Gmail or Yahoo.
You include legal disclaimers or compliance text	EAC or Desktop Signature Editor	Both preserve line breaks and font size reliably — unlike OWA’s paste method.
You use shared mailboxes or delegate access	Desktop Signature Editor	Signatures apply per-user profile, not per-mailbox — so delegates see their own, not the owner’s.