Outlook Mobile Signature: How to Set Up & Sync on iOS and Android

Here's the problem with Outlook Mobile signatures: they work almost nothing like your desktop Outlook signature. There's no sync, no HTML support, no way to include your logo, and your signature gets wiped every time the app updates or you reinstall it. If you've set up a great signature on Outlook for Windows or Mac, none of that carries over to your phone.

This catches a lot of people off guard. You spend time creating a professional signature in Outlook on your desktop — with your company logo, job title, LinkedIn icon, and office number — then you send an email from your phone and it goes out with plain text (or worse, the default “Sent from Outlook” line that makes it obvious you forgot to set anything up).

The reason Outlook Mobile works this way is architectural. Outlook Mobile stores signatures locally on the device, in a completely separate data store from your Exchange or Microsoft 365 account. Microsoft hasn't built any cloud sync for mobile signatures into the product. Each device is its own island.

This guide covers how to set up an Outlook Mobile signature on both iPhone and Android, the HTML workaround that gets you a proper rich signature on your phone, how to make your existing desktop signature display correctly in mobile email clients, and the common things that go wrong (and how to fix them).

If you want a signature that looks professional across every device and client without fighting with settings on each one, the NeatStamp editor generates mobile-safe HTML that works in Outlook on the Web, Apple Mail, and any email client that supports HTML signatures. More on that below.

Why Outlook Mobile signatures are completely different from desktop

On Windows, your Outlook desktop signature is stored as an .htm file in your local AppData folder (%AppData%\Microsoft\Signatures\). When you create or edit a signature in Outlook's settings, it writes those files. When you compose an email, Outlook reads them and injects the HTML into the message. That whole system is local to your Windows machine.

Outlook Mobile doesn't read from that folder. It can't — it's a mobile app running on a completely different operating system. Instead, it has its own internal settings storage on the device. When you sign into your Microsoft 365 account in Outlook Mobile, it connects to your mailbox for emails, calendar, and contacts, but it does not pull your signature configuration from anywhere. You start fresh.

No HTML support in Outlook Mobile

The Outlook Mobile signature editor is plain text only. You can type your name, title, phone number, and website. You can't bold anything, change the font size, add a logo, insert social icons, or include any HTML markup. What you type is what gets appended to your emails, formatted as unstyled plain text.

This is a significant limitation compared to what you get on Outlook for Microsoft 365 on desktop, or on Outlook on the Web (OWA), both of which support full HTML signatures. Microsoft hasn't explained why they haven't added HTML support to the mobile app, but it's been a known limitation since the app launched and remains the case in 2026.

No sync between devices

If you have two phones, or a phone and a tablet, both running Outlook — you need to set the signature on each device separately. There is no Microsoft 365 setting to push a mobile signature. There is no import/export. The only way to get the same text on multiple devices is to type it on each one.

This also means when you upgrade your phone and sign in to Outlook Mobile on the new device, your signature is gone. Signing into your Microsoft 365 account restores your emails, calendar, and contacts from the cloud — but not your mobile signature setting, because it was only ever stored locally on the old phone.

No sync with Outlook on the Web

Outlook on the Web (OWA, at outlook.office.com) does store its signature in the cloud. When you set up a signature in OWA, it's available on any device you use to access OWA via browser. But OWA signatures also don't sync to Outlook Mobile. They are three separate systems: Outlook Desktop, Outlook on the Web, and Outlook Mobile. Each manages signatures independently.

The practical implication: if you want the same signature everywhere, you have to configure it in three places. Most people just accept the limitation and configure the desktop version properly, set a minimal plain text version in Outlook Mobile, and move on.

Step-by-step: Set up your signature in Outlook Mobile on iPhone (iOS)

Setting up a basic plain text signature in Outlook Mobile on iPhone takes under two minutes. Here's exactly where to find the setting:

