Inline Images Are Still Loading in Outlook: How to Fix It


Can’t send emails in Outlook because you’re getting the “Please wait to send” warning? Fix the inline images are still loading error in outlook that’s keeping your emails stuck and preventing them from sending.


When Microsoft Outlook hits you with “Please wait to send: Inline images are still loading. You can send your message after they’ve loaded”—or its twin alert, “Please wait to send: Attachments are still loading”—it locks your email in Drafts. This bug regularly triggers across New Outlook for Windows, Outlook on the Web (OWA), and Outlook for Mac, even on plain-text replies where you never pasted a photo or attached a file.

Scope Check: This pop-up is an outgoing send-blocking bug, not an incoming display issue. Changing your Trust Center picture download settings (which fix received emails showing a red X) will not clear it.

Use the 30-second workarounds below to get an urgent email out now, then apply the permanent fix to stop the “inline images are still loading” error in Outlook from returning.


5 Ways to Force-Send a Stuck Outlook Email in Under 30 Seconds

Once Outlook stalls on the “Please wait to send” dialog, waiting passively rarely clears the upload queue. Use one of these five bypasses to push your message through immediately:

  1. Switch to Plain Text to Strip Locked Objects: Drop whatever invisible inline asset is holding the Send button hostage. In New Outlook, click Pop Out (if composing inside the Reading Pane), then select Options > Switch to plain text > OK. In Classic Outlook, select Format Text > Plain Text.
  2. Save, Close, and Reopen From Drafts: Close the compose window (or save manually), wait 10 to 15 seconds for Exchange Online sync to settle, reopen the email from Drafts, and click Send.
  3. Replace Pasted Screenshots With File Attachments or OneDrive Links: Delete pasted screenshots from the message body, save them locally as a PNG or JPG, and insert them through the Attach file (paperclip) icon. If standard attachments also hang, upload the files to OneDrive and paste a sharing link.
  4. Forward Shared Mailbox Emails From Your Personal Inbox: Drag or copy the stuck shared mailbox email into your personal inbox and forward it from there. Tradeoff: sending from your personal mailbox will not stamp the forwarded indicator onto the original thread in the shared inbox.
  5. Finish Sending in Another Outlook Client: Because Microsoft 365 syncs drafts in the cloud, open your Drafts folder in Outlook on the Web (OWA) (if blocked on desktop) or Classic Outlook (if blocked in New Outlook) and click Send.

Protect Your Draft Before Retrying: If Outlook refuses to save your draft, copy the body text into Notepad before closing the window. Always check Sent Items before clicking Send a second time—sync stalls occasionally transmit the message on the backend while leaving the “Please wait to send” pop-up on screen, causing duplicate emails.


Why Your Outlook Send Button Is Locked?

Match your exact symptom below to jump straight to the permanent fix built for your scenario.

Error triggers only in a shared mailbox (even on plain text)New Outlook Offline Mode sync conflict
Error appears with zero pasted images or attachmentsCorrupted signature HTML / VML, 1×1 tracking pixels, or buried reply-chain images
Emails with signatures get stuck in Outbox or hang repeatedlyThird-party add-in (CodeTwo, Exclaimer, OpsHub) clashing with Outlook’s inline-image loader
Draft will not save, and restarting Outlook did not clear itCorrupted Olk / Edge WebView2 cache (New Outlook) or RoamCache (Classic Outlook)
Sends cleanly in OWA, fails in New Outlook desktopBroken local Windows app build or outdated Edge WebView2 runtime
Fails in both New Outlook and OWA across multiple coworkersActive Microsoft 365 service incident or tenant-wide regression

Why Outlook Blocks Plain-Text Emails With “Inline Images Are Still Loading”

Before unlocking Send, Outlook runs a pre-send check to confirm every embedded visual asset has finished syncing to Exchange Online. Five hidden triggers trip that check even on messages that look like pure text:

  • Signature Logos and Hidden Bitmaps: Outlook treats every company logo, badge, and social icon in your email signature as an inline attachment. Centralized signature tools also convert custom brand fonts and colored banners into rendered bitmap images behind the scenes, injecting multiple hidden files into every message.
  • Copy-Pasted VML and Dead cid: Paths: Pasting a signature or table from Microsoft Word, a webpage, or an older sent email drags in hidden Vector Markup Language (VML) or broken cid:image paths. Outlook stalls indefinitely trying to verify a reference that no longer resolves.
  • Microsoft’s Updated Inline-Image Security Loader: Starting in November 2025, Microsoft overhauled how OWA and New Outlook for Windows load inline images in the HTML editor. Outlook replaced legacy URL-embedded attachment tokens with header-based fetch calls and cid: content IDs inside the src attribute. Outdated web add-ins and signature scripts still parsing the old URL structure can freeze inline-image processing.
  • Inherited Graphics Inside Reply and Forward Chains: Replying to or forwarding a long thread forces Outlook to re-validate every earlier sender’s signature logos, banners, and pasted screenshots buried further down the conversation.
  • WebView2 Local Cache Locking: New Outlook for Windows runs on Microsoft Edge WebView2 with Offline Mode turned on by default. Stale local browser storage and offline draft locks frequently block background image uploads—especially on delegated shared mailboxes.

