Images Not Displaying in Emails: Why Clients Block Them

Images not displaying in emails is almost never a broken internet connection. It is usually deliberate. Email clients block remote images by default because every image request pings the sender's server and reveals that your address is live, what time you opened the message, and sometimes where you are. The same mechanism that stops tracking pixels from loading also stops legitimate images from loading.

The sender's fix and the recipient's fix are different problems that share a symptom. If you received a message with blocked images, your client is making a privacy decision on your behalf. If contacts tell you they cannot see the images in your emails, the problem is your image URL or your hosting setup. This guide covers both halves, in the order you are most likely to need them.

What actually causes images to not display in emails#

Five causes account for the vast majority of blocked or broken email images. Match your symptom to the cause before you try a fix — a recipient cannot repair a broken URL, and a sender cannot whitelist themselves inside another person's mail client.

Fix 1: How to always show images from a specific sender#

If your email client is blocking images from a sender you trust, the fix is to add that sender to your trusted list. Your client will then download images from their address without asking each time. The steps differ by client, but the pattern is consistent: open the message, find the images-blocked banner, and choose to always allow images from that address.

1. 1

   Gmail (desktop browser)

   Open the message. At the top of the email body, Gmail shows a banner that reads 'Images are not displayed'. Click 'Always display images from [sender address]'. Gmail saves this preference for that sender going forward. To apply it globally for all external senders, go to Settings, then See all settings, then General, and under Images choose 'Always display external images'.

2. 2

   Gmail (mobile, iOS and Android)

   Open the message. Tap the three-dot menu in the top-right corner of the message. Tap 'Show images' to load them for this message only, or tap 'Always show images from [sender]' to make the preference permanent for that address.

3. 3

   Outlook (Windows desktop)

   Open the message. The infobar at the top reads 'To protect your privacy, Outlook blocked automatic picture download'. Click 'Download Pictures' to load images for this message. To trust the sender permanently, right-click the infobar and choose 'Always Download Pictures from [domain]'. A global override is at File, then Options, then Trust Center, then Trust Center Settings, then Automatic Picture Download.

4. 4

   Outlook (Mac desktop)

   Go to Outlook, then Preferences, then Email, then Reading. Under 'Automatically download pictures in HTML email from', choose 'Anyone' or 'My Contacts'. For a single sender, open their message and click 'Always Download Pictures from [domain]' in the banner at the top of the email.

5. 5

   Apple Mail (macOS)

   Go to Mail, then Settings on macOS Ventura and later (or Preferences on older versions), then Privacy. Uncheck 'Block All Remote Content'. Apple Mail does not offer a persistent per-sender allow rule through its UI — you allow all remote content or none. For selective per-sender control, a third-party extension is needed.

Fix 2: Repairing a broken image URL#

If contacts see a red X, a broken-image icon, or a blank space where your image should be — and you did not host it behind a login — the most likely cause is a broken or expired URL. Images get moved, deleted from the original host, or stored on services that generate short-lived links. The fix is to re-upload the image to a stable, public host and update the link in your template.

Before you fix it, confirm the URL is broken: paste it into a private browser window. If it returns a 404, a redirect, or any page that is not the raw image, the URL needs to be replaced.

1. 1

   Confirm the URL is broken

   Right-click the broken image placeholder in your sent email or a preview and choose 'Copy Image Address' or 'Inspect'. Paste the URL into a private browsing window. A 404, a redirect to a homepage, or a login wall confirms the URL is broken or private.

2. 2

   Re-upload to a stable host

   Use your email platform's built-in media library — Mailchimp, ConvertKit, Klaviyo, and similar tools all include one. Alternatively, use an S3-compatible bucket with a public-read policy or Cloudflare R2. The host must return the raw image file to any unauthenticated request.

3. 3

   Update the template

   Replace the old URL in your HTML or template editor with the new hosted URL. One wrong character breaks it — paste rather than type.

4. 4

   Test across two clients before sending

   Send a test to a Gmail address and an Outlook address. These two clients are the most common and have the most differences in how they handle images. If both load the image correctly, the fix held.

5. 5

   Use a stable asset library going forward

   If your process generates a new image URL every time you export a template, switch to a hosted asset library where the URL is fixed and does not change on re-export. Regenerated URLs are a common cause of broken images in re-sent or duplicated campaigns.

Fix 3: Images that load for you but not for recipients#

A specific and very common variant is when you can see the image in your sent copy — because you are logged in — but recipients see a blank or a login prompt. This happens when the image is stored on Google Drive, Dropbox, SharePoint, or OneDrive. Even a file set to 'anyone with the link can view' is not a public CDN link. It is a sharing permission designed for human access, and most email clients — particularly Outlook — block or fail on it.

1. 1

   Test the URL without being logged in

   Open a private browsing window and paste the image URL into the address bar. If it redirects to a login page, shows a permissions error, or loads a sharing page rather than the raw image file, recipients without an account on that service will see the same thing. This confirms the host is the problem.

2. 2

   Download the original file

   Get the source image file from Drive, Dropbox, or wherever it currently lives.

3. 3

   Upload to a public image host

   Use your email platform's media library, an S3 bucket with a public-read policy, or a CDN. After uploading, test the resulting URL in a private window — it should load the raw image file with no redirect and no login prompt.

4. 4

   Replace the URL in your email and test externally

   Update your HTML or template with the new public URL, then send a test to an external inbox that is not your own account. Your account may load the authenticated version regardless, so the external test is what confirms the fix for recipients.

How to tell which cause you have#

The fastest diagnosis is to match what you see on screen to one of the symptoms below and follow the pointer.

• You see the image fine but a contact reports they cannot — the URL is likely public, but the host may be authenticated or the link may be broken in a way only you can see because you are logged into the hosting service. Test the URL in a private window.
• You see a 'Download images' banner yourself when you open the message — your client is applying its default block. The image URL is probably fine. Use Fix 1.
• Some recipients see images and some do not with no clear pattern — the image URL is reachable but may be slow, rate-limited, or restricted geographically. Move to a CDN with broader availability.
• The image loads in most clients but shows a red X only in Outlook — Outlook validates image URLs more strictly than most clients. Check for redirects in the URL and confirm the server returns a Content-Type header that is an image MIME type rather than text/html.
• The image strips for recipients on corporate networks even though you hosted it publicly — a security gateway or antivirus appliance is removing inline base64-encoded images. Switch from embedded inline images to externally hosted links that the email references by URL.

Preventing it#

For senders: use a purpose-built CDN or your email platform's media library for every image, every time. Never embed large base64 inline images or use authenticated storage links. Test every campaign by sending to a Gmail address and an Outlook address before it goes to your list. Keep image files under 100 KB where possible — oversized images are more likely to be stripped or timed out by security gateways.

For recipients: add legitimate senders to your contacts or your trusted-senders list. Most clients treat your contacts as a signal to download images automatically, making this the lowest-friction route. If you are on a corporate network, your IT team may have set a central policy and the option may not be available to you.

The reason your client blocks images by default is the same reason tracking pixels work at all: every image request is a network call that tells the sender your address is live and when you opened their message. AI Emaily's privacy model intercepts known tracking pixels before they load, so you can allow images from senders you trust without exposing your read receipt to bulk mailers you did not invite. We build AI Emaily — how the privacy model handles tracking is in the documentation linked below.