1. 1

   Open the Outlook app and tap your profile picture

   Your profile picture (or initials if you haven't set a photo) is in the top-left corner of the main screen. Tap it to open the left sidebar.

2. 2

   Tap the Settings gear icon

   The gear icon is at the bottom of the sidebar. Tap it to go into the Outlook Settings screen.

3. 3

   Scroll down to find “Signature”

   In the Settings screen, scroll down until you see “Signature” under the Mail section. Tap it.

4. 4

   Toggle the signature on and type your text

   You'll see a toggle (on/off) and a plain text field. Turn the toggle on if it's off. Clear the default text (“Get Outlook for iOS”) and type your signature. Use line breaks to separate your name, title, phone, and website.

5. 5

   Select which accounts use this signature

   If you have multiple email accounts in Outlook Mobile (e.g., your work Microsoft 365 account and a personal Gmail), you can choose “All Accounts” or “Per Account” to set different signatures for different accounts. Per Account is useful if you want different plain text for your work account vs. personal.

6. 6

   Back out — it saves automatically

   There's no Save button. Tapping the back arrow saves the setting. Send yourself a test email to confirm the signature appears correctly.

Step-by-step: Set up your signature in Outlook Mobile on Android

The Android process is virtually identical to iOS. The navigation is the same:

1. 1

   Tap your profile picture in the top-left

   Opens the navigation drawer on the left side of the screen.

2. 2

   Tap the gear icon at the bottom

   Takes you to the Settings screen.

3. 3

   Tap your account name, then tap “Signature”

   On Android, signature settings are sometimes nested under the specific account rather than a top-level setting. If you don't see “Signature” at the top level, tap your email account name first.

4. 4

   Enable the signature and type your content

   Same as iOS — toggle on, clear the default promotional text, type your name, title, phone, and website on separate lines.

5. 5

   Tap the checkmark or back arrow to save

   On some Android versions there's a checkmark to confirm; on others the back gesture saves. Send a test email to verify.

One thing to watch on Android specifically: if you have Outlook connected to both a Microsoft 365 account and a Gmail account, the signature settings may behave slightly differently per account. The Microsoft 365 account will use Outlook's own signature. The Gmail account in Outlook Mobile may use Gmail's own signature setting, which you configure separately in the Gmail app or at mail.google.com. Check both.

The HTML workaround: using native mail apps for a rich signature

If you need a proper HTML signature on your phone — with your logo, formatted contact details, and social icons — Outlook Mobile can't do it. But your phone's native mail apps can. Here's how to get a rich signature on your phone using a workaround:

Option 1: Apple Mail on iPhone (the cleanest solution)

Apple Mail on iPhone supports HTML signatures. You can add your Microsoft 365 or Exchange account to Apple Mail and send emails from there when you need a professional HTML signature. The setup:

1. Go to Settings → Mail → Accounts → Add Account
2. Choose Microsoft Exchange and enter your work email and password
3. Apple Mail will connect to your Exchange or Microsoft 365 mailbox
4. Now open a desktop computer and go to outlook.office.com
5. Go to Settings → View all Outlook settings → Mail → Compose and reply
6. Set up your HTML signature there — OWA supports full HTML

The Apple Mail trick: Apple Mail on iPhone actually reads your signature from the iOS Settings app. Go to Settings → Mail → Signature. You can type rich text there, but not HTML directly. For a genuine HTML signature in Apple Mail, you need to copy your formatted signature (not the HTML code, but the rendered output) from a desktop and paste it into the Apple Mail signature field on your Mac, then it syncs to your iPhone via iCloud.

This is easier than it sounds. Build your signature in the NeatStamp editor, click “Copy Signature” on your Mac, then open Apple Mail on your Mac, go to Mail → Settings → Signatures, and paste it in. Enable iCloud sync for Mail and it appears on your iPhone within a few minutes. The full process is in the mobile-friendly signature guide.

Option 2: Use Outlook on the Web from your phone's browser

Outlook on the Web (OWA) at outlook.office.com works in mobile browsers. If you bookmark it on your home screen, it functions almost like a native app. The signature you configure in OWA is an HTML signature stored in your Microsoft 365 account — it travels with your account and appears on any device where you access OWA.

To set up your OWA signature: log in at outlook.office.com, click the settings gear (top right), click “View all Outlook settings”, go to Mail → Compose and reply, and paste your HTML signature. You can paste the rendered output (click “Copy Signature” in NeatStamp, then Ctrl+V in the OWA signature editor) and it works with full formatting preserved. This is the closest thing to a true sync between your Microsoft 365 signature and your mobile experience.

Option 3: Gmail app for Google Workspace accounts

If your organization uses Google Workspace (not Microsoft 365), you can set up an HTML signature via Gmail on desktop at mail.google.com and it will appear when you compose emails in the Gmail app on Android and iOS. Google does sync Gmail web signatures to the mobile app. The Gmail mobile app itself only has a plain text signature setting — but the HTML signature set on desktop takes priority for composed emails. For the full Gmail signature setup, check the compatibility guide for cross-client testing tips.

How to make your desktop signature mobile-safe

Even if you're sending from the desktop most of the time, your recipients are reading your emails on their phones. 61.9% of emails are opened on mobile. So your desktop signature — the one you send from Outlook on Windows — needs to render properly on a 375px iPhone screen, not just look good in your Outlook compose window.

Keep the max width at 500px

Most email signature templates default to 600px or 700px wide. That's wider than most phone screens in portrait mode. Set your outer signature table to a maximum of 500px and add max-width: 100% so it shrinks on narrower screens without creating horizontal scroll. The code looks like this:

<table width="500" style="width:500px;max-width:100%;" cellpadding="0" cellspacing="0" border="0">

This single change eliminates the horizontal scroll problem that makes wide signatures look broken on phones. For mobile-friendly signatures, 500px is the widest you should go.

Use table-based layout, not CSS floats or flexbox

Outlook for Windows uses the Word rendering engine, which ignores CSS flexbox, CSS grid, and float-based layouts. Build your signature with HTML tables for layout. This is old-school web development, but it's what actually works across Outlook desktop, Outlook Mobile, Gmail, and Apple Mail simultaneously. If your signature uses flexbox and it renders fine in Gmail — it will likely break in Outlook on Windows.

Table-based layouts also tend to be more predictable on mobile, since they don't rely on CSS behavior that varies by client. A two-column table with your logo on the left and contact info on the right will render the same in most clients (though on very narrow phones, the two columns may be squeezed — single-column is safer for small screens).

Inline all CSS — no external stylesheets

Email clients strip external stylesheets and often strip <style> tags from the email head. Everything needs to be inline: style="font-size:14px;color:#374151;"on each element directly. This is verbose but it's the only approach that works reliably across all clients. NeatStamp generates inline-CSS signatures by default — this is not something you need to do manually if you use the editor.

Minimum 14px font size

Text below 13px gets auto-scaled by the Gmail Android app in ways that aren't predictable. Text below 14px is genuinely difficult to read on a 5-inch phone screen. Set your name at 16px or 18px, job title and contact details at 14px, and any disclaimer text at a minimum of 12px (acceptable for legal fine print, but that's the floor). The font size hierarchy helps create visual structure without making anything unreadable on mobile.

