Favicon Checker Tool Online

Last updated:

Audit any website favicon setup in seconds. Check icon tags, preview detected files, verify /favicon.ico, and flag missing sizes that affect browsers, search results, and mobile shortcuts.

Enter a URL to check its favicon setup:

How the Favicon Checker Works

The tool inspects the HTML head and default icon location to understand how your site appears in browsers and devices.

  1. Fetch the page, the API requests the URL with a timeout and safe host validation.
  2. Find icon tags, it looks for rel icon, shortcut icon, apple-touch-icon, mask-icon, and manifest links.
  3. Resolve URLs, relative icon paths are converted into absolute URLs.
  4. Check fallback, the tool sends a HEAD request to /favicon.ico.
  5. Report issues, missing desktop, Apple, Android, and manifest sizes are flagged.

Why Favicons Matter

Favicons are small, but they influence recognition, trust, and user experience across many surfaces.

  • Search visibility, Google may show a favicon next to your result, making your brand easier to identify.
  • Browser usability, tabs and bookmarks are easier to scan when the icon is crisp.
  • Mobile shortcuts, Apple and Android icon sizes control how saved websites appear on home screens.
  • Brand consistency, a complete icon set prevents stretched, blurry, or missing assets.

For where favicon and touch-icon tags sit among the rest of your head markup, see our complete meta tags SEO guide.

Recommended Favicon Sizes

A reliable favicon setup covers classic browser tabs, Apple devices, Android shortcuts, and progressive web app metadata.

SizePurposeTypical tag
16x16Browser tab fallbackrel="icon"
32x32Desktop and high density tabsrel="icon"
180x180iOS home screenrel="apple-touch-icon"
192x192Android app iconmanifest
512x512Large app icon and install promptmanifest

Favicon Files & Link Tags Reference

A complete favicon setup is a handful of files referenced from the page head and web app manifest. The table below shows each file, where it is declared, and what it powers across browsers and devices.

FileLink tag / locationPurpose
/favicon.icoServed at site root; requested automaticallyUniversal fallback browsers and crawlers fetch by default.
32x32 PNG<link rel="icon" type="image/png" sizes="32x32">Crisp desktop and high-density browser tab icon.
apple-touch-icon 180x180<link rel="apple-touch-icon" sizes="180x180">Icon for the iOS home screen.
192x192 PNGicons array in the web app manifestAndroid home screen shortcut icon.
512x512 PNGicons array in the web app manifestLarge icon for install prompts and splash screens.
SVG favicon<link rel="icon" type="image/svg+xml">Scalable modern icon; keep ICO/PNG as fallback.

A complete icon set is one small part of a polished technical foundation. Our SEO services build that foundation across favicons, schema, performance, and crawlability.

Next steps

Favicon Checker related tools and articles

Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.

Favicon Checker: FAQ

What does the Favicon Checker inspect?
It fetches the returned page HTML, finds link elements whose rel value contains icon, apple-touch-icon, mask-icon, or manifest, resolves their href values, and reports rel, declared sizes, type, and URL. It also sends a HEAD request to the final origin's /favicon.ico path.
Does the checker verify that every declared icon file loads?
No. Only the default /favicon.ico fallback receives an existence request. Other icon and manifest URLs are listed from markup without being downloaded or validated. Open unexpected URLs directly and confirm status, content type, dimensions, and image appearance.
Why are 192x192 and 512x512 reported missing even though my manifest contains them?
This implementation detects the manifest link but does not fetch or parse the manifest JSON. Its size checks use sizes attributes found on page link tags. Verify manifest icon declarations manually when those warnings appear.
How are the recommended-size warnings produced?
The report looks for declared 16x16, 32x32, 180x180, 192x192, and 512x512 size strings. A reachable /favicon.ico satisfies the 16 and 32 fallback checks, while apple-touch-icon and manifest-link checks are separate. These are implementation-completeness prompts, not a browser-support certification.
Why can a valid favicon link be missing from the report?
The HTML parser expects a recognizable link element and extracts common quoted attributes. Icons injected after load, manifest-only icons, unusual attribute syntax, or markup patterns outside the parser can be missed. Compare with rendered head markup and the browser network panel.
What should I fix after a favicon warning?
Add or correct the relevant link declarations, provide files at stable crawlable URLs, and make the manifest reference real 192 and 512 pixel icons where installation matters. Keep a working root favicon.ico fallback, then test browser tabs, bookmarks, iOS, Android, and search appearance separately.
Does a clean report guarantee that the icon looks good?
No. The checker does not inspect pixels, transparency, padding, contrast, maskability, or legibility at small sizes. Review the actual artwork at 16 and 32 pixels and on both light and dark browser surfaces.
What data is sent during a favicon check?
The public page URL is sent to the Web Aloha API. The server fetches its public HTML and sends one HEAD request to the origin's /favicon.ico path. Private-network hosts are blocked, no credentials are requested, and the endpoint contains no application-storage step for the URL or result.

Free 48-Hour Website Audit

Not sure what to fix first on your own website? We'll review it and tell you, in plain English. Free & non-obligatory.

Need a Complete Brand Icon System?

We build polished technical SEO foundations, from favicons and schema to performance and crawlability.