Icon files your page declares and icon files the browser receives are not always the same set.
Paste any URL. Headicons reads every <link> declaration in the page
head, fetches each icon file, parses the actual pixel dimensions from the binary headers,
and reports which are present, which are missing, and which serve the wrong format —
per consumer (browser tab, iOS home screen, search result).
What the tool does
One input field, one table of results. You supply a URL. The tool reads the page's
<head>, extracts every icon declaration with its sizes
and type attributes, then fetches each one and parses the actual image
binary headers to get real pixel dimensions.
- Reads all
<link rel="icon">,apple-touch-icon, andshortcut icondeclarations - Also checks the two root-path conventions browsers request without a declaration:
/favicon.icoand/apple-touch-icon.png - Parses PNG, JPEG, GIF, WebP, ICO and SVG binary headers for actual pixel dimensions
- Reports which icon each consumer (browser tab, iOS home screen, search result) would actually use
- All fetching happens server-side — no CORS issues, no browser limitations
- No accounts, no saved history, no monitoring over time
How it differs from generic advice
"Clear your cache" tells you nothing is wrong with the files. Headicons tells you which file is absent — a column of facts next to the file path, not a troubleshooting guide.
What it cannot do
Headicons does not generate images, offer design opinions, or monitor icons over time. It is a stateless diagnostic probe: paste a URL, read the result, fix the file.
Platform limitation: Some hosts behind Cloudflare may report as unreachable because the Workers runtime cannot open a socket back into its own network. These hosts appear as "missing" even when the icon files are present. Known Workers limitation.