Host images externally, not as base64

Base64-encoded images bloat your email HTML, get converted to attachments by Outlook desktop, and don't cache on mobile devices. Host your logo and any signature images on a CDN or your own server with a public HTTPS URL. Reference them with a standard <img src="https://..."> tag. For reliable delivery and display, see the email signature images not displaying guide — it covers exactly which hosting setups work and which cause problems.

Use PNG icons for social links at 2x resolution

Phone screens are retina displays (2x or 3x pixel density). A 24px icon displayed at 24px on a 2x display gets stretched to fill 48 physical pixels — which makes it look blurry. Export your social icons as 48x48px PNG files and display them at 24px via the HTML width attribute. The display size stays 24px but the extra pixels keep it sharp on retina screens.

PNG is better than SVG for email signatures because SVG support in email clients is inconsistent. PNG renders identically across all clients and all devices.

Common Outlook Mobile signature problems

Problem: signature disappeared after the app updated

This is the most common Outlook Mobile signature complaint. App updates sometimes reset locally stored settings, and your signature is one of them. It happens with major version updates more often than minor ones, but there's no pattern you can predict. The fix is straightforward: go back to Settings → Signature and retype it.

The prevention: keep a note with your signature text saved somewhere (Notes app, a document, anywhere accessible). When the app resets it, you're copying and pasting instead of retyping from memory. 30 seconds versus 3 minutes. Some people also email themselves the text so it's in their inbox for quick reference. For other Outlook signature disappearing issues, the Outlook signature not working guide covers the desktop-specific causes as well.

Problem: signature not syncing between devices

It won't. There is no sync. This is not a misconfiguration — it's how the product works. If you have two phones, you set the signature on both phones manually. If you got a new phone and signed in to Outlook, you set the signature again. The only workaround is to accept the limitation and either keep the mobile signature very short (easy to retype) or use an alternative approach like OWA in the browser.

Problem: images in emails aren't loading on Outlook Mobile

Outlook Mobile by default may block remote images to protect privacy. When your recipients see your email in Outlook Mobile with blocked images, your logo shows as a broken image icon. They need to tap “Load images” or adjust their settings to always load images from known senders. You can't control this on their end, but you can make it less of a problem by:

• Setting descriptive alt text on all images so the signature reads sensibly even without images
• Hosting images on a reputable CDN (not a personal web server) — trusted hosts get unblocked more often
• Keeping the signature readable without images — critical info as text, not embedded in the logo

Problem: signature text is too wide on recipients' phones

If recipients are telling you your signature requires horizontal scrolling on their phone, your desktop signature HTML is too wide. Check the outer table width — if it's 600px or 700px without max-width:100%, that's the cause. Drop it to 500px and add max-width:100%. Also check for any images with explicit pixel widths larger than 500px and no max-width override.

The quickest way to diagnose this: email yourself from your desktop Outlook, then open that email on your phone. Can you read the entire signature without scrolling sideways? If not, you have a width problem. Resize the table and repeat until it fits cleanly on a 375px iPhone screen (iPhone SE width, the narrowest iPhone still in common use).

