Outlook Signature Not Working? Here’s How to Fix It (2026)

1. Signature disappeared or won’t appear

This is the most common complaint after a Windows Update or Office update. The signature hasn’t been deleted — it’s almost always a matter of it being de-assigned from your account. Here’s the fix:

Signature file was deleted during the update

Outlook stores signature files in a specific location. On Windows, open File Explorer and navigate to:

(Paste that path into the File Explorer address bar and press Enter — Windows expands the %APPDATA% variable automatically.) You should see files named after your signature. If the folder is empty, your signature files were wiped.

If you had the signature elsewhere (another computer, a backup, a shared network drive), copy the .htm, .rtf, and .txt files back into this folder. Each signature consists of three files plus a folder with the same name plus “_files” (containing images).

If you no longer have the files, rebuild the signature in the NeatStamp editor, copy the HTML, and paste it into Outlook’s signature editor. The Outlook signature setup guide walks through this step by step.

2. Images showing as attachments

Recipients get an email from you with a paperclip icon and a file attached. The file is called something like “image001.png” or “logo.jpg”. Your signature image appears inline in some clients but as an attachment in others.

There are three different causes, and each has a different fix.

If you’re consistently seeing this issue across your organization, it’s also worth checking whether your Exchange admin has configured a policy that strips embedded attachments — some anti-spam configurations do this. For a fully Outlook-compatible signature format, see the HTML email signature guide.

3. Formatting stripped or broken

Your signature looks perfect in the preview, perfect in Gmail, but in Outlook it’s a jumbled mess — wrong fonts, colors gone, layout collapsed into a single column.

The reason is Outlook’s HTML renderer. Unlike every other email client, which uses a browser-based rendering engine, Outlook desktop uses the Microsoft Word rendering engine (since Outlook 2007). Word was designed for print documents, not the web. It supports approximately 25% of the CSS properties that Chrome or Firefox do.

CSS properties Outlook ignores entirely

What Outlook does support

The practical fix

Rebuild your signature using HTML tables for layout. Every column, every side-by-side element, every piece of structure should be a <table> with <tr> and <td> elements. All styles must be inline — Outlook strips <style> blocks in signatures.

Using style="display:flex" on a div to place your logo and contact info side-by-side? Outlook ignores flexbox. Replace that div with a two-column table. This is tedious to write by hand, which is why tools like NeatStamp exist — we generate table-based HTML automatically. The Outlook 365 guide and the main Outlook signature page have code examples.

4. New Outlook vs. Classic Outlook

Starting in late 2023, Microsoft began rolling out a completely new version of Outlook — sometimes called “New Outlook” — that replaces the classic .exe desktop app with a web-based version. In 2026, many organizations are in the middle of this migration, which creates specific signature problems.

Key differences for signatures

Common confusion: set up in Classic but not in New

If you set up your signature in Classic Outlook and then someone on your team switches to New Outlook, they won’t see the signature. The cloud-based New Outlook has no visibility into the local %AppData% signature folder. Both versions require independent setup.

How to identify which version you have

Classic Outlook has a ribbon-based UI with the familiar Office look. New Outlook looks similar to Outlook on the web — flat, clean, with a toggle in the top-right corner labeled “New Outlook” (you can switch back to Classic using that toggle if you’re in a transition period).

The Outlook 365 signature guide has specific instructions for the New Outlook interface alongside the Classic instructions.

5. Admin policies blocking signatures

In enterprise environments, IT administrators can restrict or override email signatures at the server level. This is more common than you might think — and it’s one of the hardest problems to diagnose because nothing appears broken on your end.

Exchange Transport Rules

Administrators can use Exchange Transport Rules (or Mail Flow Rules in Microsoft 365) to add, modify, or replace email signatures at the server level. These rules run after the email leaves your client, so they can overwrite whatever you set in Outlook. Symptoms include:

• Your signature shows in the compose window but recipients see a different one
• Your signature shows twice (your client-side one plus the server-side one)
• Your signature doesn’t appear for external recipients but works for internal

If you suspect a transport rule, contact your Exchange administrator or check the Microsoft 365 Admin Center → Exchange → Mail Flow → Rules. Solving this requires admin access — it’s not something you can fix from Outlook itself.

