Favicon Checker
Review favicon, Apple touch icon, and web manifest references so you can spot missing or inconsistent icon coverage before publishing or troubleshooting site branding.
What this tool checks
Standard Favicon References
Checks for a conventional favicon file and linked icon declarations in the page markup. Use the result to confirm that browsers and other clients have a clear icon reference, then inspect any missing, conflicting, or inaccessible file before deciding what to change.
Apple Touch Icon Coverage
Looks for apple-touch-icon declarations used by iOS when a site is saved to a home screen. If the reference is missing or points to the wrong asset, review the page head and the referenced file so the saved-site icon reflects the intended brand asset.
Web Manifest Icon Coverage
Checks whether a web app manifest is referenced and whether it includes icon entries for installable or app-like experiences. Treat this as a configuration check: a manifest can support PWA presentation, but the presence of an icon entry does not by itself guarantee installation behavior or search visibility.
Why Consistent Favicon Coverage Matters
Favicons and related icon assets help identify a site across browser tabs, bookmarks, saved shortcuts, and some search interfaces. A missing, broken, or mismatched asset can create inconsistent branding across those surfaces, so the useful decision is whether each declared icon exists, is intentionally selected, and matches the context where it may be displayed.
Frequently asked questions
Which favicon and app icon sizes should I review?
The existing guidance on this page calls for 16x16 and 32x32 favicon assets, a 180x180 Apple touch icon, and a 512x512 manifest icon. Treat that set as a practical coverage checklist for this tool, then confirm the actual files referenced by your page and manifest are present, accessible, and appropriate for the surfaces you support.
Why should I check apple-touch-icon?
iOS can use an apple-touch-icon when someone saves a site to a home screen. Checking the declaration helps you confirm that the page points to the intended asset instead of relying on an absent, broken, or unintended fallback.