Back to Blog
How-To Guide

Images Not Loading on Your Website? 9 Causes and Fixes

October 31, 202611 min read

Images stop loading on a website for one of two reasons: something on the visitor's side is blocking them (an extension, cache, or browser setting), or the image is broken on the site (a wrong file path, a file that was never uploaded, an insecure http:// link, or a format the browser can't display). The fastest way to tell them apart: open the page on a different device or network. If images load there, it's your browser. If they're broken everywhere, it's the website, and the causes below will help you fix it.

Quick answer

  • Only broken for you? Hard-refresh (Ctrl+Shift+R / Cmd+Shift+R), disable ad blockers and extensions, or try another browser.
  • Broken for everyone? Open DevTools → Network → filter "Img". Red 404s mean wrong paths or missing files, 403s mean permissions or hotlink protection.
  • Broken only in some browsers? Likely an unsupported format (HEIC, AVIF, WebP on old Safari).
  • Broken after a migration or redesign? Files weren't moved, or links still point to the old domain or staging site.

If images aren't loading only for you

Try these quick fixes in order. If none work and images still fail on other devices too, skip to the site-owner causes below.

Hard refresh the page

Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac reloads the page without cache. On a phone, close the tab and reopen it, or clear the browser's cache.

Disable ad blockers and extensions

Ad and privacy blockers hide images whose URLs look like ads (paths containing "ad", "banner", or "sponsor"). Try a private window, where most extensions are off.

Check image settings

Chrome (Settings → Privacy and security → Site settings → Images) and Firefox can be set to block images, globally or for one site. Data-saver modes and some antivirus web shields can also strip images.

Try another browser or network

If images load on mobile data but not on your Wi-Fi, a network filter or DNS setting is blocking the image server, which is common on office and school networks.

If images are broken for everyone: the 9 causes

1

The file path is wrong

Most common
A typo, a moved folder, or a relative path that breaks on sub-pages (images/photo.jpg works on the homepage but not at /blog/post/) all produce a 404. Most web servers are also case-sensitive: Photo.JPG and photo.jpg are different files. Right-click the broken image → "Open image in new tab" to see the exact URL the browser requested.
2

The file was never uploaded (or was lost in a migration)

Images that worked on staging or on the old site often 404 in production because the files were never copied over, or because links still point to the old domain or staging URL. This is the single most common cause after a redesign, host move, or platform switch.
3

Mixed content: http:// images on an https:// site

Browsers upgrade or block insecure http:// images on secure pages. If the image server doesn't support https, the image fails without an error. Search your pages and database for "http://" image links and change them to https://.
4

Unsupported image format

HEIC photos (the iPhone default) don't display in Chrome or Firefox. AVIF and WebP don't work on older iPhones and Macs that can't update Safari. If images fail only in certain browsers, convert to JPEG or PNG, or serve modern formats with a fallback using the <picture> element.
5

Permissions or hotlink protection (403 Forbidden)

A 403 means the server refused to send the file, because of file permissions set too strictly or hotlink protection that blocks images from being displayed on other domains. Check the folder permissions on your host and your CDN or host's hotlink settings, especially if you recently changed domains.
6

Lazy loading that never triggers

JavaScript lazy-loading libraries swap in the real image (from a data-src attribute) when you scroll to it. If that script fails or conflicts with another plugin, images stay blank forever. Native lazy loading (loading="lazy") is safer. If you use a lazy-load plugin, disable it temporarily to test.
7

External image links have expired

Images hotlinked from another site, an old CDN, or expiring signed URLs (from cloud storage) break when the source moves or the link expires. Host important images yourself or on a CDN you control.
8

A security policy is blocking the image source

A Content Security Policy (CSP) header with an img-src rule blocks images from any domain not on its list. The browser console shows a clear "Refused to load the image" error. Add the image's domain to img-src.
9

Images are too large and time out

Multi-megabyte images can fail or appear half-loaded on slow mobile connections. Resize images to the size they're displayed at, compress them, and use a CDN. It fixes loading failures and speeds up the whole page.

What image error messages mean

The message or icon you see points to the cause. Right-click the broken image and choose "Open image in new tab", or check the browser console, to see which one you have.

