Favicon, manifest and PWA checker

How to use it

1. 1Enter the address you want to checkType or paste it into the field marked "Address to check", including the https:// at the front. Any page on the site — icons are declared per page but are almost always site-wide.
2. 2Press Check and wait a few secondsThe request runs from our server rather than from your browser, so your cache, your extensions and your login session cannot affect the answer. That is the point of it: you are seeing what an anonymous visitor sees.
3. 3Look for icons that are declared and missingEvery declared icon is actually FETCHED. A tag pointing at a file that no longer exists is invisible to anyone whose browser has the old one cached, which is why this outlives most redesigns.
4. 4Check the sizes you actually needA favicon, an Apple touch icon at 180px and a 512px icon for the manifest cover almost everything. Missing ones are reported individually rather than as one failure.
5. 5Read the manifest findings as separate from the iconsA web app manifest with no name, no start URL or no icons is reported — but the tool does not claim the app is installable, because that needs a service worker, which is JavaScript and invisible to a raw fetch.
6. 6Share or keep the result within 24 hoursThe result has its own link you can send to whoever needs to act on it. It is deleted 24 hours after the check ran, so save anything you need to keep — and re-run the check after a change rather than trusting an old link.

About this tool

A favicon tag proves only that someone once wrote the tag. The icon that actually appears in tabs, bookmarks, search results and home screens is the file behind it — and when that file has been moved or deleted, the browser falls back to a blank square without reporting anything. Anyone who visited before the breakage still sees the old icon from cache, which is exactly why these stay broken for months.

This tool reads every icon declaration on a page — favicons, apple-touch-icon, Safari's mask-icon — and requests each file to confirm it exists and is an image. It also fetches the web app manifest and reads it the way an installing browser would: name, start URL, display mode, and whether the icon sizes Chrome requires for installation are declared.

Understanding the result

The declarations table shows each tag with the verdict from actually requesting the file: exists, a specific HTTP error, or HTML-instead-of-an-image (a soft 404 — the server answers 200 with an error page).

If no icons are declared, the /favicon.ico fallback is requested instead, because that is the address every browser silently tries.

The manifest section reports the install-relevant members and the two icon sizes that matter: 192×192, which Chrome requires before offering installation, and 512×512, used for the splash screen.

Example

https://example.com/

icon /favicon-32.png — exists · apple-touch-icon /apple.png — HTTP 404
manifest /site.webmanifest — readable · name "Example" · 192×192 ✓ · 512×512 missing
1 critical issue: the declared apple-touch-icon could not be retrieved.

Limitations

• Installability is not judged. Chrome's install prompt also requires a registered service worker, and registration happens in JavaScript — invisible without running the page. The result covers the metadata half and says so.
• Icon files are verified to exist and be images; their pixel dimensions are not decoded, so a 16×16 file declared as sizes="512x512" passes here.
• On pages with very many icon declarations, the first eight are fetched and the rest are listed as not fetched — the table says which.
• Requests to private and internal addresses are refused by design.

Questions