7 Permanent Fix to Stop Outlook’s “Please Wait to Send” Loop

Work through these fixes in order, or jump straight to the fix matched to your symptom in the table above.

1. Turn Off New Outlook Offline Mode to Unblock Shared Mailboxes

Turning off Offline Mode is the most dependable fix for New Outlook users—especially when plain-text replies or shared mailbox emails freeze on send. Disabling offline access stops New Outlook from waiting on stale local sync storage and forces direct communication with Exchange Online.

  1. Open New Outlook for Windows.
  2. Click Settings (gear icon) in the top-right corner.
  3. Select General > Offline.
  4. Toggle off Enable offline email, calendar, and people.
  5. Click Save.
  6. Close Outlook, open Task Manager, select Microsoft Outlook, and click End task to terminate background WebView2 sync processes.
  7. Relaunch New Outlook and send a test email.

Why Task Manager Matters: Closing the New Outlook window with the X button often leaves its background WebView2 helper process running in memory. Ending the task in Task Manager forces the updated Offline Mode policy to initialize cleanly on relaunch.

2. Strip Broken VML Markup & Bitmap Fonts From Your Email Signature

Verify whether your email signature is causing the hang before rebuilding it: delete your signature in Outlook settings, restart Outlook (or refresh your OWA tab), and send a plain-text test email to yourself. If that email goes through, rebuild your signature cleanly:

  1. Open Settings > Account > Signatures in New Outlook or OWA (or Message > Signature > Signatures in Classic Outlook).
  2. Delete the broken signature outright instead of editing over corrupted HTML markup.
  3. Save a clean, compressed copy of your logo locally as a PNG or JPG (keep file size under 100 KB and pixel dimensions modest).
  4. Create a new signature and add the logo using Outlook’s Insert Picture icon—never paste graphics from Microsoft Word, Google Docs, or a web browser.
  5. Balance Embedded vs. Hosted Images: Externally hosted image URLs pause Outlook whenever a remote server responds slowly, while stacking multiple high-resolution embedded graphics inflates message size and stalls upload checks. Stick to one lightweight local logo whenever possible.
  6. Prevent Hidden Bitmap Conversion: Swap custom brand fonts for standard font stacks and replace solid-color background graphics with plain HTML background colors so signature tools stop generating extra hidden bitmaps.

3. Fix CodeTwo, Exclaimer & OpsHub Add-In Stalls After the cid: Update

Signature injectors and workflow plugins (CodeTwo, Exclaimer, OpsHub) run scripts inside the compose pane as you draft or click Send. Following Microsoft’s shift to cid:-based inline image representation in New Outlook and OWA, older add-in versions are prone to stalling outgoing sends or leaving emails stuck in the Outbox.

  • In New Outlook and OWA: Pause until your signature visibly finishes rendering before clicking Send. To test for a faulty plugin, open Apps > Manage apps in the left rail and temporarily disable signature or CRM add-ins. On OWA, test in an Incognito or InPrivate browser window to rule out interfering browser extensions.
  • In Classic Outlook: Press Win + R, run outlook.exe /safe, and test sending in Safe Mode (which turns off COM add-ins). If Safe Mode works, open File > Options > Add-ins > Manage COM Add-ins > Go and disable third-party plugins one at a time to isolate the culprit.
  • Move to Server-Side Signatures: If a client-side CodeTwo or Exclaimer add-in keeps stalling sends, ask your IT team to switch to server-side signature stamping, which applies brand logos in transit after Outlook releases the email.

4. Wipe New Outlook’s Olk Cache, Classic RoamCache, or Mac Sync Data

When Outlook refuses to save drafts or blocks signature-free plain text, clear your local client cache using the exact path for your version below.

Do Not Look for RoamCache in New Outlook: The RoamCache folder only exists in Classic Outlook. New Outlook for Windows stores its cache inside Windows app storage and the hidden %localappdata%\Microsoft\Olk directory.

