Inspect your favicon set.
Paste your public URL below. We'll fetch the page, the manifest and every declared favicon asset, then score each piece against platform expectations.
- Validating URL…
- Fetching page…
- Reading icon links…
- Fetching web manifest…
- Measuring icon assets…
- Scoring 14 checks…
Why use our Favicon Checker?
Comprehensive Analysis
We check all favicon formats including ICO, PNG, SVG, and web manifest icons with detailed validation for each platform.
Multi-platform Support
Verify your favicon works across Chrome, Safari, Firefox, iOS, Android, Windows, and progressive web apps.
Actionable Fixes
Get specific recommendations and HTML code snippets to fix missing or incorrect favicon declarations instantly.
Manifest Validation
We parse and validate your web manifest file, checking icon sizes, purposes, and color declarations for PWA readiness.
Visual Preview
See how your favicon appears in different contexts: browser tabs, bookmarks, mobile home screens, and app switchers.
Free & Unlimited
Check as many URLs as you want without limits. Perfect for agencies managing multiple client websites.
How to check your favicon
Paste Your URL
Enter the public URL you want to check in the input field above and click the check button.
Review Results
We fetch the page, parse the manifest and all favicon assets, then score each piece against platform expectations.
Fix & Implement
Get actionable recommendations and HTML code snippets to fix missing or incorrect favicon declarations.
Every icon size you actually need
A complete set is smaller than most guides claim. Seven files cover every browser, OS and home screen — everything beyond this is dead weight in your repository.
| Size | Format | Where it appears | Declaration |
|---|---|---|---|
| 16 × 16 | ICO / PNG | Browser tab (legacy), bookmark sidebar | /favicon.ico or rel="icon" |
| 32 × 32 | PNG / SVG | Browser tab, taskbar (modern browsers) | rel="icon" sizes="32x32" |
| 48 × 48 | PNG | Google Search results, Windows site shortcuts | rel="icon" sizes="48x48" |
| 96 × 96 | PNG | Google Search (minimum for reliable display) | rel="icon" sizes="96x96" |
| 180 × 180 | PNG (opaque) | iOS home screen | rel="apple-touch-icon" |
| 192 × 192 | PNG | Android home screen, PWA install | manifest icons (any) |
| 512 × 512 | PNG | Splash screen, install prompt, app stores | manifest icons (any) |
Sizes below 48 px are increasingly ignored by Chrome, which prefers the SVG or the largest raster available. If you ship only one modern asset, make it a 96 px PNG or an SVG with a crisp 16 px result.
Why your favicon is missing from Google results
Google renders a favicon next to every mobile search result, but only when the page clears four hard requirements. A valid tab favicon is not sufficient.
1 · It must be a square, and a multiple of 48 px
Google's documentation is explicit: the icon has to be square and its size a multiple of 48. A 32 × 32 or 180 × 180 asset is ignored for search. Ship at least 48 × 48 — 96 × 96 is the practical minimum for a sharp result on high-density screens.
2 · It must be crawlable and unblocked
The icon file has to return 200 to Googlebot. Favicons served from a path disallowed in robots.txt, or behind a CDN that challenges bots, will never appear — the page ranks, the icon stays generic.
3 · The homepage must be indexed
Google associates the favicon with the site's root domain, and it is only fetched once a page from that domain is indexed. A noindex homepage means no favicon in results, regardless of the markup.
4 · It must be declared with a full URL
Relative paths are resolved by browsers but are a common failure source when the head is rendered by a framework with a different base path. Absolute URLs in rel="icon" remove that class of bug entirely.
After fixing any of the above, expect a delay: Google re-crawls favicons on its own schedule, typically days to weeks. Requesting a re-index of the homepage speeds it up but does not make it immediate.
Favicon changed but the old one still shows
Browsers cache favicons far longer than other assets. Chrome and Safari keep them in a separate store that survives a normal refresh and sometimes a hard reload. Testing in a fresh profile, or appending a query string, is the only reliable way to see the new file.
The /favicon.ico fallback wins. If you replace the declared PNG but leave an old favicon.ico at the domain root, many clients still request and display it. Replace or remove both.
A stale service worker serves a stale icon. If the site ships a PWA, the cached manifest may reference the old asset. Bump the manifest version or the icon path so the worker refetches it.
CDN edge caches hold icons for weeks. Purge the icon path at the CDN, not just the page. Check the response headers for cache-control — a one-year max-age is common and means no client will see your update until it expires.
Frequently Asked Questions
What is a favicon checker?
A favicon checker is a tool that analyzes your website favicon setup across all platforms. It inspects your manifest file, icon sizes, and formats to ensure your brand icon displays correctly in browsers, mobile apps, and operating systems.
Why are favicons important?
Favicons are crucial for brand recognition and user experience. They appear in browser tabs, bookmarks, mobile home screens, and app switchers. A properly configured favicon set ensures your brand looks professional across all touchpoints.
What favicon sizes do I need?
Modern websites need multiple favicon sizes: 16x16 and 32x32 for browsers, 180x180 for Apple touch icons, 192x192 and 512x512 for Android and PWA. Our checker identifies which sizes you have and which are missing.
What is a web manifest file?
A web manifest (manifest.json) is a JSON file that defines how your website appears when installed as a progressive web app. It specifies icons, colors, and display settings for a native app-like experience.