Outlook Email Signature: Fixing the Broken-Image Problem

Posted October 5th, 2026 under Branding

Two professionals exchanging a business card, standing in for the contact details that belong in an email signature

Open a message from your own business in classic Outlook and look at the logo in your signature. There’s a real chance it has turned into a small gray box with a red x through it. In May 2026, Microsoft confirmed a bug that broke exactly this: signature and newsletter images failing across several Outlook build channels, replaced with “The linked image cannot be displayed. The file may have been moved, renamed, or deleted.” The fix shipped weeks later, but it exposed something most small businesses never think about — an Outlook email signature is one of the most fragile pieces of branding a company sends out, and it quietly breaks in ways nobody notices until a client mentions it.

Why do Outlook email signature images keep breaking?

The May 2026 bug hit images referenced with Content-ID (cid:) links — the standard way Outlook embeds a signature logo — after the May 12 security updates landed. Microsoft’s support page confirms the fix: corrected builds shipped for Version 2604 (Build 19929.20202), Version 2605 (Build 20026.20140) and Version 2606 (Build 20120.15000), plus the perpetual Word-based versions 2016 through 2024. An older build meant showing every recipient a broken logo without knowing it.

Microsoft logged a second, separate bug the same month: images placed with “Wrap Text with Top and Bottom” formatting lost their reference entirely, leaving a red-x placeholder or blank space. The lesson isn’t which bug mattered — it’s that classic Outlook’s rendering engine is Microsoft Word doing the drawing, not a browser, and it breaks images in ways no other mail client does. Keeping Outlook itself updated is part of keeping a signature intact.

Why do images sometimes send as an attachment instead of a picture?

A second complaint shows up just as often: the logo arrives as a file attached to the email rather than displayed inline. A few things usually cause it, mostly on the sender’s side:

  • The message is sent as Plain Text. Images can’t be embedded in plain text at all — Outlook has to be set to compose in HTML for an inline image to work.
  • The image was dragged in from File Explorer instead of inserted with Insert → Picture — drag-and-drop is the method most likely to land as an attachment.
  • The image isn’t set to 96 DPI. Outlook’s renderer treats higher-DPI images as attachments more often than standard files at their true pixel size.

None of this is visible to whoever built the signature. It shows up only on the recipient’s screen, which is why testing a signature by emailing yourself in the same client proves almost nothing.

Hands typing on a laptop keyboard while building an Outlook email signature

What actually survives Outlook’s renderer?

Outlook desktop doesn’t render HTML the way a browser does — it hands the message to Microsoft Word’s layout engine, which ignores most of what modern CSS can do. A signature built the way a web page is built will not survive the trip:

  • Table-based layout, not flexbox or grid. Word’s renderer has supported HTML tables since Outlook 2007 and nothing has changed since.
  • Every style written inline. Style blocks and CSS classes get stripped on the way in; a style=”…” attribute on each element is what Outlook actually keeps.
  • Fixed pixel widths, not percentages, and both the CSS and HTML width/height set on every image — some Outlook builds honor only the HTML attribute.

A properly built Outlook email signature checks against this list line by line, because most signature generators and design-software exports quietly ignore every one of them — they’re built for the browser, not for Word.

How small should the logo in an Outlook email signature actually be?

Image size runs in the opposite direction of instinct — a sharp-looking signature on a modern monitor needs a smaller file than most people expect. The working range is 100×100 to 200×200 pixels for a logo mark, with the larger size for a signature meant to look crisp on a retina display. A 2,000-pixel-wide logo exported straight from a design file doesn’t look more professional; it’s more likely to get resized unpredictably or blocked outright by a recipient’s mail server. Fonts carry the same caveat: Word’s renderer falls back to whatever is installed locally the moment a web font isn’t available, so a signature should use a safe stack — Helvetica Neue, Helvetica, Arial, sans-serif — rather than the display font used on the website. Font choice matters a great deal on a website; a signature is one of the few places it pays to play it safe instead.

Business owner writing a signature checklist by hand beside a closed laptop

What changes for a multilingual Aruba business?

A signature for a business serving clients in English, Spanish, Dutch and Papiamento carries more information than most — and more information is exactly what breaks first in Outlook. Keep it minimal. List the phone number once, in international format (+297 followed by the local number), since a recipient outside Aruba can’t dial a local-format number directly, and keep an address to one line if included at all — a multi-line address is a common place a signature table collapses unpredictably in older builds. A WhatsApp click-to-chat link is worth adding alongside email and phone for an island business — it’s the channel most local clients actually reach for, and a plain text link survives every mail client with no image needed. Keep the logo to the version from a real logo file set, not a resave from a social profile picture, which is already compressed and will look worse at signature size. Knowing which logo file does what solves this before it becomes a signature problem.

A five-minute signature check you can run this week

Testing a signature properly takes about five minutes and catches nearly everything above:

  • Send a test to yourself from classic Outlook, not just Outlook on the web or a phone — the desktop, Word-based renderer is where most of these problems live.
  • Check the logo’s real pixel dimensions — anywhere near 1,000 pixels wide means it’s being resized down by the client, not by design.
  • Confirm compose format is set to HTML, not Plain Text, under File → Options → Mail.
  • Open the message source and search for cid: if the image reference in the Outlook email signature looks broken or points to a file name instead of a hosted URL, that’s the point of failure.

Talk to 139 Design Studio about getting your email signature built the way Outlook actually renders it — alongside the website, hosting and day-to-day maintenance support we handle for clients across Aruba.

Sources: Microsoft Support — Images are not displayed in classic Outlook, 2026 · Litmus — Email client market share, July 2026 · MiN8T — Outlook-safe HTML email signature guide · MySignature — Why images are added as attachments in Outlook