Email Signature Not Working in New Outlook? Complete Fix Guide

First: are you actually on New Outlook?

Before going through the fixes, confirm which version you’re running. It matters because Classic Outlook and New Outlook store signatures in completely different places — a fix for one does nothing for the other.

Here’s how to tell:

• New Outlook has a toggle switch in the top-left corner of the window. If you see a small labeled toggle that says 'New Outlook' — that's New Outlook.
• New Outlook looks cleaner and more minimal. The ribbon toolbar is gone, replaced by a slimmer top bar. The layout resembles Outlook on the Web.
• New Outlook shows 'New Outlook' in the title bar on some builds.
• Classic Outlook has the full ribbon toolbar at the top with tabs like Home, Send/Receive, Folder, View.
• If you're not sure: go to Help in the menu. Classic Outlook shows a version number like '16.0.xxxxx'. New Outlook shows account info but not a build number in the same way.

Fix 1: Your signature didn’t migrate to New Outlook

This is the most common cause of a missing signature. Classic Outlook stores your signatures as files in this folder on your computer:

New Outlook ignores that folder entirely. It stores signatures in the cloud via your Microsoft 365 account. When you switch to New Outlook, it doesn’t import anything from your local machine — your old signature just doesn’t exist in the new system.

The fix is to recreate your signature from scratch in New Outlook:

Fix 2: Signature saves but doesn’t appear in emails

You set up your signature in New Outlook. You can see it in Settings. But when you open a new compose window — nothing. This is a known bug in New Outlook that Microsoft has been aware of since launch. It affects certain Microsoft 365 account configurations and tends to come and go with app updates.

The most reliable fix is to bypass the New Outlook app entirely and set your signature via Outlook on the Web (OWA):

This OWA workaround is also covered in our dedicated post on New Outlook signature problems with more details on the specific account types affected.

Fix 3: HTML formatting is broken

Your signature shows up, but something looks wrong — images are huge, fonts are different, the two-column layout has collapsed into one block, or the spacing is completely off. This comes down to how New Outlook renders HTML.

Classic Outlook used Microsoft Word’s rendering engine — with all its quirks and limitations. New Outlook uses a more browser-like renderer. That sounds like an improvement, but in practice it means signatures designed for Classic Outlook sometimes break in New Outlook, and vice versa.

The specific things that break most often:

• Images sized with width/height attributes on the <img> tag may scale unexpectedly. New Outlook often overrides these with CSS. Use inline style="width:Xpx; height:auto;" on the image tag, not just HTML attributes.
• Font-family declarations using system fonts sometimes fall back to a different default. Stick to web-safe fonts like Arial, Helvetica, Georgia, or Verdana and always specify a fallback: font-family: Arial, Helvetica, sans-serif.
• Table-based layouts generally survive the transition well, but tables using percentage widths (width='100%') can collapse on narrow views. Use fixed pixel widths on your outer table: width='600'.
• CSS classes and external stylesheets are stripped entirely. Everything must be inline styles — style="..." directly on each element.
• Padding and margin on <td> elements behave differently than Classic Outlook. Use cellpadding and cellspacing attributes on tables instead of CSS padding where possible.

The safest approach is to start with a signature generator that produces Outlook-safe HTML from the beginning, rather than trying to fix broken HTML manually. Our full guide on Outlook-compatible email signature HTML covers the exact markup patterns that work consistently across all Outlook versions.

Fix 4: Images showing as attachments

Recipients are getting your emails with a mysterious attachment — and it turns out to be your signature logo or headshot. This is one of the most embarrassing signature bugs because it looks unprofessional to everyone you email.

The cause is almost always embedded images — where the image data is baked into the HTML as a long base64 string that starts with data:image/png;base64,.... New Outlook doesn’t handle these. It converts them to file attachments instead of displaying them inline.

The fix is straightforward: host your images externally and reference them with a URL.

NeatStamp automatically hosts all signature images on our CDN — you never deal with base64 or self-hosting. This also keeps your emails lighter, which helps with signature saving issues caused by large payloads.

Fix 5: Signature resets after every update

