Outlook signature missing after device switch — quick fixes

Short answer: your signature is missing because it was stored only on the old device or in a different Outlook client and wasn’t copied to the new one, or because an organization policy applies a server-side signature that replaces or hides client signatures. Follow the steps for the Outlook client and account type you use to find and restore it.

Symptom — what you see and when it happens

You can quickly check whether the problem is a missing client file or a server policy.

You open Outlook on a new computer or phone and the signature you used before is gone from the editor and from new messages. You may see an empty signature list, a generic footer added only when sending, or different signatures for new messages and for replies.

• Observable items: signature editor shows no entries; composing a new message shows no signature; replies show no signature or a different one; Sent Items lack the expected signature.

• When this appears: right after setting up a new device, after reinstalling Outlook, or after switching between desktop, Mac, web, and mobile clients.

Before you start (scope, safe checks and prerequisites)

Quick answer: confirm account type and access to the old device, and back up before you change files.

This guide covers Outlook desktop on Windows and Mac, Outlook on the web (OWA), and Outlook mobile (iOS/Android) used with Exchange/Exchange Online (Microsoft 365), IMAP, or POP. Do these checks first:

• Confirm which account you signed into in the client (work/school Microsoft 365 vs personal).
• Check whether the old device is still available and accessible.
• Back up any existing signature files on the new device before overwriting them.
• Note whether you have admin rights and whether your org manages signatures centrally.

• Stopping condition: stop and contact IT if the organization enforces server-side signatures or transport rules; do not change server rules yourself.

Where Outlook stores signatures (client vs server — quick reference)

Short answer: some signatures live on the device, some live in the mailbox, and admins can apply server-side signatures.

• Outlook for Windows (desktop): signatures are client-side files in your Windows profile under \%appdata%\Microsoft\Signatures. Each signature usually has three files (.htm, .rtf, .txt) plus an images folder.

• Outlook for Mac (desktop): signatures live in the user Library and are managed by Preferences. They don’t copy automatically between Macs unless you copy the Library items or use a migration tool.

• Outlook on the web (OWA): signatures are stored in the mailbox and follow you to any device where you sign into that mailbox.

• Outlook mobile (iOS/Android): signatures are per-app and per-account and don’t reliably sync between devices.

• Exchange / Microsoft 365 (admin-controlled): administrators can apply server-side signatures or transport rules that append or replace signatures at send time. Those are stored on the server and do not rely on client files.

If your signature existed only as client files on the old device, it will not appear automatically on the new device.

Which signature will Outlook use for a message

Direct answer: Outlook inserts a signature based on client defaults unless a server rule appends or overrides it.

• General behavior:
• Each client keeps a default signature for new messages and a separate default for replies and forwards.
• If a server-side signature is applied by an Exchange/Microsoft 365 transport rule or admin policy, the server may append or override the client signature at send time.

• How to check:

1. Open the client signature settings and note the defaults for "New messages" and "Replies/forwards." Empty fields mean none will insert automatically.
2. In OWA, check Compose and reply to see the mailbox-stored signature settings.
3. If recipients see a different footer, the server likely added it after send.

Knowing which source (client vs server) is active tells you whether to restore local files or contact your admin.

Restore steps — detect-and-repair flow

Short answer: check the client first, then copy files or recreate the signature depending on where it was stored.

Do the safe checks in "Before you start" first. Back up before replacing files.

Outlook for Windows (desktop)

1. Open Outlook and go to File > Options > Mail > Signatures to check whether any signatures are listed.
2. If the dialog is empty and the old PC is available, copy the Signatures folder from the old profile.

%appdata%\Microsoft\Signatures

3. Paste the entire Signatures folder into the same path on the new PC.
4. Restart Outlook.

Expected result: signatures appear in the Signatures dialog and insert according to the defaults.

What it means if it fails: permissions, a profile mismatch, or an Exchange policy may hide client signatures. Log steps and escalate to IT.

Outlook for Mac (desktop)

1. In Outlook, open Preferences > Signatures to check for entries.
2. If empty and the old Mac is available, copy the signature items from the old user Library to the new one.

3. Restart Outlook.

Expected result: signatures show in Preferences and apply when composing.

What it means if it fails: the Library path was incorrect or the files are incompatible. Recreate the signature in Preferences.

Outlook on the web (OWA)

1. In a browser, sign into the same mailbox and open Settings > Mail > Compose and reply.
2. If the signature exists there, copy it or confirm defaults for new messages and replies.
3. If it’s empty but the old device still has OWA access, open OWA there and copy the HTML from the editor into the new OWA editor.

What it means if it fails: the mailbox did not have a saved signature; recreate it in OWA or ask IT if a server policy applies.

Outlook mobile (iOS/Android)

1. Open the Outlook mobile app, tap Settings > Signature (or account > Signature) and check the entry for that account.
2. Re-type or paste a simplified version; mobile clients often do not support complex HTML or embedded images.

What it means if it fails: the mobile app requires plain-text or simplified HTML; keep a mobile-friendly copy to paste.

Exchange / Microsoft 365 with admin-controlled signatures

1. Check OWA for a mailbox signature and whether a corporate footer appears on sent messages.
2. If you suspect server-side rules, contact your admin. Do not modify transport rules yourself.

What it means if it fails: if admins enforce a signature, client changes may be ignored. Ask IT whether they can restore a client-side copy or adjust the server policy.

Recreating signatures with images and fonts

1. Open the old signature in the old device or a saved HTML file and copy the HTML into the new client's editor.
2. Save image files locally and reinsert them via the signature editor so links point to local copies.

Verify — how to confirm the fix worked

Answer: compose, reply, and send a test message to confirm defaults and rendering.

1. Compose a new message and check the default signature used for new messages.
2. Reply to an existing message and confirm the reply signature is correct.
3. Send a test email to yourself or a colleague and open the received message in a web client to check images and HTML rendering.

Expected output: signature text, images, and links render correctly and match the defaults you set. If images are broken, reinsert them from local files.

Troubleshooting log for IT escalation

Short answer: collect client and account details, copies of any files you moved, and screenshots before contacting IT.

Gather this information:

• Client type and exact version (for example, Outlook for Windows build number or Outlook for Mac version).
• Account type: Exchange/Exchange Online (Microsoft 365) vs IMAP vs POP.
• Whether the old device is available and whether the Signatures folder or exported HTML exists.
• Screenshot of the signature settings page in the client and in OWA.
• Exact path of any signature files you copied and the timestamped backup location.
• Steps you tried and results (for example: copied \%appdata%\Microsoft\Signatures, restarted Outlook, checked OWA).

Give this log to IT so they can check mailbox-level settings, transport rules, or group policies that affect signatures.

Keep it from happening again — backup and migration best practices

Short answer: back up local signature files and prefer mailbox-stored signatures when you move between devices.

Practical steps:

• Backup local signatures before retiring a device. On Windows copy \%appdata%\Microsoft\Signatures; on Mac copy the user Library signature items.
• Prefer OWA signatures for mailboxes you move between devices; mailbox-stored signatures follow the account.
• If you need identical signatures across many desktops, ask your admin about centrally deployed signatures or a distribution script that places files into user profiles.
• For mobile, keep a plain-text or simplified HTML signature to paste into the app because mobile clients limit HTML support.

Conclusion

If you know which client and account type you used on the old device, pick the matching restore path above. If the signature lived only on the old device and that device is gone, recreate the signature or ask IT whether they have backups. If the organization controls signatures, contact your admin — changing server rules yourself will not help and can create compliance issues.