Enter a URL above to start the validation process.
Detection Results
Primary Favicon
Standard Check
- /favicon.ico path
- HTTPS Security
- Format Support ICO/PNG
Platform Preview
Browser Tab Preview
How users see your site
A favicon is the small icon browsers show in tabs, bookmarks and next to your site in mobile search results. Our free Favicon Checker tests whether your website serves a valid favicon, confirms your site uses HTTPS, and previews how the icon looks to real visitors.
The standard favicon is a 16×16 or 32×32 pixel ICO or PNG file served at /favicon.ico, with a 180×180 apple-touch-icon for iOS home screens. If your icon is missing, browsers show a generic placeholder and your site looks unfinished.
Once your favicon is fixed, check the rest of your site’s technical SEO: run a mobile friendly test, review the page speed checklist, and tidy your tags with the meta tag generator.
Quick answer
A valid favicon is a small icon file — usually /favicon.ico at your site's root, backed by PNG and apple-touch-icon variants — that browsers display in tabs, bookmarks, and mobile search results. This free checker loads your domain's /favicon.ico in real time: a green check means the file exists and loads, a red X means it's missing or unreachable. It also confirms your URL uses HTTPS and renders your icon through Google's favicon service into a mock browser tab and a search-result preview. If the icon fails to load, the usual culprits are a missing file, a wrong path, or aggressive browser caching.
Example: https://google.com or simpliconvert.com
Enter a URL above to start the validation process.
Primary Favicon
Browser Tab Preview
How users see your site
Paste any URL into the box above and hit Check Icon. Here's what happens behind the button.
First, the tool attempts a real, live load of https://yourdomain.com/favicon.ico. This is the file browsers request by default, and the check treats it the way a browser would: if the image loads, you get a green check; if the request fails — the file is missing, the path is wrong, or the server blocks it — you get a red X. No guessing, no assumptions carried over from some earlier crawl.
Second, it looks at the URL you typed and flags whether it uses HTTPS. Icons served over plain HTTP on an HTTPS page can trigger mixed-content warnings, so the protocol check is a quick hygiene pass worth having.
Third, it pulls your site's icon through Google's favicon service and renders it in two mockups: a browser tab and a mobile-style search result. That preview answers the question that matters most — not "does the file exist?" but "what do my visitors actually see?"
One honest limitation: the tool does not crawl your HTML looking for declared icons. It won't tell you whether your apple-touch-icon link tag is correct or whether an SVG favicon validates. The /favicon.ico check plus the visual previews cover the cases that affect nearly every visitor — but the touch-icon and manifest checks described below are on you.
Your favicon is the smallest piece of your brand and one of the most-seen. Every open tab, every bookmark, every history entry, and every mobile search result carries it. When someone has a dozen tabs open, they aren't reading titles — they're scanning tiny squares of color and shape. That's your icon doing recognition work at sixteen pixels.
When the icon is missing, browsers substitute a generic placeholder: a blank page or a gray globe. Next to a row of crisp brand marks, that placeholder reads as unfinished. It doesn't matter how good your product is — the first signal a new visitor gets is that this site couldn't be bothered with the details.
Google raised the stakes when it started showing site icons next to URLs in mobile search results. Your listing now competes visually before anyone reads a word, and a sharp, recognizable favicon can be the difference between a scroll-past and a tap. That's why icon health belongs in the same routine as title tags and meta descriptions. Run this check after any redesign, migration, or CMS switch — those are the moments icons quietly break.
The favicon world has accumulated two decades of formats. Here is the short list that covers essentially everyone.
The .ico file is the old guard. It's a container that can hold multiple sizes — typically 16×16, 32×32, and 48×48 — in one file, and browsers have requested /favicon.ico from the site root since the beginning. Keep one there for legacy support and for any client that still asks by default.
The 32×32 PNG is the modern workhorse. PNGs are smaller than ICOs, support full transparency, and every current browser accepts them when declared with a link tag. If you ship only one declared icon, make it this one.
The 180×180 apple-touch-icon PNG serves iOS. When someone adds your site to their iPhone home screen, this is the image iOS uses — and iOS applies its own rounded corners and ignores transparency, so design it on a solid background.
SVG favicons are the optional upgrade. A single tiny vector file scales from a 16-pixel tab to a high-resolution bookmark bar with zero quality loss, and most modern browsers now support them. They're not universal yet, so treat SVG as a supplement rather than a replacement.
Put together — a multi-resolution .ico at the root, a 32-pixel PNG link tag, and a 180-pixel apple-touch-icon — and your icon renders correctly on virtually every browser and device shipping today.
The minimum viable favicon takes about two minutes. First, create your icon and save it as favicon.ico, then upload it to your site's root directory — https://yoursite.com/favicon.ico. Browsers request this path automatically, so with most setups you don't even need HTML changes for the classic tab icon to appear.
Second, cover modern browsers and iOS with explicit link tags in your page's <head>:
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
Third, verify. Run this checker to confirm /favicon.ico loads, then open your site in a fresh tab and look at the tab bar. If the old icon (or no icon) persists, you're almost certainly looking at a cached copy — hard-refresh with Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac, or append a version query like favicon.ico?v=2 to force browsers to fetch the new file. If you also need the surrounding tags — theme-color, Open Graph images, the works — SimpliConvert's Meta Tag Generator builds the full head block for you in one pass.
You uploaded the file, refreshed the page, and the tab still shows a blank page. Work through this list in order — the culprit is usually near the top.
?v=2 to the icon URL to bust the cache./favicon.ico from the root by default. If your file lives in /images/ or /assets/ without a matching link tag, the browser never finds it. Either move the file to the root or declare the real path with rel="icon".If every row comes back green, you're in good shape — but don't stop at the tab. Icons also surface in bookmarks, browser history, and mobile search results, so glance at the search-result preview above and confirm your mark reads clearly at tiny sizes. Then run your URL through the SERP Preview Tool to see the full listing — title, description, and icon together — exactly as searchers will see it.
If the /favicon.ico check fails, fix the file first — path, format, or a fresh upload — bust your cache, and re-run the check. One clean pass here plus a Title Length Checker run, so your brand name isn't truncated in the tab next to your new icon, covers the two most visible tab-bar issues in about a minute.
Make the favicon check part of your launch checklist: after redesigns, domain moves, HTTPS migrations, and CMS changes. Those are precisely the moments when an icon that worked for years silently disappears — and nobody notices until a customer mentions the blank tab.
Type in any website URL and hit Check Icon. The tool performs a live load of https://yourdomain.com/favicon.ico — a green check means the file exists and loads, a red X means it is missing or unreachable. It also flags whether your URL uses HTTPS and renders your icon through Google's favicon service into a mock browser tab and a mobile-style search result preview, so you can see exactly what visitors see.
A favicon is the small icon browsers display in tabs, bookmarks, history, and next to your listing in mobile search results. When someone has twenty tabs open, that tiny square is often the only visual clue identifying your site. A missing favicon shows a generic placeholder instead, which makes a site look unfinished and harder to recognize — a small detail that quietly shapes first impressions.
Cover the bases with three files: a multi-resolution .ico (containing 16, 32, and 48-pixel versions) at your site root for legacy support, a 32x32 PNG declared with a link tag for modern browsers, and a 180x180 PNG apple-touch-icon for iOS home screens. SVG favicons are a nice optional extra — they scale perfectly and stay tiny — but the .ico plus PNG plus touch icon combination renders correctly nearly everywhere.
Nine times out of ten, it is caching. Browsers cache favicons aggressively and can keep showing the old (or missing) icon for days. Try a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) or add a version query like favicon.ico?v=2 to force a fresh fetch. If that fails, check the file path, confirm the file is a valid ICO or PNG, and make sure your apple-touch-icon and icon link tags point to the right locations.
Not directly — Google has never listed the favicon as a ranking factor. Indirectly, though, it matters: Google displays site icons next to mobile search results, so a crisp, recognizable icon can lift your click-through rate. Favicons also reinforce brand recognition across tabs and bookmarks, and a polished, consistent brand presentation supports the trust signals that keep visitors coming back.
The simplest route: name your icon file favicon.ico and place it at your site's root — browsers request /favicon.ico automatically. For fuller coverage, add link tags in your HTML head pointing to your PNG and apple-touch-icon files. After uploading, clear your cache or do a hard refresh before judging the result, because browsers love to serve the stale version.
No — and it is worth knowing that upfront. This checker tests whether /favicon.ico loads over HTTPS and previews your icon via Google's favicon service. It does not crawl your HTML for apple-touch-icon, manifest, or SVG declarations. To verify those, view your page source and confirm each link tag's href actually resolves to a real file.