You set up your signature. It works for a few days. Then New Outlook updates and it’s gone again — or reverted to an old version, or back to nothing. This is one of the most frustrating issues because the fix keeps undoing itself.

Microsoft has acknowledged this as a known issue in New Outlook’s early release channels. The root cause is that the app sometimes overwrites the cloud-stored signature settings on update, particularly when there’s a conflict between local cache and cloud state.

The most durable fix:

• Set your signature via OWA (outlook.office.com) rather than inside the New Outlook desktop app. The OWA write goes directly to the cloud backend and is less likely to be overwritten by app updates.
• After setting via OWA, clear the New Outlook cache. Close New Outlook, then navigate to %LocalAppData%\Microsoft\OneOutlook and delete the cache folder. Reopen New Outlook — it will re-sync from the cloud.
• Check if your organization uses roaming signatures centrally managed by IT. If so, your personal setting may be getting overwritten by a policy. See our guide on Outlook roaming signatures for the exact settings to check.
• If you're on the Beta Channel of Microsoft 365, consider switching to Current Channel or Monthly Enterprise Channel — those builds are more stable for signature handling.

The Outlook roaming signatures guide has a full walkthrough on how roaming signatures interact with New Outlook — and why the interaction sometimes causes this reset loop.

Fix 6: Can’t paste a rich formatted signature

You copy your beautifully formatted signature — with the logo, the colored name, the two-column layout — and paste it into New Outlook’s signature editor. What comes through is a plain text mess. Or the layout is there but all the fonts and colors are wrong. Or the paste just doesn’t work at all.

New Outlook’s built-in signature editor has noticeably weaker paste support than Classic Outlook. This isn’t a user error — the editor genuinely strips more on paste.

Two workarounds that actually work:

If you’re starting from scratch, the NeatStamp editor gives you clean HTML output that pastes correctly into OWA without stripping. You can also copy the rendered signature (not the HTML) from our preview and paste that directly — the formatting holds up better than pasting from most other sources.

Fix 7: Multiple signatures aren’t available

In Classic Outlook, you could save multiple signatures and pick one per email — one formal signature for client emails, a simpler one for internal threads, a plain text version for replies. New Outlook doesn’t support this the same way.

As of early 2026, New Outlook lets you save multiple signatures, but the compose window doesn’t show a dropdown to switch between them mid-email the way Classic Outlook did. You can change your default in settings, but that’s a global change — not a per-email choice.

Your options:

• Switch back to Classic Outlook for now. If you frequently switch signatures, Classic Outlook is still significantly better for this workflow. The section below covers how to switch back.
• Use OWA in a browser tab as your primary email client instead of the desktop app. OWA has more reliable multi-signature support.
• Change your default signature in Settings when you need a different one, then switch back. Annoying, but workable for occasional use.
• For company-wide scenarios — where different teams need different signatures — look at centralized signature management rather than per-user workarounds.

This limitation also affects Microsoft Teams email signatures and mobile — see our Outlook mobile signature guide for the current state of signature support across the Microsoft ecosystem.

How to switch back to Classic Outlook

Microsoft has been nudging — and in some cases forcing — users onto New Outlook. But as of early 2026, the switch back to Classic Outlook is still available for most users. Here’s how to do it.

The long-term solution

Every fix in this guide is a workaround for New Outlook’s current immaturity around signatures. Microsoft will improve it — but the timing is unpredictable, and your signature needs to work today.

The most durable approach is to build your signature in a format that’s already compatible with New Outlook from the start:

• Table-based HTML with fixed pixel widths — not flexbox, not percentage widths, not CSS grid.
• Inline styles only — no classes, no external stylesheets, no <style> blocks.
• Externally hosted images via HTTPS — no base64, no locally embedded files.
• Web-safe fonts with fallbacks — no Google Fonts, no custom font-face declarations.
• No JavaScript, no CSS animations, no SVG — these are stripped by every email client.

Writing this HTML by hand is tedious and error-prone. That’s the exact problem NeatStamp was built to solve.

If you want to browse tested templates before building from scratch, the signature template library has options that are pre-validated for New Outlook. Pick one, customize it, and copy the output directly into OWA.

Related guides

Frequently asked questions