Skip to main content

Favicon Auditor

checks presence & sizes of a site's icon set

Enter a domain or full URL. No protocol needed — example.com works.

Probing icon endpoints and reading page markup…

RESULT

—

0/0
Icon Source Detected size Recommended Status

  • What a complete favicon set looks like
    FileUsed forRecommended size
    favicon.icoLegacy fallback, browser tabs16×16, 32×32, 48×48 (multi‑size)
    favicon-32x32.pngBrowser tabs, bookmarks32×32
    favicon-16x16.pngBrowser tabs (small)16×16
    apple-touch-icon.pngiOS home screen180×180
    android-chrome-192x192.pngAndroid home screen, PWA192×192
    android-chrome-512x512.pngPWA splash / install prompt512×512
    safari-pinned-tab.svgSafari pinned tabsSingle-color SVG
    site.webmanifestPWA installabilityLists 192×192 & 512×512 icons
  • How this audit works

    The tool checks the standard icon file paths directly in the browser and reads back their actual pixel dimensions — this works regardless of the target site's server configuration.

    It also tries to read the page's <head> markup and any web app manifest to pick up icons declared at non-standard paths. That step depends on the target site allowing cross-origin requests (or a public CORS relay succeeding), so it's best-effort: a "not found" result there doesn't necessarily mean the icon doesn't exist, only that it wasn't declared at a default location or wasn't reachable this way.