Broken Image Checker
Last updated:
Scan any page and find images that fail to load. We request every image and report the broken ones with their status codes, so you can fix missing files before visitors and crawlers see them.
Enter a page URL to scan for broken images:
Found issues? That’s exactly what our SEO audit fixes.
Our SEO Audit + Essentials package ($555, one-time) finds and fixes exactly these kinds of problems, with a prioritized plan in plain English.
Looks clean here. How is the rest of your SEO?
One passing check doesn’t make a ranking strategy. We audit the full picture: content, technical SEO, internal links, and search intent.
Want us to act on this result? Fix these findings →
Prefer the partnership route? Refer clients to us, earn 10% →
How the Scanner Works
- Fetch the page, the host is validated, then the HTML is read.
- Collect images, every img src and first srcset candidate is gathered.
- Test each one, images are requested and their status codes recorded.
- List the broken ones, you get a clear report of what failed.
Why It Matters
- User trust, missing images make a site look neglected.
- Layout stability, broken images can worsen layout shift.
- Image SEO, missing files cannot rank in image search.
- Crawl efficiency, fewer dead requests for bots to chase.
Broken images tend to creep in over time as files get renamed, moved, or deleted, which is exactly the kind of slow rot our website maintenance services catch and fix before your visitors do.
Common Broken-Image Causes & Fixes
Most broken images trace back to a handful of recurring causes. Match the symptom you are seeing, usually a status code or a blank space where the picture should be, to the cause below, then apply the fix. The scanner above reports the status code for each image to help you tell these apart.
| Cause | Symptom | Fix |
|---|---|---|
| 404 / wrong path | Image returns 404; the src points to a folder or filename that does not exist. | Correct the src (and srcset) to the real file location; watch for missing segments after a migration. |
| Renamed / deleted file | Previously working image now 404s after an edit, cleanup, or media-library change. | Restore or re-upload the file, then update the link to the new URL. |
| Mixed content (http on https) | File exists but is blocked; browser console warns about insecure content on an HTTPS page. | Serve every image over HTTPS; update hard-coded http URLs to https. |
| Hotlink blocked | External image returns 403; it loads on its origin but not when embedded on your site. | Host your own copy of the image, or get a permitted, stable URL. |
| Case-sensitive path | Image 404s on Linux hosting though it worked on Windows or macOS. | Match the filename case exactly (e.g. photo.jpg vs Photo.JPG). |
| Lazy-load misconfig | Blank or placeholder image; the real URL sits in data-src and never swaps in. | Ensure the lazy-load script initialises; provide a valid fallback src or noscript image. |
If broken assets keep reappearing, ongoing website maintenance services monitor your pages and fix missing images, mixed content, and bad paths before visitors notice.
Next steps
Broken Image Checker related tools and articles
Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.
Broken Image Checker: FAQ
What does the Broken Image Checker scan?
Which responses are marked as working or broken?
Why does the report say the scan was truncated?
How does the checker handle srcset and lazy-loaded images?
Are missing alt text and broken image requests the same issue?
Why might the checker report a false failure?
How should I fix a confirmed broken image?
What data is sent during a broken image scan?
Free 48-Hour Website Audit
Not sure what to fix first on your own website? We'll review it and tell you, in plain English. Free & non-obligatory.
Want a Polished, Fast Website?
We audit and fix broken assets, optimise images, and tune Core Web Vitals for a flawless experience.