The fastest way to edit a signature in Outlook is to open Settings (or Options), go to the signature editor, change the text, and save—but the exact path depends on which app you're in. Outlook on the web and in the new Outlook for Windows use Settings > Accounts > Signatures; classic Outlook for Windows uses File > Options > Mail > Signatures. Microsoft's own support pages still list separate routes for each, and picking the wrong one is why so many people can't find the setting at all.

Which Outlook version you're in changes every menu path

Microsoft maintains at least five versions of Outlook, and three of them store signatures in different places. That's a support burden, but it also means the first question is never "where is the button"—it's "which app am I holding." You can tell from the ribbon shape and the title bar. If the ribbon is wide with a "Help" tab and a top-left File menu, you're in classic Outlook for Windows (version 2016 through Microsoft 365 Apps, still the default in many organizations as of late 2026). If it looks like the web app and shows a "Settings" gear at the top right, you're in the new Outlook for Windows or Outlook on the web.

The version split matters because signatures don't sync automatically in every direction. Classic Outlook stores signatures as .htm files in the user profile (typically inside %APPDATA%\Microsoft\Signatures), and they don't appear in Outlook on the web unless you recreate them. The new Outlook for Windows and the web version store signatures in the mailbox itself, so they roam across devices. Microsoft's support documentation confirms signatures sync between Outlook on the web and the new Outlook, but not into classic Outlook. That one fact explains most "my signature disappeared" complaints.

On Mac, Outlook for Mac (the version that ships with Microsoft 365) lives in the Preferences > Signatures panel. It writes files to a hidden folder inside the user's Library and does not share them with Windows Outlook. Outlook on iOS and Android has no editable signature beyond a short auto-inserted line; if you need formatted text, logos, or hyperlinks, you're editing in a desktop or web client and accepting the mobile limitation.

App Menu path Syncs to web? Format support
Classic Outlook for Windows File > Options > Mail > Signatures No Rich text and HTML
New Outlook for Windows Settings > Accounts > Signatures Yes Rich text
Outlook on the web Settings > Mail > Compose and reply > Signatures Yes Rich text
Outlook for Mac Outlook menu > Preferences > Signatures No Rich text
Outlook mobile (iOS/Android) Settings > Account > Signature Mailbox-based Plain text only

Editing a signature in classic Outlook for Windows

Classic Outlook is the version where most people get stuck, because the entry point sits three layers deep in the File menu and the dialog box looks like a settings page from a different decade. Open Outlook, click File in the top-left corner, click Options at the bottom of the left column, then click Mail in the Options window and press the Signatures button near the top. The full path reads File > Options > Mail > Signatures, and it works identically in Outlook 2016, Outlook 2019, and Outlook for Microsoft 365.

1: Open Outlook and click File > Options. 2: Select Mail in the left column. 3: Press the Signatures button in the Compose messages section. 4: Pick the signature you want to change in the "Select signature to edit" list, or press New to create one. 5: Edit the text in the bottom pane, and use the formatting toolbar to change font, size, color, and alignment. 6: Assign the signature to New messages and Replies/forwards using the two drop-downs. 7: Click OK twice to close both dialogs; signatures save the moment you click OK, with no separate Save button.

If the Signatures button is greyed out, you're probably in a mail item rather than the main Outlook window—close the message and repeat the path. If you can't see the two assignment drop-downs, widen the dialog by dragging its edge; they squeeze to near-invisible widths on some laptop screens. A missing signature in a new message usually traces back to a wrong default assignment rather than a missing file, so check the drop-downs before recreating anything.

The new Outlook for Windows and Outlook on the web share one editor

The new Outlook for Windows and the browser version are built on the same engine, so the path is identical: click the Settings gear in the top-right, expand Accounts in the left pane, click Signatures, then choose the signature you want to modify. The editor supports bold, italic, underline, font size, color, links, and images. Changing the default for new messages or replies takes one click on the drop-downs above the editor.

There's a catch worth knowing before you write instructions to your team. Microsoft has documented an active complaint that signatures created in the new Outlook can appear in classic Outlook as plain text with formatting stripped, and vice versa. The two clients read the same mailbox but process HTML differently. If you share a signature across both apps, test it by sending yourself a message from each and comparing the render. Assume a logo or table will break somewhere.