What you seeWhat it meansFix
Broken image icon, or alt text where the image should beThe browser asked for the file and got an error or something that isn't an imageOpen the image URL in a new tab and read the status code
"Image could not be loaded" / "Image failed to load" / "Unable to load image"An app or browser could not download the file: timeout, blocked request, or the link no longer existsRetry on another network; if it fails everywhere, the file or link is broken
"Image not found"The server has no file at that address: it was moved, renamed or deletedVisitors: nothing to fix. Site owners: re-upload the file or correct the link
"Image not available" / "Image unavailable"The site or app removed the file, or it's restricted in your region or accountNothing to fix as a visitor. Site owners: re-upload or remove the reference
"Images could not be shown right now. Please try again."An app or service failed to fetch its images, usually a temporary fault on its sideWait a few minutes and retry on another network. If it lasts, contact the service
"Could not load image details (error: http)"An app asked its server for an image and the HTTP request failedCheck your connection, update the app, and retry. If it persists, the app's server is at fault
"Oops! Image didn't load."The site's own error text for a failed image requestReload the page. If it repeats on another device, tell the site owner
404 Not FoundWrong path, wrong letter case, or the file was never uploadedCorrect the path or upload the file
403 ForbiddenFile permissions or hotlink protection refused the requestFix permissions or allow your domain in hotlink settings
500 / 503 server errorThe image server or resizing service crashed or is overloadedCheck the host or CDN status and logs
net::ERR_BLOCKED_BY_CLIENT in the consoleAn ad blocker or privacy extension blocked itDisable extensions; site owners can rename paths that look like ads
"Mixed Content" warning in the consoleAn http:// image on an https:// pageChange the link to https://. See mixed content
"Image URL does not have a file type"An editor or app only accepts direct links ending in .jpg, .png or .webpUse "Copy image address" to get the direct file URL, not the page URL

Images not loading on Shopify, WordPress, Wix or Squarespace

Shopify

Product images that vanish after a theme update are usually a section setting or a lazy-load script in the new theme. Images inserted into descriptions from another site break when that site removes them. Upload images to Shopify's Files instead of hotlinking.

WordPress

After a domain or HTTPS move, image URLs in the database still point at the old address. Update the site address, run a search-and-replace on a backup, and regenerate thumbnails if only some sizes fail. Lazy-load and optimisation plugins are the next suspect.

Wix and Squarespace

Images rarely 404 on hosted builders. When they look missing, it's usually a section hidden on mobile, an image placed off-canvas in the mobile editor, or an embedded code block loading images from another site.

How to find every broken image on your site

Checking pages one by one works for a single page. For a whole site, you need a tool, and the type of tool matters. An SEO crawler reads your HTML and flags image URLs that return 404, but it doesn't render the page, so it misses images injected by JavaScript, lazy-loaded images that never appear, and images that only fail on certain screen sizes.

Find them with a scan: BugSense loads your pages in a real browser at mobile, tablet, and desktop sizes, records every failed image request, and flags the blank or broken image slots customers see. Run a free scan. No account needed. Comparing options? See the best website bug detection tools.

Frequently asked questions

Why are images on websites not loading?

If only you are affected, it's usually cache, an ad blocker or extension, a browser image setting, or your network. If everyone is affected, the site has a broken image path, a missing file, insecure http:// image links, an unsupported format, or a server permission problem.

Why are my pictures not showing up on my website?

The most common causes are a wrong file path or file name case, files that were never uploaded after a migration, http:// links on an https:// site, HEIC or other unsupported formats, and lazy-loading scripts that fail. Right-click the image and open it in a new tab to see the exact error.

How do I get images to load on a website?

Hard-refresh the page, disable extensions, and try a private window or another browser. If you own the site, use the browser's Network tab to find the failing image requests and fix the path, format, or permissions.

Why are images not loading in Safari but loading in Chrome?

Usually an image format older Safari versions can't display (such as AVIF, or WebP on old devices), or a Safari privacy feature blocking an image served from a third-party domain. Serve JPEG or PNG fallbacks and host images on your own domain or CDN.

Why are some images not loading on my iPhone?

Check Low Data Mode, content blockers in Settings → Safari → Extensions, and whether the site uses a format your iOS version doesn't support. If images fail on every iPhone, the site itself needs fixing.

Why can't I see pictures on any website?

If images fail on every site, the cause is on your side: an ad or privacy extension, images turned off in browser settings, a data-saver mode, antivirus web filtering, or a network filter. Try a private window, then another browser, then mobile data.

What does "image could not be loaded" mean?

The browser or app could not download the image file. It is usually a temporary network problem, a blocked request, or a link to a file that no longer exists. If it fails on every device and network, the website needs to fix or re-upload the image.

What does "image not found" mean?

The server has no file at the address the page asked for, so it returned a 404. The file was moved, renamed or deleted, or the link has a typo. Visitors can't fix it. The site owner has to re-upload the file or correct the link.

How can I tell if a website's images are broken for everyone?

Open the page on mobile data or another device, or paste the URL into a server-side checker such as the one on this page. If the images fail there too, the website is broken for every visitor. If they load, the cause is your browser, extensions or network.