Migration guide
Clearbit-style logos vs our favicon API
Products like Clearbit expose company brand logos and rich firmographic data. FaviconAPIs does one thing: return a high-quality website favicon (256×256 PNG) derived from what a site actually publishes — SVG, manifest, touch icons, PNG, or ICO. If you only need an icon next to a domain in your UI, we may be a simpler, purpose-built fit.
What FaviconAPIs is (and isn't)
| Topic | FaviconAPIs |
|---|---|
| Primary output | Normalized favicon image for a URL / domain |
| Brand logo database | No — we don't maintain a proprietary catalog of official logos; we resolve icons from the web presence of the URL you pass. |
| Enrichment / firmographics | Out of scope — use your data vendor for company records; use us for the icon strip in lists, CRM rows, or email clients. |
When migrating from a logo API makes sense
- You only display a small icon next to a domain or email sender.
- You want pricing and limits aligned to favicon fetches, not full enrichment bundles.
- You are OK with site-published icons (often indistinguishable from “the logo” for many brands).
When you need an official marketing logo with strict brand guidelines, a dedicated logo or brand API may still be the right tool — you can use FaviconAPIs for default avatars and fall back to your logo provider where needed.
Integration shape
Same as any other FaviconAPIs client: authenticate with your API key, call GET /api/v1/favicon?url=..., use the JSON url field. See the API documentation and usage & billing.
FAQ
- Is this a drop-in Clearbit replacement?
- No — endpoints, data models, and pricing differ. This page explains when our favicon API covers your icon use case so you can plan a deliberate migration.
- How is usage billed?
- Per successful API call to FaviconAPIs under your plan's monthly quota — see Usage, billing & security.