You change your signature in Outlook at File > Options > Mail > Signatures on Windows, Outlook > Settings > Mail > Signatures on Mac, and Settings > Mail > Compose and reply on Outlook on the web. Each version keeps signatures in a different place because the desktop app stores them on your local machine, while web and Microsoft 365 store them encrypted in your mailbox. That split explains almost every confusion about missing, duplicated, or server-side signatures.
The paragraphs below trace how Outlook stores and injects signatures, why the wrong one appears on phones, what character limits and image rules actually apply, and how to fix the most common failures with a few precise steps.
How Outlook stores and injects a signature
A signature is not a single object. Outlook keeps the signature text and HTML in a file or folder, then copies that content into the message body when a compose window opens. That copy step is the mechanism behind most signature problems, because the copy happens at a specific moment and from a specific location.
On Windows, Outlook saves signatures as files in the user profile. Older builds used a folder named after the Windows version, and current builds use a folder under the AppData path for the user. Each signature exists as a text file, an HTML file, and a resource folder for images. When you edit a signature, Outlook rewrites those files, and when you open a new message, it reads the HTML file and pastes the markup into the body. The signature is therefore a snapshot, not a live link. If a file goes missing or the profile changes, Outlook cannot reconstruct it.
On Mac, Outlook stores signatures in the mailbox rather than only on disk, which is why Mac signatures can follow the account in some configurations. Outlook on the web and the new Outlook for Windows store signatures as mailbox settings on the server. The server copies the signature into a draft when the compose surface loads, and the signature is stored encrypted in the mailbox, settable through Outlook on the web or PowerShell.
This distinction matters because local files and server settings behave differently across devices. A signature you create on one Windows PC does not appear on another PC unless you copy the files or use roaming settings. A signature created in Outlook on the web appears in other clients that read the server setting, but only after those clients sync. The insertion is a copy operation, so changing a signature later never edits messages you already sent.
Plain-language version: Outlook does not link your message to a signature, it pastes a copy of the signature into the message when you start writing.
Quantified context: limits, sizes, and sync behavior
Signature constraints are modest, and the numbers explain why large graphics fail. Outlook on the web limits the signature to 4,000 characters, which includes spaces and any HTML markup the editor inserts. That limit is generous for text but tight once you add a logo, because inline images add markup weight even when the image itself is small.
Images are the usual failure point. A signature that embeds a photograph creates a message far larger than the text alone, and some mail systems reject or strip large signatures. A practical target is to keep the total signature, including the image, well under a few hundred kilobytes, because many corporate filters treat oversized messages as suspicious. A text-only signature typically stays under a few kilobytes. The character count and the byte count are different measurements, so a signature can pass the 4,000-character check and still be too heavy for a mail gateway.
Sync timing is another quantified factor. Server-stored signatures propagate to a client when that client refreshes its settings, which usually happens at sign-in or within minutes of a change. A user who edits a signature in the web app and immediately opens a desktop client may see the old signature until the client reconnects. The delay is usually short but nonzero, and it explains the "I changed it but nothing happened" report.
Consider the mobile apps, which are the most common source of mismatch. The Outlook mobile app does not read the desktop signature files. It reads the server-side signature when the account supports it, and it may apply a separate default. A user who sets a signature on a work PC and then sends from a phone can produce a message with no signature or a generic one. The fix is to set the signature in the web app, which the mobile app can inherit, and to check the per-account toggle in the mobile app settings.
One useful convention is to treat the signature as a small HTML document rather than a picture. A short line of text, a name, a title, and a phone number stays readable in plain-text clients and in replies where images are blocked. Percentages and byte thresholds vary by mail system, so treat any specific size as a rule of thumb, not a hard guarantee.
Edge cases: shared mailboxes, aliases, and roaming profiles
The standard File menu path fails in several common configurations. Shared mailboxes, delegate access, and multiple accounts each expose a different signature control, and the default path only edits the signature for the primary account.
Shared mailboxes are the most frequent edge case. When you open a shared mailbox, Outlook may apply the signature of your own account rather than the shared mailbox's signature, because the compose window inherits the default from the profile. To give a shared mailbox its own signature, you generally configure it through the mailbox owner's account or through the web app while the shared mailbox is selected. If your organization uses server-side signatures, the shared mailbox may have its own setting that overrides the local file, which produces a signature that appears only from certain clients.
Aliases create a subtler problem. A single mailbox can have several addresses, and Outlook does not automatically vary the signature by the address you send from. The signature is chosen by the account and the compose setting, not by the From address. If you need a different signature per alias, you must create multiple signatures and select the right one manually, or use server-side rules where your mail system supports them.
Roaming profiles and profile resets wipe local signatures. Because the Windows signature files live inside the user profile, a profile rebuild or a migration that does not copy AppData removes them. The server-stored signatures survive this, which is an argument for configuring signatures in the web app or through the organization's management tools rather than only on the desktop.
Red-flag warnings: A signature that appears in one client but not another usually means the signature is local-only, not server-stored. A signature on replies but not new messages, or the reverse, means the two compose settings differ. A signature that vanishes after a Windows update or profile reset usually means the local files were not preserved. A signature with a broken image usually means the image was deleted from its source folder or the client blocks remote content.
Misconceptions: what the settings do not do
The most persistent misconception is that editing a signature updates messages already sent. It does not. The signature was copied into the message body at compose time, and later edits cannot reach it. This is why two replies from the same person can carry different signatures, and why a legal disclaimer added after the fact never appears in earlier emails.
A second misconception is that the signature is a security or compliance control. It is formatting, not authentication. A signature can state a title or a department, but nothing in the signature proves the sender's identity. Organizations that need verifiable attribution use message headers, digital signing, or mail-flow rules, not signature text.
A third misconception concerns mobile. Many users assume the phone inherits the desktop signature automatically. The apps are separate clients with their own settings, and the mobile signature frequently defaults to a short "Sent from my phone" line. To align them, set the signature in the web app and verify the mobile app setting.
A counterintuitive detail: the new Outlook for Windows and Outlook on the web share the same server-stored signature setting, so a change in one can appear in the other. Classic Outlook for Windows and Outlook for Mac historically kept signatures locally, so they may not reflect the same change. Two clients from the same vendor can therefore disagree about which signature is "correct."
Plain-language version: think of the signature as a stamp you press onto each new message, not a label attached to your account.
Comparison of signature locations by client
| Client | Where to change it | Storage location | Applies to shared mailboxes |
|---|---|---|---|
| Classic Outlook for Windows | File > Options > Mail > Signatures | Local user profile files | No, uses profile default |
| New Outlook for Windows | Settings > Accounts > Signatures | Mailbox settings on server | Partly, depends on account selection |
| Outlook for Mac | Outlook > Settings > Mail > Signatures | Mailbox and local store | Limited, per account |
| Outlook on the web | Settings > Mail > Compose and reply | Encrypted mailbox setting | Yes, when mailbox is selected |
| Outlook mobile | Settings > Signature per account | Server setting where supported | Depends on account type |
| Microsoft 365 admin tools | PowerShell or admin center | Server-side, organization scope | Yes, with policy configuration |
Use this table as a map, not a guarantee. Menu labels shift between builds, and some organizations hide or redirect settings through policy. If the expected menu item is absent, the cause is usually a policy or a client that does not support the setting, not a missing feature.
Timeline: what happens from edit to send
| Stage | What occurs | Typical timing |
|---|---|---|
| Edit signature | Client writes signature files or server setting | Immediate |
| Save | Files rewritten or setting saved to mailbox | Immediate |
| Client refresh | Other clients read the new setting | Minutes, or at sign-in |
| Compose window opens | Signature is copied into the message body | At open |
| Switch account or alias | Default signature may change or stay | At selection |
| Send | Message carries the copied signature as fixed text | At send |
| Later signature edit | No effect on already sent or drafted content | Never retroactive |
| Profile reset or migration | Local signature files may be lost | At reset |
The practical takeaway from this sequence is that the critical moment is compose, not send. If the wrong signature appears, the fix happens before you type, by choosing the correct signature from the signature menu in the compose window or by correcting the default for that account.
Practical actions: exact steps and thresholds
To change a signature, open the client that matches your setup and follow the path for that version. Then verify the result by composing a test message from the account you actually use, including any shared mailbox.
On classic Outlook for Windows, open File, then Options, then Mail, then Signatures. Create or edit the signature and assign it to new messages and replies separately. Those two assignments are independent, so a signature set only for replies will not appear on new messages.
On the new Outlook for Windows, open Settings, then Accounts, then Signatures. Choose the account, edit the signature, and set the default for new messages and replies. Because the setting is stored on the server, verify it in the web app as well.
On Outlook for Mac, open Outlook, then Settings, then Mail, then Signatures. Create the signature, then use the "Choose default signature" controls to map it to the account. Confirm the mapping for new messages and replies.
On Outlook on the web, open Settings, then Mail, then Compose and reply. Enter the signature, keep it under the 4,000-character limit, and save. This is the setting that mobile clients and the new Outlook can inherit.
For shared mailboxes and aliases, configure the signature while the shared mailbox or alias is selected, and test by sending from that address. If the wrong signature appears, the default is attached to the wrong account.
Keep a text-only fallback. Many recipients read mail in clients that block images, and a signature that depends on a logo becomes an empty box. A short plain-text line always renders.
Check the character count before adding graphics. The 4,000-character limit counts markup, and a single pasted image can consume a large share of that budget. If the signature is rejected or truncated, remove the image first.
Plain-language version: set the signature where the account lives, then send yourself a test from that account to confirm it.
Limitations and what this guide cannot resolve
Signature behavior depends on the client version, the account type, and the organization's policy, and these change over time. Menu names and locations shift between builds, and some settings are controlled centrally rather than by the user. This article describes the stable mechanism, the copy-on-compose model and the local-versus-server storage split, which does not change even when the menus move.
The specific character limit, the exact storage path, and the availability of server-side signatures vary by product and plan. Treat the 4,000-character figure as a web-app limit that may differ elsewhere, and treat the size guidance as a practical range rather than a hard threshold. Your mail administrator can confirm which settings your organization manages and whether signatures are overridden by policy.
Nothing here is legal, compliance, or security advice. A signature is formatting, not authentication, and any disclaimer or attribution requirement should be confirmed with the people responsible for your organization's email policy. For a definitive answer about your own account, check the client's current settings and, where policy applies, ask your administrator.