Problem: phone number not tappable in email

Plain text phone numbers in emails are sometimes auto-detected by iOS and Android and converted to tappable links automatically. But this is unreliable — some email clients do it, some don't, and the formatting can vary. The reliable fix is to explicitly wrap your phone number in a tel: link in your HTML signature:

<a href="tel:+15551234567" style="color:#2563eb;text-decoration:none;">+1 555 123 4567</a>

This works in Apple Mail, Gmail, Outlook Mobile, and every mobile email client. Recipients tap once and their phone dialer opens with your number pre-filled. It's one of the most practical improvements you can make for mobile recipients.

How NeatStamp handles mobile signatures

Every signature built in NeatStamp is mobile-safe by default. You don't have to think about any of the technical details above — the output HTML already includes them. Specifically:

• ✓375px tested: Every template is previewed and tested at 375px width (iPhone SE), the narrowest iPhone in common use. If it fits there, it fits on any phone.
• ✓Table-based layout: All signatures use HTML tables, not flexbox or CSS floats, so they render correctly in Outlook desktop and Outlook Mobile.
• ✓Inline CSS only: No external stylesheets, no style tags. Everything is inline so it survives email client preprocessing.
• ✓PNG social icons: Social icons are exported as PNG at 2x resolution, displayed at 24px — sharp on retina screens, correctly sized touch targets.
• ✓Hosted images: Logo and photo images are hosted on NeatStamp's CDN via HTTPS. No base64 encoding, no attachment issues in Outlook.
• ✓max-width:100% on all images: Every image element includes the responsive max-width declaration so images scale down on narrow screens.
• ✓14px minimum font size: No text element in any NeatStamp signature is below 14px, keeping content readable on every screen size.

The one thing NeatStamp can't do is bypass the Outlook Mobile plain-text limitation. That's a product decision by Microsoft, not something any tool can override. What NeatStamp gives you is a properly built HTML signature for your desktop clients that looks right when your recipients open your emails on their phones.

You can also use NeatStamp to generate a clean plain-text version of your signature to paste into Outlook Mobile — same information, just no formatting. Browse the signature templates to find a design that works for your role and industry.

Pro tips for Outlook Mobile signatures

Tip 1: Test on a real phone, not a simulator

Browser developer tools with mobile simulation modes give you a rough idea of how an email looks on a phone, but they don't replicate real email client rendering. Send yourself a test email and open it in Outlook Mobile, Apple Mail, and Gmail on your actual phone. What looks fine in Chrome DevTools at 375px may render completely differently in the real Outlook Mobile app on an actual iPhone. Five minutes of real device testing reveals problems that hours of simulator testing misses.

Tip 2: Use hosted images, never attachments

For the images in your desktop signature (the ones that appear in emails you send from desktop Outlook), host them at a stable HTTPS URL. Images that load from a URL display correctly in Outlook Mobile when recipients open your emails. Images embedded as base64 or attached as files may show as attachments or not load at all on mobile. Keep the images under 80KB each. Faster loading on mobile data connections, less chance of getting caught in spam filters. The images not displaying guide has the full breakdown of what causes image loading failures in Outlook Mobile.

Tip 3: Keep the Outlook Mobile signature under 5 lines

Since it's plain text, keep it short. Recipients who get your mobile emails don't need a six-line signature with every social profile listed. They need to know who you are and how to reach you. A good 4-line Outlook Mobile signature:

That's it. Name, title, phone, website. If you need to include your email address too, add it. But avoid listing every social media handle, your full office address, and a legal disclaimer in the plain text mobile signature — that's what the full HTML desktop signature is for.

Tip 4: Keep your HTML under 10KB

The HTML that makes up your desktop email signature gets included in every email you send. If the HTML is 50KB, every email you send is 50KB heavier. On mobile data connections, large emails load noticeably more slowly. Some corporate email gateways flag messages with unusually large signature HTML as potential spam. A well-written email signature HTML should be 3-8KB. If yours is larger, look for base64 images or excessive inline CSS that can be trimmed.

Tip 5: For teams, use server-side signatures as the safety net

If you manage signatures for a team and the Outlook Mobile limitation is causing problems — people sending from their phones without a proper signature — the practical solution is a server-side signature appended by Exchange transport rules. Every email that goes through Exchange (including mobile emails) gets the signature appended server-side, regardless of which client or device it was sent from. The employee doesn't need to configure anything on their phone. The signature is added automatically. See the email signature for teams guide for how this works and what tools support it. Also worth reading: how to set up email signatures on any phone.

Related guides

Frequently asked questions