Group Policy restrictions

Group Policy can disable signature creation entirely or lock the signature settings. If the Signatures button in Outlook is greyed out or the Signatures window is inaccessible, Group Policy is the likely cause. Signs:

• File → Options → Mail → Signatures button is greyed out
• You can click Signatures but can’t edit or add new ones
• A new signature is applied automatically every time you restart Outlook

Solutions here require your IT department. You can raise a support ticket explaining the business need for a custom signature. Many organizations have exceptions for C-level executives or external-facing roles. If your company uses a third-party signature management tool like Exclaimer, there may be a self-service portal — the alternative to Exclaimer page covers this scenario in more detail.

6. Roaming signatures issues

Microsoft introduced “Roaming Signatures” in Microsoft 365 to sync signatures across devices. It’s a useful feature in theory but a significant source of confusion and conflicts in practice.

How roaming signatures work

When enabled, Outlook uploads your signatures to the Microsoft cloud (Exchange Online) and downloads them on any device where you sign in with the same Microsoft 365 account. Sounds ideal — but when something goes wrong, it’s hard to diagnose because the signature lives in the cloud, not locally.

Common roaming signature problems and fixes

7. Cached and stale signatures

You’ve updated your signature but Outlook keeps inserting the old version. Or you see a different signature in sent emails than what you set. This is almost always a caching issue.

Clearing the Outlook signature cache

OWA (Outlook Web Access) caching

If you use both the desktop app and Outlook Web (outlook.office.com), the web version has its own signature settings that are separate from the desktop. Stale signatures on the web version require you to update them in Outlook Web settings directly — go to Settings (gear icon) → View all settings → Compose and reply → Email signature.

8. Registry fixes (use only if other solutions haven’t worked)

Fix: Signature not auto-inserting in new messages

If the signature assignment in Outlook’s UI doesn’t stick (resets after restart), the registry may have a corrupt or conflicting value. Check:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\MailSettings

Values to check:
NewSignature = [Your Signature Name]
ReplySignature = [Your Signature Name]

If these values are missing or point to a signature name that no longer exists, either recreate the signature with the exact same name or update the registry values to match your current signature name. The version number (16.0) varies: Outlook 2016/2019/2021 and 365 all use 16.0; Outlook 2013 uses 15.0.

Fix: HTML signature being stripped to plain text

If Outlook is stripping your HTML signature to plain text, the mail format setting may have been reset at the registry level:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences

MailFormat = 2  (1 = Plain Text, 2 = HTML, 3 = Rich Text)

Set MailFormat to 2 for HTML. This is equivalent to the setting in File → Options → Mail → Compose messages in this format, but sometimes the UI change doesn’t persist while the registry change does.

Fix: Signatures missing after Office repair

Running an Office repair (Programs and Features → Microsoft 365 → Change → Quick Repair or Online Repair) can reset signature settings. After a repair, check the Signatures folder and reassign signatures in the UI. If signatures are gone, they may be in a backup — check %APPDATA%\Microsoft\Signatures for any .bak files.

9. Preventing future problems

If you’ve gone through this guide once, you probably don’t want to do it again. Here’s what I’d set up to prevent recurring issues.

• Back up your signature files. Copy the %APPDATA%\Microsoft\Signatures folder to a shared drive or cloud storage quarterly.
• Use externally hosted images, not base64. This eliminates the attachment bug and keeps email file sizes manageable.
• Use table-based HTML. If you rebuild your signature, generate it with NeatStamp's Outlook-proof output rather than writing flexbox-based HTML that will break.
• Set up signatures in both Classic and New Outlook if your organization is in a mixed state.
• Document your signature setup. A simple note with the signature name, account it's assigned to, and where the image files are hosted saves hours the next time something breaks.

If the Outlook complexity is getting to be too much to manage, one option is to look at a server-side signature manager. The alternative to Exclaimer page covers the available options, including some much cheaper alternatives to enterprise tools. NeatStamp’s Pro plan also handles multi-signature management. The free editor is the quickest way to regenerate a clean Outlook-compatible signature right now.

Frequently asked questions