Broken Image Checker

Find every broken image on a page or an entire website. Paste a URL, choose single page or whole-site mode, and watch the live crawl as we scan each page, collect every <img> reference, and HEAD-check it for 4xx/5xx responses. Export the broken-image report as CSV or JSON.

How to Find Broken Images on a Website

1

Enter Your URL

Paste any webpage URL into the input field.

2

Watch the Live Crawl

Watch the live crawl as the tool checks every image on the page.

3

Review & Export

Review broken images with HTTP status codes and export as CSV.

Broken Image Checker

Find Broken Images Before Visitors Do

Broken images make a site look abandoned. The crawler walks every page, checks every image URL, and lists every broken file with its exact HTTP status code.

Run it monthly on large content sites and catch the silent rot from old uploads, expired CDN paths, and renamed files.

Why Use Our Broken Image Checker?

Single Page or Whole Site

Toggle between scanning a single URL (just that page) or the whole website (up to 100 internal pages). Whole-site mode does a breadth-first crawl, following only same-host links and skipping admin/asset paths so it stays focused on your actual content.

Smart Image Discovery

Each crawled page is parsed with DOMDocument so the tool catches every <img> element, including images loaded lazily via data-src. Image URLs are deduplicated across the entire crawl so the same image used on 20 pages is only HEAD-checked once.

Parallel HEAD Checks

After discovery, every unique image URL is HEAD-requested with a 7-second timeout. Six requests run in parallel from your browser, so even a thousand images finish in seconds. Servers that reject HEAD get a fallback Range-limited GET so the tool still detects 4xx/5xx responses.

CSV / JSON Export

Once the scan finishes, every broken image is listed with its status code, alt text, error description, and every page it appears on. Export the full report as CSV (Excel-ready) or JSON (developer-ready) with one click for follow-up fixes.

Frequently Asked Questions

Common questions about checking websites for broken images.

How does the broken-image check actually work?
Phase 1 fetches each crawled page server-side and parses the HTML with DOMDocument to extract every <img> src and alt. Phase 2 sends a HEAD request to each unique image URL with a 7-second timeout. Any HTTP response 4xx or 5xx (or a network error) marks the image as broken. Some servers block HEAD; for those, a tiny Range-limited GET is used as a fallback.
What is the page limit?
Whole-site mode is capped at 100 pages to keep scans fast and avoid surprising the target site. Most blogs and small business sites fit comfortably under that limit. For very large sites, run the tool on each section URL separately, or use a desktop crawler like Screaming Frog for a complete audit.
Why are some images marked as broken when they look fine in the browser?
A few possibilities: the image is loaded by JavaScript after page render (so it is not in the static HTML), the host blocks server-side requests by user-agent or IP, or the image needs cookies/auth to load. The checker only sees what server-side fetching can see, close to what Googlebot sees, which is what matters for SEO and accessibility.
Is my data stored?
No. The crawl runs entirely server-side per request, no database write, no logging of URLs you submit, no account required. The CSV/JSON exports are generated client-side from the result data and saved straight to your downloads folder.
Scroll to Top