Test any site’s favicon against the modern 2026 spec. Enter a URL or drop your files and get a clear pass/warn/fail scorecard — plus a plain-English fix for anything that’s off. We check what matters and don’t nag you for legacy files you no longer need.
Every check is graded against the verified 2026 favicon spec — the same set our generator produces.
Reachable at the site root, multi-size, at least 32×32 — the desktop & Google fallback.
A scalable SVG with a valid viewBox — what modern browsers and Google prefer.
180×180 and opaque, so iOS doesn’t render a transparent icon as a black square.
Valid JSON with 192, 512 and a separate 512 maskable icon for PWAs and Android.
The clean four-tag set — and a flag if you’re still using obsolete rel="shortcut icon".
Your detected favicon rendered in a browser tab, Google result and Android maskable masks.
Most favicon checkers still grade against a decade-old checklist and tell you that you’re
“missing” a 48×48, a 96×96, a 144×144 and a dozen other PNGs. You’re not. Modern browsers
read your favicon.svg and downscale it; Google reads the SVG and the
.ico. The full 2026 set is small on purpose.
So this checker rewards a clean, minimal favicon: favicon.ico,
favicon.svg, an opaque apple-touch-icon,
a site.webmanifest with three icon entries, and the four-tag
<head> markup. If you have that, you pass — no legacy nagging.
We only warn about things that genuinely break or weaken your favicon.
Check a live site, or drop favicon.ico / .svg / apple-touch / manifest — or the generated .zip.
We read your <head>, fetch each icon and check sizes, transparency, viewBox and manifest entries.
Get a plain-English fix for each item, then regenerate the correct set in one click.
Enter your site’s URL above and the checker fetches your page, reads the favicon tags in your <head>, downloads each icon and inspects it — then shows a pass/warn/fail scorecard with a plain-English fix for anything wrong. You can also drop your favicon files in to validate them before you deploy.
Google keeps its own favicon cache, separate from your browser, and re-crawls on its own schedule — so a correct favicon can take days or weeks to appear in search. Google also needs a favicon.ico that’s at least 48×48 at a reachable URL. The checker confirms your .ico meets that bar.
Yes. In 2026 the clean set is favicon.ico, favicon.svg, an apple-touch-icon, three manifest icons and the manifest itself. The old 16-file dump (48/96/144 PNGs and the rest) is no longer needed — browsers read the SVG and downscale it. This checker won’t nag you to add legacy files; it rewards a clean, minimal set.
That means your apple-touch-icon.png has a transparent background. iOS composites the icon onto a solid tile, so transparency shows as black. Re-export the 180×180 Apple touch icon as opaque with a solid background colour. The checker flags this automatically.
It’s free. The file-upload mode runs entirely in your browser — your files are never uploaded. The URL mode fetches only the public page and icons at the address you enter, to read their bytes; nothing is stored.