Broken Image Checker
Broken images make a page look abandoned and waste requests. This checker collects every image address a page uses – img elements, the largest srcset candidate, picture sources, the Open Graph and Twitter images and the icons – and tests up to 60 of them. Each result shows the status code, the content type, the file size and redirects, so you also find files that are not images, images over 500 KB and slow responses.
- Encrypted connection
- No sign-up
- Free to use
How to use Broken Image Checker
- Enter the page URL.
- Click “Check images”.
- Wait for the image tests to finish.
- Fix or replace the images marked red.
Broken Image Checker features
All image sources
img, srcset, picture, og:image, icons.
Status and type
Errors and non-image responses.
File sizes
Images over 500 KB flagged.
Redirects and speed
Redirected and slow images.
Up to 60 images
Checked in parallel.
Safe fetching
Only public http(s) addresses; private networks are blocked.
When to use Broken Image Checker
- Checking a page after moving media to a CDN.
- Finding images lost in a CMS migration.
- Confirming the social sharing image works.
- Spotting heavy images that slow a page.
Broken Image Checker FAQ
Why does an image show 403?
Some servers block requests without a browser referrer (hot-link protection). If the image shows on your site, it may still work for visitors.
Are lazy-loaded images included?
Yes, when the address is in src or data-src in the HTML. Images inserted only by JavaScript are not seen.
Which srcset image is tested?
The largest candidate, because it is the one most likely to be missing after a resize job.
Is the file size exact?
It comes from the Content-Length header when the server sends one, otherwise from the downloaded bytes of a partial request.
Why does an image work in my browser but fail here?
It may be cached in your browser, blocked for automated requests, or only available after logging in.
Find images that fail to load
Images are usually the heaviest part of a web page and a common source of errors after redesigns, CDN changes or media library clean-ups. A broken image is easy to miss on a page you no longer visit, but visitors and crawlers notice.
The checker reads the HTML the server sends and tests each image address from our server with short timeouts, like a crawler would. Images over 500 KB are flagged because they slow down pages on mobile connections – the image optimisers on this site can shrink them in your browser.
Use the Image Alt Text Checker to review the descriptions of the same images.
Tip: fix the problems marked red first, because they affect whether a page can be found at all. Yellow warnings are worth reviewing but are often harmless in context, and blue notes are information. After a change, run the check again to confirm the result – search engines will pick up the change on their next visit to the page.
A broken image shows an empty box or the alt text, which makes a page look neglected and wastes a request. The checker collects image addresses from img elements, the largest srcset candidate, picture sources, Open Graph and Twitter images and icons, and tests up to 60 of them.
Each result shows the status code, content type, file size and any redirect. Besides 404 errors, look for images that redirect (each redirect adds delay), images served with the wrong content type and unexpectedly large files.
Broken social images are easy to miss because they only appear when the page is shared. After fixing paths, clear your CDN cache and re-run the check.