The web version also lets you create multiple signatures and select one per message from the compose window's signature menu. That's useful for people who send from a shared mailbox and their own address. Assigning a signature to a shared mailbox requires going into that mailbox's own settings from a session where it's opened as a full mailbox, not as a delegated folder; signatures set for delegated mailboxes default to the primary mailbox's choices.

Editing signature content in Mac, mobile, and shared mailboxes

Outlook for Mac puts signatures in Outlook > Preferences > Signatures, where you can add, delete, and edit entries, then set defaults for new and replied messages. The panel is friendlier than Windows but still doesn't sync with the web client's signatures. If your Mac signature looks fine locally and absent in a browser session, that's the split storage talking.

Mobile versions are the harshest limitation. Outlook on iOS and Android supports only a short plain-text signature, typically limited to a single line entered under Settings > Account > Signature. There's no logo, no link formatting, and no sync of rich text back to desktop. Any signature with a job title, phone number, and confidentiality notice will look cramped on mobile, so consider keeping the mobile one deliberately short and letting the desktop signature carry the branding.

For shared or delegated mailboxes, the signature you set while piggybacking on another person's mailbox belongs to your own account, not theirs. To change the shared mailbox's signature, open that mailbox as a full account (via a separate Outlook profile on desktop or by adding the mailbox to your account in the web client), then edit its signatures from inside that session. Admin-level signature management in Microsoft 365 generally requires a third-party tool or transport-rule-based disclaimers; there's no native central signature editor in the admin center as of late 2026.

Common editing mistakes that break the layout

The most common failure is accidental inheritance. If you select text, delete it, and paste unformatted text, Outlook can carry the pasted paragraph's font into the rest of the signature. The result is a blocky, mismatched look that survives every "fix" until you clear formatting. Press Ctrl+A inside the signature pane and use the clear-formatting button, then reapply styling from scratch.

Two-sided formatting is a second trap. Mixed fonts and sizes render fine in Outlook desktop but collapse to inconsistent sizes in Gmail, Apple Mail, and the mobile clients. Outlook's signature editor uses HTML under the hood; if you paste from Word, you bring Word's CSS with you, and other clients have no idea what to do with it. Type or paste as plain text first.

Attachment bloat is the third. Signatures with large images can push a short email past an exchange server's message-size limit, causing a bounce with a vague error. A 2 MB signature added to a 24 MB attachment hits a 25 MB limit in many Microsoft 365 tenants. Keep signature images under about 50 KB by resizing before insertion rather than dropping in a full-resolution photo.

The last mistake is version drift. Someone edits their signature in the web client, a teammate edits theirs in classic Outlook, and now the same team sends visibly different signatures. The fix is procedural: pick one client as the source of truth, apply it consistently, and check staff who travel between machines.

A 10-minute audit for signature consistency across a team

Start by checking which client each person actually uses. Most organizations have a mix: desktop Outlook for assistants, the web client for contractors, mobile for executives. If signatures live in more than one app, the consistency work is bigger than the edit itself.

1: Ask each team member which client they use for routine sending, not which is installed. 2: Choose one client as the master source, usually the new Outlook or web version because signatures roam. 3: Capture each signature as plain text with formatting notes rather than as screenshots. 4: Rebuild each signature in the master client, then send a test to a personal address and open it on both a phone and a browser. 5: Check line length: signatures over roughly 60 characters per line wrap awkwardly on mobile. 6: Verify every hyperlink actually resolves before shipping the signature to the team. 7: Save the plain-text version and an HTML copy in a shared folder for quick rebuilds after a migration.

The reason to do this at all is that formatting breaks quietly. A single broken image in a signature is a professional embarrassment repeated on every message a person sends, and the deliverability impact is real—mail filters score messages partly on image-to-text ratio, and a signature that's mostly image can look like bulk mail. A signature with a modest logo and clean text clears the filter without argument.

Font inheritance and plain-text traps inside the editor

Outlook's signature editor inherits font settings from the message window's default compose font, which itself inherits from Word if Word is installed and set as the email editor. That chain explains a bizarre symptom: your signature looks correct in the preview but wrong when inserted into a new message. The preview uses the editor's own styling; the message window uses the compose font. Fixing it means changing the compose font, not the signature.

Plain-text signatures are a separate art. If a recipient's client can't render HTML (common in mailing lists and some security-conscious companies), your signature shows as raw characters with no line breaks except hard returns. Design plain-text signatures with exactly that assumption: no images, no tabs, no fancy alignment. Use short lines and put the URL on its own line rather than relying on hyperlink text.

