Why are there so many favicon sizes?

Different contexts use different sizes. iOS home screens want 180×180. Android home screens use the manifest icons (often 192×192 and 512×512). Desktop browser tabs use 16×16 and 32×32. Shipping all of them is the only way to look sharp everywhere.

Do I still need favicon.ico?

Yes, for legacy browsers and tools that look at /favicon.ico by default. Even modern browsers fall back to it when no explicit favicon is declared. Ship it alongside the PNG variants.

What is the web app manifest?

manifest.json (or manifest.webmanifest) declares the icons, name, and theme color for installable web apps. Android uses it for home-screen install prompts. iOS reads name and icons too, though some properties only work on Android.

Why does it sometimes show a CORS error?

Some hosts block cross-origin image fetches. Toova still detects whether the icon exists by checking the response, but cannot render the image in the preview. The actual website always works fine — this is just a tooling limitation.

Is the URL I check logged anywhere?

No. Toova does not see the URL you check — the request goes from your browser directly to the target site.

Favicon Checker — Inspect Favicons of Any Website

Check which favicons a website serves — including the legacy ICO file, modern PNG variants, Apple touch icons, and the web app manifest. Toova fetches and previews them in your browser, so you can audit your own site or compare with competitors.

Why favicons are a mess

Browsers, mobile platforms, social cards, RSS readers, and browser extensions all look for favicons in different places — /favicon.ico, /apple-touch-icon.png, the manifest, the meta tags. A site that ships only /favicon.ico misses every modern context. Toova checks every common location, shows the result, and surfaces which ones are missing so you can audit your own site without manually crafting requests.

What gets checked

The classic /favicon.ico at the root. Sizes of apple-touch-icon (180×180, 152×152, 120×120). PNG favicons declared in the HTML. The site's web app manifest (manifest.json) and the icons it references. Open Graph image used by social cards. Toova fetches each one, shows the size and dimensions, and flags anything missing — useful for design systems and brand audits.

Local-only

The fetches run from your browser, subject to the target site's CORS policy. The URL you check is never sent to a Toova server — there is no logging of which sites you audit. That matters when you are running competitive analysis or checking an unreleased domain. The Network tab will show requests to the target site, not to anywhere else.

Frequently Asked Questions

Why are there so many favicon sizes?: Different contexts use different sizes. iOS home screens want 180×180. Android home screens use the manifest icons (often 192×192 and 512×512). Desktop browser tabs use 16×16 and 32×32. Shipping all of them is the only way to look sharp everywhere.
Do I still need favicon.ico?: Yes, for legacy browsers and tools that look at /favicon.ico by default. Even modern browsers fall back to it when no explicit favicon is declared. Ship it alongside the PNG variants.
What is the web app manifest?: manifest.json (or manifest.webmanifest) declares the icons, name, and theme color for installable web apps. Android uses it for home-screen install prompts. iOS reads name and icons too, though some properties only work on Android.
Why does it sometimes show a CORS error?: Some hosts block cross-origin image fetches. Toova still detects whether the icon exists by checking the response, but cannot render the image in the preview. The actual website always works fine — this is just a tooling limitation.
Is the URL I check logged anywhere?: No. Toova does not see the URL you check — the request goes from your browser directly to the target site.