If you’ve moved from Classic Outlook to New Outlook for Windows and your recipients keep telling you that screenshots and logos are arriving as attachments instead of appearing in the body of your emails, the problem isn’t on their end. It isn’t on your end either, in the sense that you haven’t done anything wrong. The problem is that New Outlook handles inline images differently from Classic Outlook, and Microsoft has been remarkably quiet about a behaviour change that breaks a workflow professionals have relied on for two decades.

This is not a configuration mistake you can simply fix and forget. It’s a regression baked into how the new client is built — and until Microsoft addresses it more honestly, you need to know which insertion methods reliably embed images and which silently convert them to attachments mid-flight.

What’s actually happening

In Classic Outlook, you could paste a screenshot from the Snipping Tool into a message body, drag an image out of File Explorer, or copy something from a browser, and the result was consistent: an image rendered inline, with the underlying MIME structure including the image as a cid: referenced inline part. Recipients on virtually any client — Classic Outlook, Gmail, Apple Mail, mobile — saw the image where you put it.

In New Outlook, the same actions produce inconsistent results. The image often appears inline on your screen while you compose, but the message that actually leaves your outbox includes the image as a separate attachment. Sometimes both: inline and attached, which is its own special annoyance because recipients see the image twice.

Microsoft’s own product team has confirmed this on its support forums. Pasting an image into the body of an email in New Outlook is described as a default behaviour issue that the product development team is “aware of” and “working on”. The phrasing matters: this isn’t a one-off bug report, it’s an acknowledged design problem that has persisted through general availability and into 2026.

Why New Outlook does this

The short version: New Outlook isn’t really a desktop application in the way Classic Outlook is. It’s built on Microsoft Edge WebView2, which means it runs essentially the same code as Outlook on the web wrapped in a desktop shell. The plumbing that handles message composition, image embedding, and MIME structure is web-tier code, and web-tier code historically struggles with the same problems that have always made inline images inconsistent in browser-based email clients.

Microsoft has been making real changes here, but they’ve been changes for developers, not changes that fix the user-facing problem. Starting November 15, 2025, Outlook on the web and New Outlook for Windows began rolling out an update transitioning how inline images are represented in HTML — moving from tokenised image URLs to a more secure method using content IDs and request headers. The full production rollout begins March 30, 2026.

That change brings New Outlook’s HTML representation closer to what Classic Outlook has always done with cid: references. In theory, it should help. In practice, the change addresses how add-ins correlate inline images with attachments — not whether your pasted screenshot arrives inline at the other end.

The insertion method actually matters

Here’s the practical part. Despite what the marketing implies, not all ways of getting an image into a New Outlook message are equivalent. Some routes reliably embed, some routes reliably attach, and some routes are inconsistent.

The route that works reliably: Insert ribbon → Pictures → This Device. Browse to your image file, select it, and it embeds inline. This path uses New Outlook’s actual image-insertion logic rather than relying on clipboard or drag handling. If you only remember one thing from this article, remember this.

The route that frequently fails: Pasting (Ctrl+V or right-click → Paste) a screenshot or image from the clipboard. This is where the inline-as-attachment behaviour shows up most often. The image displays in your composition window inline, which is misleading, but the message that leaves often has the image as a separate attachment.

The route that’s inconsistent: Dragging an image from File Explorer into the message body. Sometimes it embeds, sometimes it attaches, sometimes it does both. The result varies based on which area of the composition window you drop onto.

The route that always attaches: Dragging an image into the attachments area, or using Insert → Attach File. This is the documented attachment path and behaves exactly as expected.

Most people don’t realise these aren’t equivalent because in Classic Outlook they more or less were. If you’ve trained yourself over fifteen years to paste screenshots into emails because it was faster than navigating a file picker, you’re now in the worst position: the muscle memory works against you.

Account type matters more than you’d think

The other variable in this is what kind of mailbox you’re sending from. Microsoft has been explicit that the behaviour can vary based on tenant configuration, and this isn’t documented well anywhere.

If you’re on an Exchange Online mailbox with default tenant settings, you have the best chance of consistent inline behaviour, particularly with the post-November 2025 changes. If your administrator has applied transport rules that modify message content — particularly anything touching HTML body rewrites or attachment scanning — those rules interact with the cid-referenced inline images in ways that can convert them to attachments at the server.