If you use business cards or vCards, test the recipient experience rather than trusting the desktop preview. The vCard appears as an attachment on some clients and as inline contact data on others, and mobile Outlook often hides attachments behind a chevron that people never tap. Plain text usually wins on reliability for the recipient.

Here's the rule that handles the whole family of design problems: build for the least capable client your recipients use, then let the rich clients upgrade the result automatically. A well-built simple signature looks polished everywhere. A clever one looks polished in your preview and broken in the recipient's inbox.

What changes when signatures are stored in the mailbox

Classic Outlook's file-based signatures live on your machine. The new Outlook and web client store them in the mailbox, backed by Exchange Online or another mail server. That storage model change is why "roaming" is now possible and why migration from classic to new Outlook prompts a signature recreation; it's copying files into mailbox data.

A mailbox-stored signature also inherits mailbox-level policies. If an organization blocks images from load in incoming mail, your own signature doesn't render when you preview it in the web client, and the same block may stop the image from loading for recipients unless they choose to load it. That's a client setting, not a signature bug. Use compressed images and, ideally, text-based alternatives for critical contact info.

The roaming model also means deleting a signature in one place removes it from every connected client. That's an improvement over the classic behavior of leaving orphaned .htm files behind, but it's also a hazard if you delete the wrong one. Mailbox-deleted signatures don't go into a recycle bin, so keep a plain-text copy elsewhere.

Third-party marketing signature tools often plug into the mailbox-stored model, which is also why transparent ad tracking in signatures is common in corporate mail. If a signature contains a tracked image or a redirecting link, that fact travels with every message. Builders should know which of their signature links resolve where.

FAQ

Why is my Outlook signature greyed out in Settings?

If Settings > Accounts > Signatures shows the editor but every control is inert, you're likely editing a message in a protected or read-only mail view, or the account is being migrated to a new mailbox. Close all extra Outlook windows and reopen; in most cases the editor becomes active once the mailbox finishes syncing. If it persists on a Microsoft 365 account, have an admin confirm the mailbox isn't in an Office 365 migration hold.

Can two Outlook signatures with the same name exist in one mailbox?

Yes, and the duplicate silently creates ambiguity: the compose menu shows both, and recipients get whichever one Outlook assigns by default. The editor allows duplicate display names, so the practical fix is unique names like "Sales – Base" and "Sales – Trade Show." Check the default assignment drop-downs after creating duplicates, because you may have changed the wrong entry.

What happens to my signature if I switch from classic Outlook to the new Outlook for Windows?

You get prompted to re-enter or copy signatures in the new client on first launch, and the classic files won't appear automatically. Copy the signature content into a text file before switching, then paste it into the new editor. Expect formatting to need a small pass, because classic and new Outlook handle HTML differently, particularly for logo alignment and table-based layouts.

Does editing a signature in Outlook on the web update my iPhone?

Not the full signature. The mobile apps use a short, plain-text signature stored at the app level, separate from the rich signature in the web or desktop client. Changing the rich signature doesn't alter the mobile line. Set a deliberately short mobile signature so both stay consistent enough not to confuse clients.

Why does my HTML signature lose formatting when I paste it?

The receiving editor applies its own stylesheet and can strip tags it doesn't recognize. Paste as plain text, then apply formatting with Outlook's own tools rather than pasting from a web page or Word. Testing on a second device catches the mismatch before it reaches your recipients.

Is there a size limit on signature images?

Microsoft 365 tenants typically cap message size at 25 MB by default, and attachments plus signature count against that limit. Keep signature images small—under 50 KB is a safe target—and avoid embedding multiple images. If recipients report missing images, the issue is usually the total message size rather than the file format.

Can an admin change signatures for everyone in Microsoft 365?

There's no native admin signature editor in the Microsoft 365 admin center as of late 2026. Organizations usually apply server-side disclaimers through transport rules, or use third-party signature tools that install as Office add-ins. Those tools are the reliable way to enforce formatting across all users; one-off manual edits rely on people remembering to apply them.

Do signatures sync between Outlook on the web and classic Outlook?

No. Outlook on the web and the new Outlook sync signatures through the mailbox, but classic Outlook keeps its own file-based copies and doesn't participate in that sync. That's why a signature created in classic appears missing on the web and vice versa. The workaround is to recreate the signature in both locations or move entirely to the new Outlook or web client.