Free Favicon Checker - Audit Browser, Apple, and PWA Icon Coverage

Check a live website's favicon setup for browser tabs, Apple touch icons, manifest icons, maskable assets, and modern install coverage. See what's missing before users do.

Run a real favicon audit

We'll inspect favicon declarations, manifest icons, Apple touch coverage, and the most common missing sizes so you can spot gaps before shipping.

More Site Audit & Metadata Tools

What this favicon checker audits

This tool checks the favicon setup a real website exposes to browsers and app installers. It looks for tab icons, Apple touch icons, manifest icons, raster fallbacks for SVG, and common size coverage like 16x16, 32x32, 192x192, and 512x512.

Instead of just checking whether /favicon.ico exists, it audits the icon declarations the page actually publishes and gives you a clearer picture of browser, iOS, and PWA readiness.

What a strong favicon setup usually includes

AssetTypical SizeWhy it matters
Browser tab favicon16x16 or 32x32Keeps tabs crisp in common browser chrome.
Apple touch icon180x180Used when iPhone and iPad users add the site to their home screen.
Android/PWA icon192x192Supports install banners and Android homescreen tiles.
Install / splash icon512x512Used in modern install prompts and high-resolution app contexts.
Maskable icon192x192 or 512x512Prevents awkward cropping on Android launchers.

How to use the checker

Enter a live URL

Paste the homepage or any page that includes your favicon and manifest declarations.

Run the audit

The checker fetches the page, discovers icon links, inspects the manifest, and reads image metadata when possible.

Review coverage gaps

Look for missing 16x16, 32x32, 180x180, 192x192, 512x512, and maskable assets.

Fix and recheck

After you add the missing files or declarations, rerun the audit to confirm the coverage is now complete.

Why sites still ship broken favicons

Only one favicon file

A single favicon.ico might be enough for older desktop browsers, but it leaves Apple touch, Android, and install flows underspecified.

SVG without fallback

SVG is great, but some consumers still expect raster icons. A PNG fallback keeps coverage safer.

Manifest exists, but icons are weak

Plenty of manifests ship with no 192x192, no 512x512, or no maskable icon.

Declared sizes do not match reality

If the linked file dimensions do not match the declared sizes, devices can render a blurry or unexpected result.

Frequently asked questions

Does this favicon checker inspect the manifest too?

Yes. If the page links a manifest, the checker reads it and audits the icon entries it exposes, including whether any icon is marked maskable.

Can I rely on SVG only?

Not always. SVG favicons are useful, but a raster fallback is still a safer setup for wider compatibility across simplified consumers and older environments.

Why do I need a 180x180 Apple touch icon?

That size is the common target for iOS home-screen icons. Without it, your site can look rough or inconsistent when saved from Safari.

What does a maskable icon do?

Maskable icons give Android launchers extra safe area so your logo is not cropped awkwardly inside adaptive icon shapes.