Favicon Checker
Collect and preview a site's ICO, PNG, SVG, Apple touch and web manifest icons on light and dark backgrounds.
Results are provided as is, for general information. Check anything important before relying on it. See the Terms of Use.
About Favicon Checker
Enter a public page URL to collect its browser icon declarations, Apple touch icons, Safari mask icons, linked web manifest icons and conventional /favicon.ico fallback. Our server retrieves the HTML, manifests and icon files after human verification. The gallery compares ICO, PNG and SVG files at 16, 32 and 64 pixels on light and dark backgrounds, alongside HTTP status, response MIME type, file dimensions, declared sizes, media and manifest purpose. File dimensions come from PNG headers or ICO directory entries; SVG is labeled scalable. Header recognition does not guarantee every image frame decodes. Broken resources remain visible. The checker reads raw HTML and does not run scripts or reproduce a particular browser's icon selection. It checks at most two linked manifests and sixteen unique icon URLs, with a 2 MiB HTML cap and 256 KiB cap per manifest or icon. Additional resources are reported as omitted. A combined 3 MiB result cap may omit previews while preserving their file metadata and source URLs.
When to use Favicon Checker
Favicon Checker FAQ
Which favicon types does it check?
It collects rel=icon links, including shortcut icon, Apple touch icon and Safari mask icon links, plus icons in linked web manifests. It also checks /favicon.ico at the final page's origin. ICO, PNG and SVG files get visual previews; other formats remain listed with an unsupported-format message. It does not guess additional PNG or SVG filenames.
Are declared sizes the same as file dimensions?
No. Declared sizes come from HTML or manifest metadata. The checker separately reads PNG dimensions and every ICO directory size. An ICO can contain multiple sizes in one file. SVG is shown as scalable rather than assigned a fixed pixel size. A warning appears when a raster declaration lists sizes absent from the file header or directory.
How are manifest icons found?
The checker follows manifest links in the page HTML, parses their JSON and reads each icon's src, sizes, type and purpose. Relative icon paths resolve against the final manifest URL after redirects. A missing purpose defaults to any. This is an icon inspection, not a complete manifest or PWA installation validator.
Does every website need ICO, PNG, SVG and a manifest?
No. These are different ways to supply icons for different contexts, not a mandatory checklist for every website. The checker reports what is declared and whether it can be fetched. A manifest is optional for an ordinary website. Browser and operating-system selection can vary; the gallery does not predict which file a particular device will choose.
Why might an icon be missing or different from my browser tab?
Browsers may cache icons, select a different size or media variant, or receive different HTML. This checker reads the server's HTML response without JavaScript and does not see declarations added later by scripts. A blocked request, invalid file, unsupported format or resource limit is shown in the results. Both previews use the same file with a light or dark color-scheme. SVG artwork that responds to prefers-color-scheme may adapt in supporting browsers.
Is the site URL sent to your server?
Yes. After a Cloudflare Turnstile check, our server fetches the page, linked manifests and icons through the existing guarded network fetcher. It refuses private network destinations and applies size and timeout limits. Icon previews return inline so your browser does not need to request the remote image host directly. Submitted URLs and retrieved files are not intentionally retained or logged by the tool endpoint.