How to Keep Your Email Signature When Switching Clients

No — your email signature does not move automatically when you switch email clients. Signatures are stored locally inside each application, not on the mail server, which means the moment you open a new client your HTML layout, logo, legal disclaimer, and per-account variants are all gone. Knowing how to move your email signature to a new email client before you uninstall the old one saves you from rebuilding from memory.

The good news is that the process is straightforward once you know where each client hides the HTML editor. The bad news is that the two most common failure modes — broken images and collapsed formatting — both happen after the move, not during it, so most people only discover them when a recipient mentions the problem. This guide covers the extraction step, the exact settings path in each major client, what breaks and why, and how to prevent it.

Before You Switch: Save Your Signature HTML#

The extraction step has to happen before you remove your accounts or uninstall the old client. Email signatures are not synced via IMAP or Exchange, and there is no export feature that most clients offer — once the app is gone, so is everything it stored locally.

Gather these four things before you do anything else:

• The full HTML source of each signature variant — find this in the client's signature settings and look for a source view or HTML toggle. Copy everything, including inline style declarations.
• All images used in the signature. Right-click and save each one to a folder, or locate them in the client's local application data directory. Images referenced by local paths or embedded as base64 data will not render in the new client.
• The sending address each signature variant is mapped to. If you have separate signatures for a personal account and two business accounts, write down the mapping now rather than trying to reconstruct it later.
• Any server-side or IT-managed footer text. Footers added at the Google Workspace or Microsoft 365 domain level are appended automatically on the server and will reappear without action — but footers you added manually need to travel with you.

How to Move Your Email Signature to a New Email Client#

1. 1

   Open the HTML editor in the old client

   Navigate to the signature settings in the app you are leaving — the exact path for each major client is in the table in the next section. Switch the editor to source or HTML view rather than the rich-text preview. Copy the full HTML, including all inline style attributes. Do not copy from the preview pane, which strips the raw markup.

2. 2

   Download and rename every image

   Save each image file to a dedicated folder and rename the files clearly — for example, company-logo.png and headshot.jpg. If your client embedded images as base64 data in the HTML, decode that data to a real file before moving on. Base64-embedded images add significant byte weight to every outgoing email and are less reliable than URL-referenced images.

3. 3

   Host the images at a stable public URL

   Upload each image to a location you control: your company website, a CDN, or a cloud storage bucket with public read access. Update the src attributes in your copied HTML to point to those public URLs. This step is the most commonly skipped, and it is the direct cause of the broken-image problem. A local file path or a base64 blob works only inside the app that generated it.

4. 4

   Open the HTML editor in the new client and paste

   Navigate to signature settings in the new app and switch to the HTML or source view before pasting. Paste your HTML into that raw field — not into the rich-text editor. If you paste into the visual editor, the client interprets your markup as text and wraps it in its own formatting, producing a garbled result. Save the signature before moving to the next step.

5. 5

   Assign each signature to the correct account

   If you have multiple mailboxes connected, find the per-account or per-sending-address setting and map each signature variant to the right address. Most clients have a dropdown in account settings or signature settings that lets you set a default signature per address. Do this before you send a single message.

6. 6

   Send a test from each account to an external address

   Send one email per account to an address at a different provider — for example, send from your Outlook account to a Gmail address you can open in both a browser and on mobile. Check that the logo renders, the fonts and spacing hold, and every link works. Testing internally or sending to the same client often hits a local cache and does not represent what a real recipient sees.

Where Each Client Hides Signature Settings#

The path to the HTML editor differs in every app. The table below gives you the direct route for the clients most commonly involved in a switch. Verify against the current version of each app, as settings menus move across major releases.

What to Do When the Signature Does Not Look Right#

Three failure modes account for nearly every signature problem after a client switch.

Images show as broken links or empty boxes. The cause is almost always a local file path or base64 blob in the src attribute that only worked inside the original client. Fix it by uploading the image to a public URL and updating the src. If the image breaks only on mobile but works in a browser, the host is likely blocking hotlink requests from mobile mail agents — move to your own domain or a CDN with permissive headers.

Fonts collapse to a default serif or monospace. Rich-text clients strip web font declarations and external style sheets on render because most recipients do not have custom fonts installed, and some clients sanitise all CSS that is not inline. The reliable approach is to inline every style attribute and to set font-family stacks that end in a system font: 'Helvetica Neue', Arial, sans-serif rather than a single named web font.

Table layout breaks or spacing is wildly off. Modern CSS layout — flexbox, grid, margin auto — does not survive the render pipeline of most email clients. If your signature was built with those properties, rebuild the structure in a nested HTML table layout. Every email design tool uses tables for a reason: they are the one layout primitive that has consistent support across clients dating back to Outlook 2010.

A Faster Way: Per-Account Signatures in One Place#

Migrating a signature once is a half-hour job. The problem compounds when you have six or eight accounts — different businesses, clients, or roles — each with its own HTML variant, phone number, and logo, and you need to keep them consistent across any client you use. Updating a phone number means editing the same block eight times, once per account per client.

AI Emaily (we build it) manages signatures at the account level, so each connected mailbox carries its own default signature and you make each change once. The signature editor accepts raw HTML, which means you can paste what you extracted from the old client and avoid rebuilding. Per-account assignment is a first-class setting rather than a workaround in a shared signatures list.

The 7-day free trial on Pro or Autopilot lets you connect your accounts and test this on real mail before committing — card required, $0 if you cancel before day 7. Size a plan on the pricing page, or read what the full client does on the homepage.