Skip to content

Favicon Finder

Fetch any website's favicon from Google, DuckDuckGo, and the site itself. Preview it at any size, then copy the URL or download the file.

Share

How to use Favicon Finder

1

Enter a website URL

Type or paste any domain, with or without https:// — just the hostname is enough.

2

Pick an icon size

Choose from 16 to 256 px. Google's endpoint can render any size you ask for; the other sources return whatever the site actually serves.

3

Copy or download

Preview the icon from each source, then copy the direct URL or save the image file.

Why you need more than one source

A favicon isn't one canonical file the way a page title is. Sites declare it through a handful of competing conventions — a literal /favicon.ico at the domain root, a <link rel="icon"> tag pointing at a PNG or SVG, or a whole apple-touch-icon set for mobile home screens — and plenty of sites get at least one of those wrong or skip it entirely.

Google's and DuckDuckGo's favicon services exist because of that mess: both crawl sites and cache whatever icon they find, resolved through whichever method the site actually used, then serve it back from a predictable URL. That's more reliable than guessing the path yourself, which is why this tool checks both alongside the direct favicon.ico fetch rather than picking just one.

The tradeoff is freshness. A cached favicon from a crawler can lag behind a site's real one for weeks after a rebrand, so if you need the current icon with certainty, the direct favicon.ico card (when it resolves) is the ground truth.

What people actually use these icons for

The common case is populating a bookmarks manager, a browser extension's site list, or an internal admin dashboard that links out to a bunch of external tools — anywhere you want a recognizable icon next to a domain name without asking every user to upload one.

It's also useful for competitive or research work: pulling a company's favicon for a slide deck, a comparison table, or a link preview mockup without digging through their site's source for the exact asset path.

Because the URLs returned here are stable, hot-linking them directly (rather than downloading and re-hosting) is the normal way to use Google's and DuckDuckGo's services — that's what they're built for, and it means the icon stays in sync if the site ever changes its own.

Frequently Asked Questions

Where do these favicons actually come from?

Google's favicon endpoint (www.google.com/s2/favicons) crawls and caches a site's icon at the size you request. DuckDuckGo's icon service (icons.duckduckgo.com) does the same from its own crawl. The third card fetches the site's favicon.ico directly, which only works if the site actually serves one at that exact path.

Why is one of the three icons missing or broken?

Google and DuckDuckGo only have an icon cached if they've crawled the site before, so a brand-new or very low-traffic domain can come back empty on one or both. The direct favicon.ico card fails whenever a site declares its icon through a <link rel="icon"> tag pointing at a different filename (a common pattern for SVG or multi-size icon sets) instead of serving a literal /favicon.ico.

Can I get a bigger icon than the site actually has?

Google's endpoint will still return an image at the requested size, but if the source favicon is small it gets upscaled and looks soft. For a crisp result, use a size close to or smaller than the site's original icon.

Is this stored or logged anywhere?

No. The domain you type never touches this site's server — your browser requests the icon URLs directly from Google, DuckDuckGo, and the target site.