Favicon Checker

Check which favicons a website declares and how they render

100% free. This tool needs our server to do the work, so what you submit is sent there, processed and then discarded - it is never stored.

Jump to the next useful tool without leaving your flow.

See more

About this tool

Check which favicon(s) a website has declared - the small icon shown in browser tabs, bookmarks, and search results - and shows how they actually render across different contexts. Useful for verifying your favicon setup is complete and displaying correctly everywhere it should.

How to use this tool

  1. Enter website URLFetch declared favicon links and icon manifest references from the page head.
  2. Inspect icon variantsReview `.ico` and PNG sizes used for tabs, bookmarks, and devices.
  3. Check render qualityVerify clarity at small sizes where blurry icons usually fail.
  4. Fix and redeploy icon setRegenerate missing sizes and update head tags as needed.

Why Google shows a globe instead of your favicon

Google shows a favicon in search results only when it can crawl both the page and the icon. The icon must be square, at least 48 x 48 pixels, declared with a link rel="icon" tag on the home page, and not blocked by robots.txt.

After fixing it, Google can take days or weeks to update the icon in results. Browsers also cache favicons, so check in a private window.

Key features

  • Detects incomplete favicon setups before users notice broken branding.
  • Improves tab, bookmark, and share-surface brand recognition.
  • Helps validate cross-device icon coverage quickly.
  • Useful for post-launch QA and rebrand verification.

Common uses

  • Auditing favicon setup after website redesign.
  • Debugging missing icons on iOS/Android homescreens.
  • Checking brand consistency across browser contexts.
  • Verifying client deliverables include full icon pack.

Tips for better results

  • Provide both `.ico` and multiple PNG sizes for compatibility.
  • Use simplified icon marks for tiny 16x16 rendering.
  • Clear browser cache after favicon updates during testing.
  • Include Apple touch icon and manifest references where needed.

Mistakes to avoid

  • Uploading one large logo and relying on browser downscaling only.
  • Forgetting root `favicon.ico` fallback path.
  • Using detailed text-based logos that blur at small sizes.
  • Changing icon files without updating cache-busting strategy.

Frequently asked questions

Different platforms (browser tabs, mobile home screen icons, search results) often expect different favicon sizes/formats - missing one of the expected variants can mean the icon fails to appear in that specific context even if your main favicon works fine.

A common baseline includes a standard .ico file plus various PNG sizes for different devices, and often an Apple touch icon for iOS home screen bookmarks - covering the range of places a favicon might be displayed.

Yes - enter any public URL to see what favicons that site declares and how they're configured.

Google needs a favicon it can crawl from your home page, in a square size that is a multiple of 48 px, and it can take days or weeks to update after a change.

Yes, if you want a sharp icon when someone saves your site to an iPhone or iPad home screen. A 180 x 180 PNG is the standard size.

Most modern browsers support SVG favicons, which stay sharp at every size and can even adapt to dark mode. Keep a PNG or ICO fallback for browsers that do not.