DuckDuckGo Favicon API vs Alternatives: Full Comparison

Your script needs to grab 50 site icons for a dashboard, and you don't want to host them. A public favicon API solves this in two lines of code, but which one? The DuckDuckGo favicon API has been quietly doing this job for years, sitting alongside Google's S2 service and direct /favicon.ico fetches.

Each option returns a different file format, behaves differently under load, and fails differently when a site has no icon. Picking the wrong one means broken thumbnails or mysterious 404s in your logs.

Quick Comparison: DuckDuckGo Favicon API vs Alternatives

How the DuckDuckGo Favicon API Actually Works

The endpoint is dead simple: https://icons.duckduckgo.com/ip3/example.com.ico. DuckDuckGo fetches the site's real favicon on its own infrastructure, converts it to an ICO container if needed, and serves it from their CDN. You never hit the origin server, which dodges most CORS walls.

This proxy approach means the URL also acts as a privacy-preserving fetch. Your visitors' browsers don't directly contact the target site just to render an icon. That's the same trick Google's s2.googleusercontent.com plays, and it's why both endpoints work in <img> tags from any origin without extra headers.

Format limitations

The biggest gotcha: DuckDuckGo only returns ICO. If you need a crisp 64x64 PNG for an iOS-style list, you'll need to convert it. Our PNG to ICO conversion guide covers the reverse direction, but the same tools handle both. For projects where ICO works fine — desktop browser tabs, legacy <link rel='icon'> fallbacks — DuckDuckGo is genuinely the most hands-off choice.

When DuckDuckGo Favicon API Wins

• You need ICO without the conversion step. Browser tab fallbacks, legacy IE support, and Windows shortcuts still want ICO. DuckDuckGo hands you one directly.
• You're fetching from the browser and want zero CORS config. Both DuckDuckGo and Google proxy the request, but DuckDuckGo has historically been more lenient about hot-linking.
• You want a privacy-respecting proxy. DuckDuckGo's brand is built on no tracking, which makes their favicon endpoint feel less surveillance-y than Google's.

When Google S2 Is the Better Pick

• You want a PNG, not an ICO. Google's endpoint serves image/png by default and supports a sz= parameter up to 64 pixels.
• You're building a SERP-style list. Google returns a default globe icon when a site has no favicon. DuckDuckGo returns a 404, which you'll need to handle.
• You want consistent 16x16 thumbnails. Google's response is always small, fast, and predictable.

When Direct /favicon.ico Still Makes Sense

For a single, trusted site — your own CDN, a partner's site, a known good source — fetching the favicon directly gives you the original asset at full resolution. You get SVG, multi-resolution ICO, animated PNG, whatever the site actually serves. The trade-off is CORS: most sites won't send the headers your browser needs, so this only works server-to-server, not client-side.

If you're doing bulk fetching, the lack of rate limit documentation is a real risk. Some origins will 429 you after 50 requests, others won't. The public APIs absorb that risk for you, which is the entire reason they exist.

Recommendation

For most client-side projects where you need a working icon in a browser tab or list view, the DuckDuckGo favicon API is the right default when you want ICO. Pair it with our free favicon generator if you also need to ship your own icons. For PNG thumbnails and Google-SERP-parity results, Google's S2 endpoint is faster and more predictable. Reserve direct /favicon.ico fetches for trusted, single-domain use where you need the full-resolution source file.

No matter which API you pick, cache the result. Browser favicon fetches are notoriously sticky, and your server will thank you for not hammering DuckDuckGo's CDN on every page load.

Check the documented requirements

The HTML Standard defines rel='icon' as the link relationship for an icon representing the current page.