Favicon URL builder
Construct the standard favicon URL patterns for a domain — the site's own /favicon.ico, Google's S2 service, DuckDuckGo's icons API, Icon Horse — with side-by-side preview.
URLs
Preview
Ready.
How to use
- Paste a domain or full URL.
- The tool emits four URL patterns:
https://example.com/favicon.icohttps://www.google.com/s2/favicons?domain=example.com&sz=64https://icons.duckduckgo.com/ip3/example.com.icohttps://icon.horse/icon/example.com
- A preview row uses
<img>tags to actually render each one — the browser handles the request, so it works without us hitting any API. - Copy any URL or Copy all as HTML for a fallback chain.
Which service for what
- Own
/favicon.ico— the only source you fully control. Use this for your own product. - Google S2 — high coverage, configurable size, fast. Good default for displaying third-party domains in a UI.
- DuckDuckGo — privacy-friendly, no tracking. Sometimes misses obscure domains.
- Icon Horse — higher quality (does best-effort search if
/favicon.icoisn't found), but rate-limited on the free tier.
FAQ
Does this tool fetch the favicons?
The browser does, when it renders the preview row's <img> tags. That means each service sees your IP and the domain you're looking up. The URL builder itself runs locally.
Why use a third-party service vs. the site's own favicon?
Reliability and uniformity. Some sites don't host /favicon.ico directly; they use Link headers, manifest.json icons, or just nothing. Google S2 / DDG / Icon Horse abstract over all of that.
Can I get different sizes?
Google S2 supports sz=16, 32, 64, 128, 256. The others return a single fixed size.
Is this safe to use in production?
For external services, you're trusting them to stay up. Self-host the icon (download it once, cache it) if reliability matters.