Audit favicon coverage
Inspect favicon, Apple touch icon, mask icon, manifest, and Microsoft tile declarations from one page.
Favicon Checker
Free, no signup. Inspect every standard icon declaration, including the quiet fallbacks browsers use when a page does not declare anything.
Checks run from our server; we fetch the URL you enter and don't keep the results. The page HTML and optional manifest are retrieved through bounded fetchers. Icon images load directly in your browser for their dimensions. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.
+ saves the current site or page. Use ☆ beside any saved site, page, or list to favorite it. Recent check history appears below.
Create a named list
Target filled from your local choices.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Detected icons
Rate this tool
How it works
A browser tab, iPhone home screen, pinned tab, Windows tile, and a web app manifest can all use different declarations. This checker parses rel=icon, Apple touch icons, mask icons, manifest icons, Microsoft application metadata, and the conventional /favicon.ico fallback, then loads each candidate in your browser to inspect its natural dimensions.
Frequently asked questions
Why is favicon.ico included when it is not linked?
Browsers commonly request /favicon.icoA favicon ("favorite icon") is the small square image that represents a website — shown in browser tabs, bookmarks, and history, and (when the requirements are met) next to a site's listing in Google and Bing search results. It's declared with an HTML <link rel="icon"> tag in the <head>. It is not a ranking factor, but it affects brand recognition and click-through rate. as a fallback, so the tool includes it even when the HTML has no icon declaration.
Can this know an image’s dimensions?
It loads icon images directly in your browser to read their natural dimensions. If a host blocks the image, the tool says dimensions could not be read.
What does the manifest probe fetch?
Only the declared manifest is fetched through a bounded same-origin endpoint, with a small JSON cap, so the tool can list its icons.
Feature requests for Favicon Checker
Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
Where this tool helps
Common use cases
Preview common surfaces
Review how discovered icons may appear across browser, mobile, pinned-tab, and tile contexts.
Troubleshoot a missing icon
Find absent declarations, unreachable assets, or format and sizing gaps behind inconsistent display.
Preflight a rebrand
Verify that newly deployed icon assets and declarations are discoverable before retiring the old set.
Watch the full workflow
Favicon Checker walkthrough
Read the transcript
Favicon Checker
Favicons appear in more places than a browser tab, and one missing declaration can create inconsistent branding across bookmarks, search results, home screens, pinned tabs, and installed web apps. I’ll show you how to check a page, interpret coverage findings and dimensions, distinguish declarations from fallbacks, export the inventory, understand access limits, and fix the right source.
Step 1
Use this checker when a favicon is missing, blurry, stale, or inconsistent across surfaces. It inventories standard link declarations, Apple touch and mask icons, manifest icons, Microsoft metadata, and the conventional slash-favicon-dot-ico fallback.
Step 2
Enter a full public page U-R-L and select Check icons. The page H-T-M-L and optional manifest are retrieved through bounded fetchers. Candidate icon images then load in your browser so the tool can read their natural dimensions.
Step 3
Run the audit before a launch, after changing a site-wide head template, during a domain migration, when adding a web app manifest, or after a browser or search result shows the wrong brand mark. Check representative templates if their heads differ.
Step 4
Choose Try an example to load three illustrative sources: a standard icon, an Apple touch icon, and a manifest declaration. The tool runs the same rendering and coverage logic without claiming it fetched a real external site.
Step 5
Read Coverage findings first. Warnings point to common gaps such as missing scalable or device-specific coverage. A clean result means the common checks passed for the captured inputs; it does not guarantee every browser, crawler, or operating system will choose the same file.
Step 6
The preview row shows how the preferred detected candidate may appear in a browser tab, bookmark, Google result, and home-screen tile. These are consistency checks. Real surfaces can resize, mask, cache, or select a different declared asset.
Step 7
Use the detected-icons table as the evidence inventory. Compare each declaration type and declared sizes with the natural pixel dimensions, then open the resolved U-R-L if needed. A mismatch can reveal an incorrect sizes attribute, unexpected file, or duplicate declaration.
Step 8
The checker includes slash-favicon-dot-ico even when the H-T-M-L does not link it because browsers commonly request that conventional path. Treat it as a compatibility fallback, not a substitute for deliberate modern icon declarations.
Step 9
A declared web app manifest is fetched through a small bounded J-S-O-N probe so its icon entries can join the table. Verify each manifest purpose, size, type, and path in the deployed file, especially for installable or maskable app experiences.
Step 10
Download the C-S-V to hand off declaration types, sizes, dimensions, and U-R-Ls. Add the affected template, expected surface, owner, and fix status in your tracker so a site-wide asset issue is corrected centrally rather than patched page by page.
Step 11
A host may block direct image loading, so dimensions can be unreadable. A bounded or partial H-T-M-L response cannot prove a declaration is missing. Browser and search caches may retain old icons after deployment. The preview also cannot reproduce every platform’s selection behavior.
Step 12
Trace each warning to the shared head or manifest source. Add appropriately sized S-V-G or raster assets, accurate declarations, and stable public U-R-Ls. Deploy, check response status and content type, rerun this inventory, then verify the most important real browsers and devices after caches refresh.
Fix the declarations—then test real devices.
Update the shared head template and manifest with intentional icon files, sizes, and absolute paths. Deploy the change, confirm every asset returns the correct type without redirects or blocking, clear relevant caches, and test the browser tab, bookmark, search result, mobile home screen, and installed-app experience on real devices.
Common issues & how to fix them
- Error No favicon declaration is found Fix: Publish a valid favicon and declare it with a reachable link rel=icon URL in the document head.
- Information SVG favicon is missing Fix: Add an SVG rel=icon declaration for scalable modern-browser coverage while retaining a raster fallback.
- Warning Apple touch icon is missing Fix: Publish a 180×180 Apple touch icon and declare it with link rel=apple-touch-icon.
- Information Web app manifest is missing Fix: Publish a web app manifest with valid icon entries and link it from the document head when installable-app coverage is intended.
- Error Favicon URL is invalid Fix: Replace the malformed icon reference with a valid absolute or document-relative URL that resolves from the page.
- Error Declared favicon does not load Fix: Restore the declared icon URL so it returns an image successfully, or replace the declaration with a reachable asset.
- Warning Declared icon sizes leave a coverage gap Fix: Add raster icons for the missing declared sizes, including a 32×32 browser icon and 180×180 touch icon where applicable.