Bulk up to 100 • Extract images • Validate via HEAD/GET

Image Links Checker

Paste page URLs — we’ll extract image URLs and flag broken images, redirects, loops, and wrong content-types.

Paste up to 100 page URLs (one per line)
Limits: max 50 images per page, max 500 checks per run. If HEAD is blocked, we fallback to a small GET request.

Results

Page Image HTTP Hops Time Issues
Run a check to see results here.
A “not an image content-type” warning can indicate tracking pixels, HTML errors, or blocked hotlinking.

Quick interpretation

Broken images hurt UX, speed metrics, and trust. Fix missing files and mixed-protocol or blocked hotlinks.

  • OK image returns 2xx and content-type looks like image/*
  • Warning wrong content-type, hop limit, no images found
  • Error 4xx/5xx, fetch error, redirect loop
Media health

Image Links Checker: find broken images in bulk

Images disappear, move, or get blocked. This tool extracts image URLs from your pages and validates them with HTTP checks, including redirect handling and content-type sanity.

Common problems

  • 404/410 — missing file
  • Hotlink protection — returns HTML or 403 instead of an image
  • Redirect chains — slows load and can fail for some bots

FAQ

What does Image Links Checker validate?

It fetches each page, extracts image URLs from HTML (<img>, common lazy-load attributes, and srcset/<source>), resolves relative URLs to absolute, and then checks each image URL with HTTP.

Why do you use HEAD first and then GET?

HEAD is fast and usually enough to confirm status and headers. Some servers block HEAD (405/403/501) or return status 0, so the tool falls back to a small GET range request to verify the image without downloading the whole file.

What does “not an image content-type” mean?

The URL responded, but the Content-Type header isn’t image/*. Common causes: hotlink protection returning HTML, login pages, CDN/WAF blocks, or a broken URL that redirects to an error document.

Does it check images loaded by JavaScript?

Only if the image URL is present in the HTML markup (src, data-src, srcset, etc.). If a site injects images only after JS runs, they may not appear in the report.

Why do I see “No images found” on a page?

Either the page has no <img>/<picture> images in the fetched HTML, the request was blocked and returned a simplified/empty HTML, or images are loaded only via JS/CSS.

Why are there limits (50 images per page / 500 total)?

Some pages have hundreds or thousands of images. Limits keep checks fast, prevent server overload, and avoid timeouts on shared hosting. For audits, test key templates first (home, category, product/article).

Is a 200 status always OK?

Not always. A URL can return 200 but still be wrong if it’s HTML (wrong content-type), a tracking pixel, or a blocked response. That’s why the tool also shows Content-Type and flags non-image responses.

What should I fix first?

Start with 4xx/5xx broken images and redirect loops. Then reduce redirect chains and investigate “not an image content-type” warnings (often hotlink protection or wrong URLs).