Favicon Checker
Test any website's favicon in seconds. Enter a URL to check favicon.ico, the 16 and 32 px PNG icon tags, the Apple touch icon and the web manifest icons, then copy an HTML fix for anything missing.
What the favicon checker tests
Seven checks cover the files browsers, iPhones, Android and search engines look for. Each one comes back as PASS, FAIL (declared but broken) or MISSING (not declared at all).
| Check | PASS means | Common reason it fails |
|---|---|---|
| /favicon.ico at the site root | The file loads with a successful HTTP response. | File never uploaded, uploaded to a subfolder, or blocked by a redirect to an HTML page. |
| PNG icon tag, 16×16 | A <link rel="icon" sizes="16x16"> tag exists and its file loads. | Tag missing, or the href is relative (favicon.png instead of /favicon.png) and breaks on subpages. |
| PNG icon tag, 32×32 | A 32×32 PNG icon tag exists and its file loads. | Only a 16×16 icon is declared, so high-density screens upscale a blurry image. |
| Apple touch icon, 180×180 | A <link rel="apple-touch-icon"> tag points to a file that loads. | No tag, so iOS takes a screenshot of the page for the home-screen icon. |
| Web manifest link | A <link rel="manifest"> tag points to a JSON file that parses. | Manifest missing, served as HTML, or contains invalid JSON (often a trailing comma). |
| Manifest icon, 192×192 | The manifest lists a 192×192 icon and the file loads. | Wrong src path in the manifest, or the sizes value does not match the real image. |
| Manifest icon, 512×512 | The manifest lists a 512×512 icon and the file loads. | Missing, which stops Chrome on Android from offering a proper install icon. |
Who uses it
- Developers shipping a new site or redesign who want a quick check that every icon path survived the build and deploy.
- WordPress and Shopify owners who changed the site icon and want to know whether the theme is outputting the new files or an old hard-coded tag.
- SEO and agency teams auditing client sites — a missing favicon is one of the most visible gaps in search results and browser tabs.
Example: reading a typical report
A common pattern, simplified: a site built from a template years ago, with a working favicon.ico, a stale Apple touch icon path and nothing else.
PASS /favicon.ico (root) MISSING <link rel="icon"> PNG 16x16 MISSING <link rel="icon"> PNG 32x32 FAIL <link rel="apple-touch-icon"> 180x180 → /img/apple-icon.png returned 404 MISSING <link rel="manifest"> /site.webmanifest MISSING Manifest icon 192x192 MISSING Manifest icon 512x512
What it means, in plain terms:
- Desktop tabs work, because browsers fall back to /favicon.ico.
- The FAIL matters most: the page declares an Apple touch icon that no longer exists, so iPhones fall back to a screenshot. A FAIL is always a broken path, never a design problem.
- The MISSING rows are gaps rather than errors. Generating a full set and pasting the suggested HTML clears all of them in one go.
What the checker does not test
- Whether the image looks good. It confirms files load, not that a 16 px icon is readable on a dark tab. Use the light and dark previews in the generator for that.
- Real pixel dimensions. A file declared as 192×192 that is actually 64×64 still passes. Open the file and check its size if Android icons look soft.
- SVG favicons. An SVG link is optional, so it is not part of the seven checks.
- What Google has cached. Search results update on Google's schedule. See favicon not showing in Google.
- Sites that block automated requests. The page is fetched from our server. Firewalls and bot protection (for example a Cloudflare challenge) can return 403, which shows up as FAIL even though browsers load the icon fine.
Check it by hand
If a result looks wrong, these two commands show exactly what a browser receives:
# Status code and content type of the icon curl -sI https://example.com/favicon.ico | head -n 5 # Expect: HTTP/2 200 and content-type: image/x-icon (or image/vnd.microsoft.icon) # Every icon and manifest tag in the homepage HTML curl -s https://example.com/ | grep -Eio '<link[^>]+rel="(icon|shortcut icon|apple-touch-icon|manifest)"[^>]*>'
A content-type: text/html response for an icon URL means the server returned an error page or your homepage instead of the file — the most common cause of a FAIL on a file you are sure you uploaded.
How to fix what it finds
- Missing files: create them with the favicon generator (text, image, emoji or icon) — one ZIP covers every check above. Have a logo file already? Use SVG to favicon or PNG to ICO.
- Missing tags: copy the HTML fix the checker generates into your
<head>. It uses the paths found on your site where they exist. - FAIL on a file that exists: open the file URL from the results. A 404, a redirect to your homepage or an HTML response means the path or hosting rule is wrong.
- Wrong sizes: the favicon sizes guide lists every size and where it is used. For iPhone and Android icons specifically, see the mobile favicon guide.
- Everything passes but the old icon still shows: it is cache. Follow the favicon not showing guide for each browser, or this guide for Google Search results.