Broken Image Checker

Paste a URL to find every image on the page that fails to load — moved files, expired CDN links, and typo'd paths. Free, instant, no signup.

What this checks & how to fix it

It fetches the page, collects every unique image URL referenced by an <img> tag, and sends a lightweight request to each one to confirm it actually loads. Anything that returns an error status, times out, or fails outright is reported as broken.

How to fix what it finds

Most broken images trace back to one of three causes: the file was moved or renamed without updating the reference, a CDN or hosting migration changed the base URL, or the source was a hotlink to another site that has since removed the file. Re-point the src at a working copy — ideally self-hosted — and re-run the check to confirm.

Frequently asked questions

How is this different from the Broken Link Checker?

The Broken Link Checker follows every <a> link on the page — links to other pages, whether internal or external. This tool checks a completely different set of URLs: every <img> source the page loads. A page can pass one check and fail the other.

Why does it show some images as "unverified" instead of broken?

A handful of image hosts (Instagram, some CDNs, some stock-photo services) block or rate-limit automated HEAD/GET requests, returning 401, 403, or 429 regardless of whether the image actually exists. Those are reported separately rather than counted as broken, since the check itself was blocked — not necessarily the image.

Does a broken image actually hurt SEO?

Indirectly, yes. A broken image is a bad user-experience signal, wastes any alt-text relevance the image could have carried, and if enough images 404 on a page it starts to look neglected — both to visitors and, over time, to how a crawler evaluates the page's overall quality.

Why is there a limit on how many images get checked?

Checking every image on a page with hundreds of them would take minutes and put unnecessary load on the target server. The check covers the first batch — typically more than enough to catch a systemic problem like a moved image folder or an expired CDN.

Does this check background images set in CSS?

No — only <img> tags (including their src, data-src, and the first candidate in a srcset). Images referenced purely through CSS background-image aren't part of the page's HTML and aren't checked here.

Related tools

Command Palette

Search for a command to run...