If you’re using IMAP or POP — which New Outlook nominally supports but has historically struggled with — image handling is more fragile still. In theory, the feature enabling users to add IMAP and POP accounts was reintroduced in May 2024 and is still referenced in the account setup wizard, but users have reported various issues when configuring such accounts in the new Outlook for Windows. Image handling is one of the rougher edges on those accounts.

Worth checking with your IT team: ask whether any data loss prevention or attachment scanning rules are applied to outbound mail. These tools sometimes strip images out of HTML body content and re-attach them, which is a perfectly reasonable security operation that looks identical to the New Outlook bug from a user’s perspective.

Verify before you blame New Outlook

One of the more frustrating discoveries when troubleshooting this is that the inline-vs-attachment status as it appears in your Sent Items folder isn’t always what the recipient sees. Different mail clients render HTML email differently. A recipient using a strict text-only client, an aggressive corporate spam filter, or certain mobile clients may see an attachment where the underlying message had a proper inline reference.

Before deciding this is definitely New Outlook’s fault, do a controlled test:

  1. Send a test email containing an inline image to a personal address you control on a known good client — Gmail web or Outlook.com web are both reasonable choices because they render HTML email faithfully.
  2. Check how the message arrives in that target. If the image is inline there but your work recipient sees it as an attachment, the issue is downstream of you.
  3. If it arrives as an attachment in the test address too, then yes, your New Outlook composition is the problem.

This sounds obvious but a surprising number of people are troubleshooting a recipient-side or transport-side issue and convinced it’s a client-side one.

Make sure you’re sending HTML, not Plain Text

This is the configuration check that fixes a meaningful percentage of “images attaching” reports — and it’s easy to miss because New Outlook hides format selection more deeply than Classic Outlook did.

In Classic Outlook, you could see and switch the message format on the Format Text ribbon of any new message. In New Outlook, the format defaults to HTML and is mostly invisible unless something has changed it. If a recipient has previously sent you a plain-text message and you’re replying in the same conversation, New Outlook can inherit plain text format, which forces any image to be sent as an attachment because plain text can’t render inline images by definition.

If you’re seeing systematic image-attachment behaviour in replies to certain people but not in new messages, format inheritance is the likely cause. Compose a fresh new message rather than replying, and check whether the image embeds correctly. If it does, you’ve found your culprit.

What Microsoft hasn’t told you

The honest summary of where this stands in mid-2026: Microsoft has acknowledged that paste-to-inline behaviour in New Outlook is a problem they’re working on, but they haven’t published a timeline for a fix that actually addresses the user-facing experience. The November 2025 and March 2026 changes are infrastructure improvements that benefit add-in developers and improve security, not user-facing fixes for the paste-an-image-and-it-attaches behaviour.

Until that changes, treat New Outlook image insertion as a workflow that needs a small habit change. Use Insert → Pictures → This Device when you care about inline behaviour. Verify with test sends to a known good external address when you’re sending anything important — a corporate logo, a contract proof, a screenshot of an error you need someone to debug. Don’t rely on the visual appearance of your composition window because what you see there isn’t always what leaves.

And if your work genuinely depends on rich email composition with inline images — sales outreach, marketing communications, anything where the email is itself the deliverable — this is one of the legitimate reasons to stay on Classic Outlook for now. Microsoft has stated that Classic Outlook will be supported until at least 2029, and the forced transition to New Outlook has been pushed back: the opt-out phase for Enterprise environments will now begin in March 2027 (previously April 2026), providing organizations with 12 months of lead time to prepare.

You have time. Use it to either wait for Microsoft to fix this properly or to adjust your workflow around it. Just don’t pretend the problem doesn’t exist — your recipients have already noticed.

If this article matches your symptoms but the fixes haven’t resolved your specific case, two adjacent issues might be at play:

  • Signature images attaching as separate files — this is a slightly different problem with different fixes. See our piece on signature images showing as attachments.
  • Setting up a working signature in New Outlook — if your inline-image troubles are specifically signature-related, the January 2026 signature feature changes affect what works and what doesn’t.

The broader differences between New Outlook and Classic Outlook image handling are covered in our New Outlook vs Classic Outlook comparison, which is the place to start if you’re encountering more than one image-related quirk and want to understand whether they share a common root cause.