Outlook ClientExact Cache Clearing & Reset Steps
New Outlook for WindowsMethod 1 (App Repair / Reset): Close Outlook via Task Manager. Open Windows Settings > Apps > Installed apps > Outlook (new) > three dots > Advanced options. Run Repair first; if the error continues, run Reset (cloud mail stays safe, though you must sign in again).
Method 2 (DevTools Cache Clear): Close Outlook, press Win + R, and run olk.exe --devtools. Open the Network tab, right-click the requests table, and select Clear Browser Cache. Open the Application tab, expand Local storage and Cookies, right-click entries referencing outlook.office, and click Clear.
Method 3 (Local Folder Wipe): Close Outlook, press Win + R, open %localappdata%\Microsoft\Olk, and delete its contents (or EBWebView\Default\Cache), then relaunch.
Classic Outlook for WindowsClose Outlook. Press Win + R, open %localappdata%\Microsoft\Outlook\RoamCache, and move or delete all files inside. For persistent attachment hangs, clear HubAppFileCache in the parent Outlook folder, then restart Classic Outlook.
Outlook on the Web (OWA)Test inside an Incognito or InPrivate window. If sending succeeds, clear cached files and cookies for outlook.office.com and outlook.live.com in your main browser and disable ad blockers or writing extensions that modify the compose editor.
Outlook for Mac (New)Open Tools > Accounts, select the affected account in the left pane, click the gear icon at the bottom left, and select Reset Account to rebuild local sync data from Exchange Online.
Outlook for Mac (Legacy)Ctrl + click (or right-click) the affected Exchange folder in the navigation pane, choose Properties, open the General tab, and click Empty Cache to force a fresh server sync.

5. Separate VPN Drops From a Microsoft 365 Outage (Desktop vs. OWA Test)

Outlook uploads inline graphics over HTTPS in real time while you draft. Unstable Wi-Fi, throttled VPN tunnels, or SSL-inspecting proxies can drop those uploads silently while leaving the UI stuck on “loading.”

  1. Test Off-VPN: Disconnect your VPN briefly (or switch to a mobile hotspot) and retry sending a small inline screenshot.
  2. Run the 2-Minute Desktop vs. Web Isolation Test: Send a small local screenshot to an internal coworker from New Outlook for Windows, then repeat the exact test in OWA:
    • Fails on Desktop, works in OWA: The fault sits in your local Windows app cache or Edge WebView2 runtime—focus on Fix #4 and Fix #6.
    • Fails in both Desktop and OWA across multiple coworkers: You are likely hitting an active Microsoft 365 service incident. Skip wiping local profiles and use Fix #7 or the Microsoft 365 Admin Fixes section below.

6. Patch New Outlook & Edge WebView2 to Clear Send-Queue Regressions

Running an outdated client build or browser engine keeps you exposed to send-queue bugs Microsoft has already patched:

  • New Outlook for Windows: Open Microsoft Store > Downloads (or Library) and click Get updates to pull the latest Outlook (new) build.
  • Windows & Edge WebView2: Run Windows Settings > Windows Update to keep the underlying Microsoft Edge WebView2 runtime current.
  • Classic Outlook (Windows): Select File > Office Account > Update Options > Update Now.
  • Outlook for Mac: Select Help > Check for Updates via Microsoft AutoUpdate.

7. Revert to Classic Outlook When a New Outlook Build Breaks Sending

When a broken New Outlook build reaches production, switching back to Classic Outlook remains the fastest uninterrupted workaround until Microsoft ships a fix.

  1. Toggle New Outlook to Off in the top-right corner of New Outlook for Windows (or select Help > Go to classic Outlook).
  2. Send affected replies and attachments from Classic Outlook.
  3. Log your client build via Help > Feedback before switching away.

Microsoft 365 Admin Fix: PowerShell Rollback, cid: Audits & Exchange CUs

When multiple users report “Please wait to send: Inline images are still loading” at once, handle remediation at the tenant and policy layer rather than wiping endpoints individually:

  • Roll Back Affected Users via Exchange Online PowerShell: Disable New Outlook cleanly for an impacted user or group until a broken build is patched:
    • Per-user rollback: Set-CASMailbox -Identity user@domain.com -OneWinNativeOutlookEnabled $false
    • Policy-wide rollback: Set-OwaMailboxPolicy -Identity "PolicyName" -OneWinNativeOutlookEnabled $false
  • Audit Web Add-Ins for Microsoft’s cid: HTML Update: Confirm internal and vendor Outlook web add-ins updated their HTML parsing after Microsoft’s November 2025 inline-image loader change. Add-ins must parse cid: values from the src attribute and map them via Office.context.mailbox.item.getAttachmentsAsync (contentId) rather than reading legacy URL-embedded attachment tokens.
  • Check Service Health Before Wiping Profiles: Review Microsoft 365 Admin Center > Health > Service health for active Exchange Online or New Outlook advisories.
  • Verify Hybrid / On-Premises Exchange Builds & SSL Proxies: Confirm on-premises or hybrid Exchange Server nodes run Exchange Server 2019 CU15 or later (or Exchange Server 2016 CU11 or later) to rule out legacy OWA download-domain inline-image bugs. Verify that SSL inspection proxies and secure email gateways are not stripping authorization headers from New Outlook’s header-based inline-image fetch calls.

