When images won’t load, clear cache, test another network, disable blockers, then check formats, DNS, and site errors.
You click a page and get broken icons or blank tiles. That stalls browsing. This guide gives fast checks, then deeper fixes for web, mobile, and apps. Follow these steps and stop once pictures return.
Quick Checks That Solve Most Cases
Start with simple moves. They clear stale data, dodge network quirks, and reveal blockers.
| Symptom | Fast Fix | Where |
|---|---|---|
| Blank boxes or broken image icons | Reload with Ctrl/Cmd+Shift+R to bypass cache | Browser |
| Some sites show photos, others do not | Open a private window and retest; extensions are off there | Browser |
| Images load on Wi-Fi but not on mobile | Turn off VPN, try a different network, or toggle Airplane mode | Phone |
| Only one site fails | Test the site on another device or a status checker | Any |
| Thumbnails load, full images stall | Wait 10–20 seconds, then try a different tab or quality setting | Any |
| Animated GIFs stuck | Disable power saver or low data modes temporarily | Any |
| Icons show, photos are blank | Enable JavaScript and images in site permissions | Browser |
| Only your site fails to show images on other domains | Turn off hotlink protection or allow your domain | Server/CDN |
Why Images Won’t Load: Common Causes
Cache Or Cookie Corruption
Cached files speed things up, but stale copies can point to dead URLs. Use a hard refresh first. If nothing changes, clear cache and site cookies. Logging back in may be needed.
Content Blockers And Privacy Tools
Ad blockers, tracking protection, and script filters can neuter image requests. Test in a private window or with extensions disabled. If pictures appear, re-enable add-ons and add the site to an allow list. Mozilla’s images not showing guide walks through common blockers and resets.
Permissions And JavaScript
If images are disabled at the site level, the browser will skip them. Open the padlock menu, review permissions, and set Images and JavaScript to Allow. Reset content settings if the switch is missing.
Mixed Content On HTTPS Pages
Pages served over HTTPS can’t safely fetch pictures over HTTP. Modern browsers block that. Developers should switch image URLs to HTTPS or use a proxy. If you maintain a site, look for mixed content warnings in DevTools and read MDN’s mixed content explainer for fixes.
DNS, Hosts File, Or VPN Routing
Bad DNS answers, custom hosts entries, or a flaky VPN can send image requests to the wrong place. Switch to a well known resolver, remove stray hosts entries, and pause VPNs. Flush the resolver cache if the same domain keeps failing.
Hotlink Protection And CORS Rules
CDNs can block image requests that come from other sites. That saves bandwidth but breaks embeds when not configured. If it is your site, allow your domain or turn that setting off while testing. Review CORS or referrer checks that gate image delivery.
Format Or Size Trouble
Old apps may not parse AVIF or big WebP files. Some email clients block external images by default. If you publish images, supply a JPEG fallback with the <picture> element, and keep file sizes sane. On slow links, giant photos time out or stall near the end.
Images Not Loading On Websites: Step-By-Step Fix
Work through these steps in order. Stop once pictures appear and stick across a few pages.
1) Hard Refresh And Basic Sanity Checks
Press Ctrl/Cmd+Shift+R to reload the page ignoring cached assets. Try another browser. Visit a site that always shows images, like a news page, to see if the problem is global or local.
2) Disable Extensions And Privacy Filters
Open an incognito or private window and load the page. If images return, disable extensions in the main window and re-enable them one at a time. Many blockers ship with lists that hide known ad slots; that can accidentally catch content images.
3) Reset Site Permissions
Click the address bar padlock. Set Images to Allow. Set JavaScript to Allow. Clear site data. Then reload. If your browser has per-site content settings, reset them to default.
4) Clear Cache And Cookies
Use your browser’s clear browsing data panel. Remove cached images and files and site cookies for the last 7 days. Close and reopen the browser after clearing to force a clean fetch path.
5) Check Network, VPN, And DNS
Move from mobile data to Wi-Fi or the other way around. Pause VPNs. Switch DNS to a public resolver like your ISP’s default or another reputable one. On Windows, run ipconfig /flushdns. On macOS, run dscacheutil -flushcache and killall mDNSResponder. Retest.
6) Look For Mixed Content Blocks
Open DevTools (F12), switch to Console or Security, and reload. If you see messages about blocked insecure image requests, the page is pulling files over HTTP while the page is HTTPS. That needs a site fix, not a client tweak. MDN’s mixed content page above matches those warnings line by line.
7) Test Format Support
Right-click the broken image and copy its address. If it ends in .avif or .webp, try opening it directly. If your app or older device lacks support, you will see a download dialog or blank page. Use another browser or a device that supports the format, or ask the site to serve JPEG fallbacks.
8) Bypass Hotlink Or CORS Blocks
If images live on a different domain, the host may block external sites. Site owners can allow their domain in hotlink settings or adjust CORS headers so cross-site image tags are permitted. When testing, serve a single test image from the same domain to confirm the block.
9) Inspect Hosts File And Security Tools
Look for entries that map popular CDNs to 0.0.0.0 or 127.0.0.1. Security suites sometimes add those. Remove the bad lines, save, and reboot. If a security tool offers web filtering, pause it briefly and retest.
10) Update Or Reinstall The App
Outdated browsers and apps mishandle new image formats or HTTP features. Update the browser. If the profile is corrupt, a clean profile or reinstall brings images back.
Mobile Fixes For iPhone And Android
iOS And iPadOS
Toggle Airplane mode off and on. Under Settings > Safari, clear history and website data. If you use content blockers, turn them off and reload. If Private Relay or a VPN is active, pause it. Update iOS and Safari, then restart the device.
Android (Chrome)
Turn off Data Saver variants. Clear site storage and cache. In site settings, set Images to Allowed and JavaScript to Allowed. If images only fail on mobile data, switch to Wi-Fi and retry. Update Chrome and WebView.
App And Email Cases
Some apps defer image fetches to save data or battery. In social or chat apps, visit settings and enable media auto-download on Wi-Fi. Many email apps block remote images on first open; tap “Display images” or set a trusted sender to load them by default.
When It’s The Website
If multiple devices show the same broken images for a single site, the fault sits server-side. Check if the direct image URL 404s, returns a 403, or stalls. Report the bad URL to the site with a screenshot, your browser version, and the time you tested.
Advanced: Read Browser Clues
Developer tools expose the exact reason a picture fails. Open Network, filter by Img, and reload. Look at Status, Type, and Size. A 200 with zero bytes means the server replied but sent no data. A 301/302 loop shows a redirect trap. A 403 hints at hotlink rules. A 415 means the server rejects the format.
| What You See | Likely Cause | Fix |
|---|---|---|
| Console says “Mixed Content” | HTTPS page pulls HTTP images | Switch image URLs to HTTPS |
| Status 403 on image host | Hotlink or referrer block | Allow your domain or serve locally |
| Status 404 | Wrong path or deleted file | Update the link or restore the file |
| MIME type mismatch | Server sends wrong Content-Type | Fix headers on the origin |
| Type shows AVIF, blank render | No AVIF support on device/app | Provide JPEG fallback or update |
| Net::ERR_NAME_NOT_RESOLVED | DNS resolution failure | Change DNS and flush cache |
| Cross-origin read block | Strict CORS policy on host | Relax headers for image tags |
Site Owner Fixes That Stick
Serve Images Over HTTPS
Load every asset over HTTPS and add a Content-Security-Policy that blocks mixed content. Replace absolute HTTP links in templates and editors, and set your CDN to rewrite to HTTPS.
Offer Fallback Formats
Use <picture> with AVIF or WebP first and JPEG fallback for old apps. Keep dimensions explicit with width and height so the page reserves space. Compress images to a practical size, under 300–500 KB for most photos.
Configure Hotlink Protection Wisely
If you enable hotlink protection, add your domains to the allow list and permit direct requests for testing. Confirm that referrer checks do not block RSS, email clients, or link previews that fetch without a referrer.
Use A Reliable DNS And CDN
Pick DNS with good reach and ensure your CDN edge returns correct content types. Add cache-control headers so repeat visits reuse images without stale failures.
Prevention Checklist
- Keep browsers and apps current.
- Audit extensions twice a year; remove what you do not use.
- Use HTTPS everywhere and monitor mixed content in releases.
- Publish AVIF or WebP with JPEG fallback.
- Limit file sizes; resize huge photos before upload.
- Use a sensible DNS and avoid stacking multiple VPN hops.
- Back up originals and CDN configs so rollbacks are easy.