Browser and search
Declare a fetchable icon in the homepage head. The Favicon Checker and search crawlers do not treat an implicit /favicon.ico fallback as enough evidence.
HTML head
<link rel="icon" href="/favicon.ico" sizes="any">Favicon Checker
Use this favicon checker to test your website icon from a public URL. See whether the live files are present and valid.
Maintained by Icon Checker
Public resources are fetched through a constrained audit service. Private networks and unsafe redirects are blocked. Run the Favicon Checker on a public URL to inspect the live icon package.
Website release check
Remote URL audit
Trace the icon from markup to platform rule
The report keeps browser favicon behavior, Google Search eligibility, Apple touch icons, and PWA manifest coverage separate.
Final HTML
Redirected page, base URL, link declarations, and fallback favicon
Image evidence
HTTP status, detected format, dimensions, sizes, and MIME agreement
Platform rules
Stable rule IDs, observed values, expected values, fixes, and official sources
What is a favicon checker?
A favicon checker is a URL audit. It follows the public page, reads icon and manifest declarations, fetches the actual files, and identifies image formats from bytes. This favicon checker then applies browser, search eligibility, Apple touch, and PWA rules as separate findings.
What this favicon checker can prove
A pass from the Favicon Checker means the fetched evidence met the deterministic rules shown in the report. It does not guarantee display in a browser, on an Apple device, or in search.
| Surface | Measured evidence | Kept separate |
|---|---|---|
| Browser favicon | rel tokens, fallback, HTTP, bytes, size, MIME | Browser selection varies by context |
| Google Search | Home declaration, crawlability, square shape, 8 px minimum | Eligibility is not a display guarantee |
| Apple touch | Declared file, PNG format, measured 180 x 180 size | Not an iOS App Store icon rule |
| PWA manifest | Manifest JSON and measured 192 / 512 icon files | Not a search favicon rule |
How to use the Favicon Checker
Test the real public page, not a local file or image URL. The report follows declarations and resources a remote browser or crawler can request.
- 1
Enter the page URL for the Favicon Checker
Use the canonical https:// URL for the homepage or public page you want to inspect. The Favicon Checker rejects credentials, private network targets, unsafe ports, and unsupported protocols.
- 2
Let the Favicon Checker follow public evidence
The favicon checker follows allowed redirects, reads HTML and manifest links, then fetches each icon within fixed time, size, and resource limits.
- 3
Fix findings from the Favicon Checker
Fix failed fetches and mismatched files first. Then review search, Apple touch, PWA, warning, and manual findings separately.
Recommended markup for the Favicon Checker
These snippets match what the Favicon Checker measures. Add them to the server-renderedheador manifest, publish the files, and retest the live responses.
Apple touch icon
Use a 180 x 180 PNG for saved-to-home-screen support. It is not an iOS App Store icon.
HTML head
<link rel="apple-touch-icon" href="/apple-touch-icon.png" sizes="180x180">Web app manifest
Declare a manifest for installable web app icons. The Favicon Checker measures 192 x 192 and 512 x 512 files when present.
HTML head
<link rel="manifest" href="/manifest.json">manifest.json
{
"icons": [
{ "src": "/icon-192.png", "sizes": "192x192", "type": "image/png" },
{ "src": "/icon-512.png", "sizes": "512x512", "type": "image/png" }
]
}How to read your Favicon Checker report
Use the Favicon Checker report to fix failures first. Warnings, manual items, and partial reports mark uncertainty, not hidden passes.
| Result | What it means | What to do next |
|---|---|---|
| Pass | The fetched evidence met a deterministic rule in this audit. | Keep the measured value; it is not a display guarantee. |
| Fail | A value conflicts with a requirement, or a required resource could not be used. | Open the finding, apply its fix, publish the change, and run the URL again. |
| Warning | The evidence is incomplete, ambiguous, or outside a hard rule. | Check the response, markup, or recommendation before release. |
| Manual | The question depends on design or platform behavior automation cannot prove. | Inspect the preview and verify the relevant browser, search, or device surface. |
Common Favicon Checker problems and fixes
The Favicon Checker can find a package that works in one browser but remains incomplete elsewhere. Treat each surface as its own path from markup to a reachable file.
The browser uses /favicon.ico but the page has no icon link
Add an explicit rel=icon declaration in the server-rendered head. A conventional root fallback can work in some browsers, but it does not replace declared evidence for every surface.
Recommended markup
<link rel="icon" href="/favicon.ico" sizes="any">The declaration points to a missing or blocked file
Correct the absolute or relative URL, publish the file with a successful public response, and allow the relevant browser or crawler to fetch it. Remove redirect loops, authentication, and access rules that block the asset.
Declared and measured sizes do not agree
Export the intended pixel dimensions and update the sizes attribute so markup matches the file. Do not rename a small image to a larger size or trust an extension without checking the decoded bytes.
The favicon is not eligible for Google Search
Declare a square icon on the home page, keep both the page and file crawlable, and use at least 8 x 8 pixels. Google recommends an icon larger than 48 x 48 pixels, but meeting the requirements still does not guarantee display.
Recommended markup
<link rel="icon" href="/favicon.ico" sizes="any">Apple touch or PWA icons are missing
Add a separate Apple touch icon when saved-to-home-screen support matters, and declare installable web app icons in the manifest. These files serve different surfaces and should not be inferred from one browser favicon.
Recommended markup
<link rel="apple-touch-icon" href="/apple-touch-icon.png" sizes="180x180">
<link rel="manifest" href="/manifest.json">Icon markup exists only after JavaScript runs
Render essential icon and manifest links in the initial HTML head. A remote audit or crawler may not execute the same client code, wait for hydration, or receive the same regional response as your browser.
Recommended markup
<link rel="icon" href="/favicon.ico" sizes="any">Favicon Checker remote checks have limits
Blocked agents, cookies, JavaScript-only markup, or regional responses make the Favicon Checker return unknown or partial evidence.
Restricted outbound access
The fetcher has no database or internal bindings. It rejects credentials, private networks, unsafe ports, loops, oversized bodies, and expired deadlines.
When to use a different checker than the Favicon Checker
Use the Favicon Checker for a public website URL. A website icon package is not an app store icon, so use the dedicated PNG checkers for files going into Xcode or Play Console.
iOS App Store icon
An apple-touch-icon is a website file. The 1024 x 1024 Primary / Any App Store icon is a different PNG with different transparency rules.
Open iOS App Icon Checker
Google Play listing icon
A 512 x 512 PWA manifest icon is not a Play Console listing icon. The Play checker measures a 512 x 512 RGBA PNG locally.
Open Google Play Icon CheckerOpen Graph share tags
A favicon is not a share image. Use the Open Graph Checker to audit og:title, og:image, and Twitter metadata from a public URL.
Open Open Graph Checker
Official rules used by the Favicon Checker
Rules were reviewed on July 28, 2026 and carry stable IDs in every report.
The Favicon Checker maps Google Search Central's search eligibility, the WHATWG HTML Standard definesrel=icon, Apple documents touch icons, and W3C defines web app manifest icon records.
Favicon checker questions
The Favicon Checker answers stay scoped to evidence this audit can measure.