Escalation Checklist for Microsoft Support: Capture exact UTC timestamps, affected mailbox types (personal vs. shared), and the exact Microsoft Outlook Version, Client Version, and WebView2 Version (under Settings > General > About Outlook). Attaching a browser HAR trace from OWA showing failing attachment upload calls cuts ticket turnaround time sharply.


Is Outlook Having a Different Image Problem?

If your image issue behaves differently from the outgoing send block above, check these three adjacent Outlook bugs:

  • High-DPI / Retina Clipboard Screenshot Bloat: Pasting screenshots from Windows Snipping Tool or macOS on 4K/Retina displays embeds multi-megabyte uncompressed PNG payloads into the HTML body. If Outlook hangs only on pasted screenshots, save the capture as a compressed JPG (or resize it below 1,500 px wide) before inserting it.
  • Pasted Images Act Like Text and Refuse to Resize in New Outlook: Certain New Outlook builds hit a WebView2 clipboard bug where Ctrl + V screenshots lock inline like text characters and cannot scale. Save the screenshot locally and insert it via Insert > Pictures.
  • Incoming Emails Show a Red X (“Right-click here to download pictures”): This is an incoming privacy restriction, not a send failure. In Classic Outlook, check File > Options > Trust Center > Trust Center Settings > Automatic Download—or verify with IT whether a Group Policy or the BlockHTTPimages DWORD registry key is blocking external HTTP images.

FAQ About Outlook Gets Stuck Loading Images Before Sending

Why does Outlook say “inline images are still loading” when I didn’t add any images?

Hidden visual assets frequently sit inside HTML emails you never created: 1×1 invisible tracking pixels copied from forwarded newsletters, spacer GIFs in signature tables, brand icons, and quoted screenshots buried at the bottom of long threads. Outlook blocks sending until every hidden inline element finishes syncing.

Why does Outlook say “attachments are still loading” when I didn’t attach anything?

Inside Exchange Online, inline images are stored as file attachments flagged with isInline: true and a contentId. Because Outlook pushes visible file attachments and embedded inline graphics through the same upload pipeline, a stalled signature logo or offline cache object can trigger either pop-up interchangeably.

Why does the error keep appearing after I delete my Outlook signature?

Erasing signature text inside an open compose pane does not always flush the stalled attachment object tied to that draft. If auto-insert signatures on replies/forwards is enabled under Mail > Compose and reply, Outlook immediately re-injects it on the next draft. Clear the default signature assignment in settings, close Outlook via Task Manager, and test a fresh compose window.

How long do inline images take to load in Outlook (and when does the 25 MB limit block them)?

Healthy inline graphics finish uploading in 5 to 10 seconds. If the prompt hangs past 30 to 60 seconds, waiting rarely clears it. Check total message size as well: inline images encoded in Base64 inflate by roughly 33%, so a few pasted high-resolution screenshots can silently push a draft past Exchange Online’s default 25–35 MB send limit and stall permanently.

How do I stop reply and forward chains from triggering this error?

Strip buried graphics from the quoted thread instead of starting from scratch. Delete the older thread below the horizontal divider line before clicking Send, or use Pop Out > Options > Switch to plain text (New Outlook) / Format Text > Plain Text (Classic Outlook) to drop every broken inline image from the reply instantly.

Why do shared mailboxes trigger “inline images are still loading” more than personal inboxes?

Auto-mapped shared mailboxes sync through delegated permissions and separate local storage containers inside New Outlook’s Offline Mode, making their local cache far more prone to synchronization deadlocks than your primary mailbox. Beyond disabling Offline Mode on desktop, opening the shared mailbox directly in OWA via your profile picture > Open another mailbox bypasses desktop offline caching completely.

How do I recover an Outlook draft that won’t save during the loading error?

Switch the frozen compose window to Plain Text (Pop Out > Options > Switch to plain text in New Outlook) first—dropping the locked inline object often lets AutoSave succeed immediately. If the UI is completely unresponsive, copy your text to Notepad, then open OWA and check Drafts to recover your last cloud-synced autosave copy before clearing your desktop cache.

Does Classic Outlook have this error, or is it only New Outlook and OWA?

New Outlook for Windows and OWA share the same web compose engine and header-fetch image loader, which is why this pop-up hits them overwhelmingly. Classic Outlook runs on a separate MAPI / OST desktop architecture—making it immune to New Outlook’s WebView2 and Offline Mode bugs unless local RoamCache files or a legacy COM add-in become corrupted.


Visit Our Post Page: Blog Page



Discover more from Izoate

Subscribe to get the latest posts sent to your email.

Leave a Comment

Your email address will not be published. Required fields are marked *