Why Is My Outlook Signature Not Showing Images? (Fix Guide)

You set up a sharp Outlook signature with your photo or logo — and recipients see a broken image icon, a red X, or an empty box. This is the single most common Outlook signature problem, and it's almost always one of six causes. Work through them in order; most people are fixed by step two.

The 30-second diagnosis

Images in email signatures are not embedded in the message the way you might expect. Outlook references them by URL. If that URL points to a file on your computer (C:\Users\you\logo.png), or to a location that requires a login, nobody else's email client can load it. That's the cause roughly 80% of the time: the image isn't reachable from the public internet.

The symptom tells you a lot before you change anything:

• Red X / broken-image icon — the image URL is dead, local-only, or blocked. Start with Fix 1.
• "Click here to download pictures" bar — your signature is fine; the recipient's Outlook is blocking downloads. See Fix 3.
• Empty white box where the image should be — usually a sizing problem (Fix 4) or a format Outlook can't render.
• Works for you, broken for everyone else — your machine is loading a cached or local copy. See Fix 6.

Fix 1: Host every image at a public HTTPS URL

This is the fix that matters. Every image in your signature — photo, logo, banner, social icons — must live at a web address that anyone can open without logging in, served over HTTPS (not HTTP).

• Easiest: build your signature in Sigline's free generator and upload images there — it hosts them and wires the URLs into the signature automatically.
• DIY: upload to your company website, or a Google Drive file shared as "Anyone with the link." (Right-click the file → Share → change to "Anyone with the link" → copy the link.)
• Test it: paste the image URL into a private/incognito browser window. If it loads without a login screen, recipients can see it.

After moving the images, re-create the signature from scratch using the new URLs — editing the old signature often leaves stale local references behind.

Fix 2: Paste the rendered signature, not the HTML

A classic mistake: copying the HTML source code of a signature and pasting it into Outlook's editor. Outlook then treats your <img> tags as literal text or mangles the paths. The correct move is to copy the visually rendered signature — what it looks like in the generator's preview — and paste that into the signature editor. Outlook preserves the layout, links, and image references.

Fix 3: Check Outlook's automatic picture downloads

Sometimes the problem is on the viewing side, not your signature at all. Outlook blocks automatic image downloads by default as an anti-tracking measure, showing a "Click here to download pictures" bar instead. Recipients who never click it will never see your images.

1. In Outlook, go to File → Options → Trust Center → Trust Center Settings.
2. Open Automatic Download.
3. Uncheck "Don't download pictures automatically in HTML email messages" — or add the sender to Safe Senders so their images always load.

You can't change this setting for your recipients, which is why Fix 1 matters so much: properly hosted images at least give them the option to load with one click.

Fix 4: Shrink and reformat oversized images

Outlook's rendering engine (yes, it's still Microsoft Word under the hood in classic Outlook) is picky:

• Keep each image under ~200KB — ideally under 100KB. Huge images get blocked or time out.
• Use PNG or JPG only. Outlook does not reliably render SVG or WebP images. If your logo is a WebP, convert it.
• Set explicit dimensions. A 2000px-wide logo with no width attribute can blow up the layout or fail to render. Resize to the display size (see our signature size guide).

Fix 5: Check your company's mail policies

On Microsoft 365 / Exchange work accounts, administrators can set mail flow (transport) rules that strip external images, rewrite URLs, or convert messages to plain text. If your personal Outlook shows images fine but your work account doesn't, this is likely it. Ask IT whether image blocking or link rewriting (like Safe Links) is enforced — there's no user-side fix for an admin policy.

Fix 6: Test like a recipient, not like yourself

Here's the trap: you will often see images that nobody else can see, because your own machine has them cached or can reach your local paths. Always verify with a real test:

1. Send an email to a personal address (Gmail, iCloud — not your work account).
2. Open it on your phone, on cellular data (not office Wi-Fi).
3. If the images load there, they load for everyone.

A special case: the Outlook mobile app

If images work on desktop but your phone shows a text-only signature, that's not a bug — the Outlook mobile app doesn't support HTML signatures with images at all. Mobile signatures are plain text, configured separately in the app's settings. There's no setting that enables images there; it's a hard product limitation. The workaround: set up your full signature on desktop and use Outlook on the web in your phone's browser when the designed signature matters.

Prevention checklist

• All images hosted at public HTTPS URLs — verified in an incognito window
• Each image under 200KB, PNG or JPG format
• Signature built by pasting the rendered design, not HTML code
• Test email opened on a second device, off your network
• Dimensions set explicitly (no giant source files)

Follow this once and the problem stays fixed — signatures don't degrade on their own; they break when an image host moves a file or a login requirement gets added.