Asset types

Favicon API

Get favicon information for a company alongside other normalized logo assets (primary, icon, wordmark) so you can render the best option for each UI context.

Why favicons alone usually fail

Many sites publish favicons that are small, low-quality, or outdated. They’re fine for tiny UI surfaces, but they often don’t match the quality you want for product displays.

What you receive

In Fivicon’s normalized response, favicon data appears as a distinct asset type. You can use type to identify it and rely on score, width, and height to compare. 

{
  "logos": [
    {
      "type": "favicon",
      "url": "https://cdn.fivicon.com/example/favicon.png",
      "width": 32,
      "height": 32,
      "score": 88
    }
  ]
}

When to use which asset

  • Use favicon for very small UI (browser tabs, 16–24px icons).
  • Use icon or primary when you need crisp rendering.
  • Always choose based on score + dimensions.

FAQ

Is there a dedicated favicon endpoint?

Fivicon’s discovery flow returns multiple normalized asset types in one response, including favicon information under logos[].

Can I rely on favicon size?

Yes. The response includes explicit width/height, allowing you to avoid guessing.

Back to Home