Your signature is not showing in Outlook because the client is not inserting the signature file into the message you are composing. That usually means the signature is set as the default for one account but not the active one, it is configured for New Messages but not Replies and Forwards, or the signature file itself failed to load from the Signatures folder. Outlook does not silently drop a signature it is set to insert; it falls back to whatever default assignment applies to the message class and account in use.
This distinction matters because Microsoft's support documentation and most troubleshooting guides treat "signature missing" as a single fault. It is actually two separate pipelines: a storage and assignment layer that tells Outlook which HTML file belongs to which account and message type, and a rendering layer that decides whether that file can be displayed. Almost every case traces to one of the two, and the fix differs completely depending on which layer failed.
Signature storage and assignment mechanics
Outlook does not store signatures as text inside the mailbox. Each signature is a separate file in a local folder, usually a single HTML file with its assets, and the account settings store only a pointer to that file plus flags for three message classes: new messages, replies and forwards, and the signature that should appear on each. On Windows, that pointer lives in the Outlook profile under the user's AppData roaming folder. On Mac, the Signatures folder sits inside the Outlook profile in the user's Library.
The important consequence is that the pointer and the file can drift apart. If the HTML file is renamed, moved, or blocked, the pointer still exists but resolves to nothing, and Outlook composes the message without a signature rather than throwing a visible error. This is why a signature can vanish after a profile migration, a Windows user profile change, or a restore from backup: the settings were copied but the file path no longer matched.
The second mechanical detail is that Outlook inserts the signature at compose time, not at send time. The signature is pasted into the message body as soon as the compose window opens. Anything that interferes with that paste operation — a blocked script, a protected view, a slow disk, a missing file — produces a message that already lacks the signature before you type a word.
Why replies and forwards behave differently
The three message classes are assigned independently. A signature set for New Messages does not automatically apply to Replies and Forwards, and vice versa. This is the single most common reason a user sees signatures on brand-new emails but not on replies, and it is not a bug. Microsoft's own support documentation describes the setting as a per-account, per-message-type assignment, and it defaults to "None" for replies in many fresh profiles.
There is a counterintuitive wrinkle here. Even when a reply signature is assigned, Outlook may not insert it into a thread where the conversation has already started. The client has to decide whether to append the signature below the quoted text or above it, and behavior changes with conversation view settings and with the "close original message" option. The practical result is that reply signatures can appear inconsistently across a single thread, which users read as random failure.
Plain-language version: Outlook treats a new message and a reply as different documents, and the signature setting must be turned on separately for each one.
A timeline of how a signature disappears
The time course of a missing signature is useful because it narrows the cause. Signatures rarely fail at random; they fail at identifiable moments.
| Stage | What happens | Typical symptom |
|---|---|---|
| Edit or rename | The HTML file is renamed or relocated | Signature missing from every new message |
| Profile change | Settings point to an old path | Signature missing for one account only |
| Compose opens | Insertion is attempted | Blank body, no error shown |
| Send | Message leaves without signature | Signature absent in Sent Items too |
| Sync | Other device composes the message | Signature missing on phone or web |
| Recovery | Profile rebuilt or restored | Some accounts keep signatures, others lose them |
The sent-items row is diagnostic. If the signature is missing from the message you sent as well as from the compose window, the insertion never happened. If it appears in Sent Items but the recipient does not see it, the problem is on the receiving side or in the message format, not in Outlook's assignment.
Quantified context: how often this is an assignment problem
The distribution of causes is skewed heavily toward configuration rather than corruption. In practice, the large majority of "signature not showing" reports resolve to one of three conditions: no signature assigned to the active account, no signature assigned to replies and forwards, or a signature file that no longer exists at the stored path. Actual file corruption is uncommon, and mailbox-side signature loss is rare in desktop Outlook because signatures are not stored in the mailbox at all.
Microsoft's documentation notes that roaming signatures, introduced to synchronize signatures across devices, changed where signatures are stored for some account types and added a dependency on cloud sync. That dependency is a legitimate failure point: if sync has not completed, a signature that exists on one machine may not yet exist on another. This is a design change, not a defect, and it explains the modern pattern of signatures appearing on a laptop but not on a newly configured desktop.
The practical threshold is simple. If the signature is missing on exactly one device and present on another, suspect a sync or profile-layer problem. If it is missing on every device for one account, suspect assignment. If it is missing for every account on one device, suspect the profile or the Signatures folder itself.
Edge cases that break insertion
Several conditions interfere with rendering even when assignment is correct.
Protected View. Messages opened in Protected View can suppress inserted content until the view is dismissed. Add-ins. Third-party add-ins that modify the compose window can overwrite or strip inserted signatures. HTML dependencies. Signatures built from web pages often reference images or fonts that fail to load, producing a blank or partial signature. Account mismatch. On profiles with multiple accounts, the compose window may default to the wrong From address and apply the wrong signature, or none. Read-only or restricted folders. Security software that blocks writes to AppData can prevent the file from being read. New Outlook and web clients. These render signatures differently from classic desktop Outlook and may not carry over complex HTML.
The professional caveat is worth stating plainly: a signature that looks correct in the editor is not proof it will render. The editor and the compose window use different rendering paths, so complex tables, external images, and embedded fonts can pass the editor preview and still fail at compose time. Test by actually creating a new message, not by inspecting the signature editor.
Common misconceptions
The most persistent misconception is that Outlook stores signatures in the mailbox, so a missing signature implies data loss. Desktop Outlook stores signature files locally, which is why a signature can survive a mailbox rebuild and still disappear after a Windows profile change. The two events are unrelated, and users often conflate them.
A second misconception is that a signature set on the web version automatically appears in desktop Outlook. The platforms have separate storage models for some account types, and assignment does not always propagate. Setting a signature in Outlook on the web is not a guarantee for the desktop client, and the reverse is also true.
A third is that replies inherit the new-message signature. They do not. It is a separate assignment with its own default.
Practical actions and thresholds
Work from the cheapest check to the most invasive, and stop when the symptom changes.
Open Settings, then Accounts, then Signatures, and confirm a signature is selected in the drop-down for the specific account you are sending from. Check all three message classes, not just new messages. Create a brand-new message and a reply to an existing thread. If one has the signature and the other does not, the cause is assignment, not corruption, and you are done. Locate the actual HTML file in the Signatures folder and confirm it exists and opens in a browser. A file that will not open in a browser will not render in Outlook. If signatures disappear on one device only, check sync status and sign out and back in to force a refresh before rebuilding anything. If every account on one device lost signatures, rebuild the Outlook profile rather than recreating signatures one by one. If the signature renders in the editor but not at compose, disable add-ins one at a time and retest; most rendering failures clear when the offending add-in is off.
The threshold that matters most: do not recreate signatures until you have confirmed the file still exists. Recreating while the old pointer is intact can produce duplicate entries and make the assignment screen harder to interpret.
Limitations and what this cannot tell you
This explanation covers the stable mechanics of signature storage, assignment, and insertion in desktop Outlook. It cannot account for organization-specific policy that disables signatures centrally, nor for tenant-level settings that override user configuration, because those vary by deployment and are not publicly standardized. Signature rendering also depends on the recipient's email client, which you cannot inspect.
If your signature problem involves a managed work account, contact your IT administrator before changing profile settings; some configurations are locked by policy. For personal accounts, the steps above cover the documented behavior, but outcomes are not guaranteed for heavily customized HTML signatures. This article is general educational information about software behavior, not a support contract or a guarantee that any specific step will restore your signature.