HomeCatalogFavicon Extractor › Why Forge Favicon

Favicon API vs Google's Favicon Service & favicongrabber.com

Google's s2/favicons service is the default favicon fetcher most developers reach for — ubiquitous, zero-infrastructure, and routed through Google. favicongrabber.com returns a JSON list of icon URLs you then have to fetch yourself. The Forge Favicon API extracts any site's favicon directly as a clean PNG at any size you ask for, with three fallback strategies and no third-party tracking. It is the fetcher you use when you want the image back in one request, sized, and not dependent on Google.

Try the Favicon Extractor →

Looking to generate a full favicon package from your logo (all sizes, manifest, HTML tags)? That is a different job — use a generator like realfavicongenerator.net. Forge fetches the favicon a site already has.

The Quick Comparison

FeatureForge FaviconGoogle s2/favicons · favicongrabber.com
Fetch a site's existing favicon
Returns the image directly (one request)✓ (PNG)Google: ✓ · favicongrabber: × (returns a JSON URL list)
Custom size, 16–512 px✓ (?size=256)Google: limited sizes · favicongrabber: whatever the site ships
Always normalized to PNG× (may be .ico / varying formats)
Multiple fallback strategies✓ (HTML parse → common paths → Google fallback)partial
No third-party request routing / tracking✓ (self-hosted)× (Google routes the request)
Cached for fast repeat lookups✓ (1-hour cache)varies
API key / signup××
Cost$0, no signupFree

Where Forge Favicon Wins

1. The image back, at the size you want, in one request

Ask for a size and get a clean PNG — no second fetch, no .ico decoding, no guessing what the site shipped:

curl "https://forge-node.tail2b516d.ts.net/favicon?url=github.com&size=256" -o github.png

favicongrabber returns a JSON list of candidate URLs you then have to fetch and resize yourself. Forge does that work and hands back the final image.

2. Three fallback strategies for reliability

Many sites do not declare a favicon cleanly. Forge tries the HTML <link rel="icon"> tags first, then common well-known paths (/favicon.ico, /apple-touch-icon.png), then a Google fallback as a last resort. You get an icon even when the site is sloppy about declaring one.

3. Self-hosted, not routed through Google

The s2/favicons service sends every lookup through Google's infrastructure. If you would rather your favicon lookups not flow through a third-party ad company — for a privacy-respecting dashboard, an internal tool, or compliance reasons — Forge runs the fetch itself.

4. Sized PNG for grids and link previews

Building a bookmarks grid, a "sites we integrate with" wall, or a link-preview card? Request the exact pixel size your layout needs and drop the URL straight into an <img> tag. The 1-hour cache keeps repeat lookups fast.

When Google's Service or a Generator Is Still Fine

Use Cases for Forge Favicon

FAQ

Is the Forge Favicon API really free?

Yes. No signup, no API key. Rate-limited per IP, with a 1-hour cache. See the Favicon API docs.

What sizes and formats do you support?

Any size from 16 to 512 px via ?size=, always returned as a normalized PNG.

What if a site has no favicon?

Forge tries three strategies — HTML parsing, common paths, then a Google fallback. If all three fail, you get a clear error rather than a broken image.

Can it generate a favicon from my logo?

No — Forge fetches a site's existing favicon. To build a favicon package from an image, use a generator like realfavicongenerator.net.

Where do I go next?

Try the Favicon Extractor, or browse the full free API catalog for 15 more developer APIs in the same no-signup style.