Favicon Checker
Check whether a website has a favicon set up. Enter a domain to see if its favicon.ico exists and preview it.
Recommended Settings
Pro Tips
- •This checks the two most common favicon locations (favicon.ico and favicon.png at the site root) plus Google's public favicon service as a fallback
- •Many modern sites declare their favicon via a <link rel="icon"> tag pointing to a custom path rather than the default /favicon.ico location, which this direct check won't find
- •Google's favicon service often finds an icon even when the direct /favicon.ico check fails, since Google independently crawls and caches site icons
- •A missing favicon doesn't break a website, but browsers will show a generic blank icon in the tab and bookmarks instead
Most Popular
Most users check both the direct favicon.ico path and the Google fallback for the most complete picture
When to Use This Tool
Verify that a website has a properly configured favicon as part of a launch checklist.
Confirm a favicon is set up correctly and displays as expected across browsers.
Investigate why a site's icon isn't showing up in browser tabs or bookmarks.
Quickly check what favicon a competitor or reference site uses.
How It Works
Attempt to load an image from the site's default favicon.ico and favicon.png paths using a standard <img> element
Since image loading doesn't require the same cross-origin permissions as fetching page content, this works reliably even for sites that don't explicitly support cross-origin requests
Also check Google's public favicon service as a fallback, since it can locate icons declared through custom <link> tags that a direct path check would miss
100% Private
Files never leave your device. All processing happens locally in your browser.
Lightning Fast
Powered by Browser native image loading (cross-origin safe) for optimal performance on modern browsers.
Open Source
Built with verified, open-source libraries. Fully transparent.
Frequently Asked Questions
Why check three different paths?
Not every site uses the default /favicon.ico location - some use a PNG file instead, or declare a completely custom path via a <link rel="icon"> tag in their HTML. Google's favicon service often finds icons that a direct path check would miss.
Why does this work without hitting CORS restrictions?
Loading an image via an <img> tag doesn't require the same cross-origin permissions that fetching raw page content does. Browsers allow images to load and report success or failure across origins, even though reading their actual pixel data would require CORS.
Is my data sent to a server?
Checking the site's own favicon paths happens directly between your browser and that website - no data passes through this tool's own servers. The Google favicon service check does send the domain name to Google's public service.
Why does the check fail even though the site clearly has a favicon in my browser tab?
The site may declare its icon through a custom <link rel="icon"> path that doesn't match the common default locations this tool checks directly - in that case, the Google favicon service check will often still succeed.
Does a missing favicon hurt SEO?
A missing favicon doesn't directly affect search rankings, but it can result in a generic icon appearing in search results and browser tabs, which may look less polished or trustworthy to visitors.