Restore Outlook signature after switching providers

Short answer: recover the signature files or copy the signature from a sent message and paste or import that HTML into the Outlook client you now use. If you have a device or backup containing the old profile, copy the signature block or the Signatures folder, then paste or place those files into the correct client and set them as the default. If that fails, extract the HTML from a sent message or ask IT for the tenant/template copy.

Prerequisites

You need three things before you start: access to the old device or backup, permission to browse your local profile files, and the Outlook client you will send from installed and signed in.

• Access to the device or backup with the old Outlook profile or sent messages.
• Permission to browse your user profile files (local account access).
• The Outlook client you will send from installed and configured: New Outlook for Windows, classic Outlook for Windows, Outlook for macOS, or the web client.

Quick 10-minute checklist (get your signature back now)

Follow these short steps to restore a signature from a sent message. Most users finish in 10–15 minutes.

1. Open Sent Items and find a recent message that used the old signature.

2. Open that sent message and select the signature content in the message body, then Copy.

3. Open the Outlook client you will use now.

4. Open the signature editor for that client and create a new signature. Paste the copied content into the editor and Save.

5. Assign the signature as default for new messages and replies/forwards for the account you send from.

6. Send a test message to yourself and to an external address to verify appearance.

If this works, you’re done. If not, continue to the file-recovery steps below.

If quick check didn't work: locate and recover signature files on your device

Start by checking the standard Signatures folder on Windows for .htm, .rtf, .txt files and an image subfolder.

%appdata%\Microsoft\Signatures

If you use New Outlook for Windows, open the client settings editor first (Settings > Compose and reply / Signatures). New Outlook often reads the legacy Signatures folder for compatibility. If you see signatures in the editor, export or copy them now.

On macOS, check the Outlook profile container for signature files. Try these common paths:

~/Library/Group Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/Main Profile/Signatures
~/Library/Group Containers/UBF8T346G9.Office/Outlook/Signatures

Copy the entire Signatures folder or the specific .htm/.html plus its image subfolder to a safe backup folder on your current device.

Importing or recreating the signature in each Outlook client and account type

Here is how to import or recreate the signature in the client you use now. Follow the steps for your client exactly.

New Outlook (Windows) — fastest import method

1. Open New Outlook and go to Settings > Compose and reply.

2. Create a new signature, click into the editor, then Paste your copied HTML or the contents of your .htm file. Save.

3. Set the signature as default for new messages and replies/forwards for the account you use.

Classic Outlook for Windows (desktop) — import using files

1. Close Outlook.

2. Copy the saved signature files (.htm, .rtf, .txt) and the image folder into the Signatures folder.

%appdata%\Microsoft\Signatures

3. Start Outlook, go to File > Options > Mail > Signatures, select the imported signature, and assign it to the correct account.

Outlook for macOS

1. Open Outlook > Preferences > Signatures.

2. If you have the original .html, open it in a browser, Select All and Copy. In the signature editor click New and Paste.

3. Assign the signature to the account by dragging it or using the default settings.

Outlook web client

1. Sign in to the web client and go to Settings > View all Outlook settings > Mail > Compose and reply.

2. Create a new signature and Paste the HTML content. Reformat if the web editor strips advanced styling.

3. Check the boxes to include the signature for new messages and replies/forwards if you want automatic insertion.

Outlook mobile (iOS and Android)

1. Open the Outlook mobile app > Settings > Signature for the account.

2. Paste plain-text or simple HTML. Mobile apps accept limited formatting; complex HTML with external images usually won’t render.

Notes for account types and shared mailboxes:

• IMAP/POP: signatures are local to the client. Restoring the client signature is sufficient for mail sent through the client’s SMTP.
• Exchange / Microsoft 365: tenant-level transport rules or third-party gateways can append or replace signatures. Restoring a client signature may not change the final outbound footer.
• Shared mailboxes: when sending as a shared mailbox, client-side signatures may not apply. Consult IT or create a signature assigned to the sending identity.

Fix images, fonts, and account-related quirks; verification tests

Start with common image problems, then confirm fonts and fallback text.

1. If images break after restoring, reinsert them using the signature editor so they are embedded rather than linked.

2. On Windows, ensure the signature's image subfolder sits next to the .htm file in the Signatures folder you copied into.

%appdata%\Microsoft\Signatures

3. If the original HTML used CID references and images show as attachments, remove the raw HTML and reinsert images with Insert > Picture in the editor.

Fonts and styling

• Use web-safe fonts: Arial, Calibri, Helvetica, Georgia, Times New Roman. Recipients without a custom font will see a substituted font.

HTML vs plain text

1. Keep a plain-text fallback version of the signature. On Windows, keep the .txt file in sync with the .htm.

Verification tests (do these after restoring)

1. Compose a new message in the client and confirm the signature appears in the compose window.

2. Send to yourself and open the received message in both web and external mail clients to verify display and images.

3. Send to an external contact and ask for feedback about images and styling.

4. Test reply and forward behavior to confirm the reply signature or shortened format works as expected.

If issues persist, edit the HTML in a text editor keeping styles inline, or rebuild the signature using the editor's controls.

Fallbacks, IT traps, and when to involve IT

If local files are gone, you can still recover the HTML and images from a sent message or ask IT for the template.

1. Extract the signature HTML from a sent message. Open the sent message and Save As an HTML file. Then open that file in a browser or editor and copy the HTML and embedded images.

2. If Save As doesn’t preserve images, view the message source or open it in a browser (if your client supports that) and save embedded images from the message view.

3. If the signature was provided centrally by IT via a transport rule or GPO and no client copy exists, request the official HTML template from IT.

When to involve IT or open a support ticket

• Open a ticket if your tenant enforces or injects signatures via Exchange transport rules, Azure AD mail flow rules, or a gateway — tenant-level rules can override client signatures.
• Ask IT if your profile is roaming and files were lost across devices; IT can check roaming-profile backups or folder redirection.
• In shared mailbox or delegated send scenarios, involve IT when signatures won’t apply to the shared identity or when send-as behavior strips client signatures.

Prevention checklist

• Export and back up each signature's .htm/.html, .rtf, .txt files and the image subfolder to versioned cloud storage or a secure backup.
• Keep a plain-text copy of the signature in a secure notes app you control.
• If you manage multiple users, use a central template repository or a signature management tool for tenant-level templates.
• After client or OS upgrades, verify the Signatures path and test a sample signature; paths and UI labels can change with updates.

Conclusion

If a quick copy from Sent Items works, that’s usually fastest. If not, recover the Signatures folder from the old profile or extract HTML from a sent message. When tenant rules or shared-mailbox behavior block client signatures, involve IT. Back up your signature files after you restore them.