> ## Documentation Index
> Fetch the complete documentation index at: https://www.logo.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Brandfetch Alternative: Logo.dev's Image URL API

> Compare Logo.dev and Brandfetch: a drop-in image URL API vs a JSON brand profile, which lookup keys each supports, and a parameter-level migration map.

Logo.dev and Brandfetch both turn a domain into brand assets. The difference is shape: Logo.dev leads with a URL-based image API you drop into an `<img>` tag, then offers JSON brand endpoints when you need structured data. Brandfetch leads with a JSON Brand API that returns a deep brand profile in one call.

## At a glance

|                            | Logo.dev                                                                                                                   | Brandfetch                                                     |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| Logo image                 | `img.logo.dev/:domain` URL, [publishable key](/platform/api-keys) via `?token=`                                            | `cdn.brandfetch.io` URL, client ID via `?c=`                   |
| Brand data                 | [Describe](/describe/introduction) (core) and [Brand](/brand/introduction) (full profile) JSON, secret key                 | Brand API JSON, bearer token                                   |
| Image URL lookup keys      | Domain, [ticker](/logo-images/ticker), [ISIN](/logo-images/isin), [crypto](/logo-images/crypto), [name](/logo-images/name) | Domain, ticker, ISIN, crypto (name via their Brand Search API) |
| Image without parsing JSON | Yes, the image URL is the product                                                                                          | Through the Logo CDN                                           |

## When each fits

**Logo.dev fits when** you mainly need the logo image and want it as a URL rather than a JSON pipeline. The image API takes a publishable key that's safe in client code, so you render logos straight from the browser without parsing a response. We built the original Clearbit Logo API. The [Brand API](/brand/introduction) returns the same `img.logo.dev` URLs, so the logo you render and the data you fetch never drift apart.

**Brandfetch fits when** you need design and firmographic metadata that Logo.dev doesn't return: fonts, company size, founded year, industry and location, explicit icon-versus-symbol logo variants, or an AI-oriented long description. Its enterprise tier also offers GraphQL, webhooks, and bulk ingestion.

<Card title="Migrate from Brandfetch" href="/migrations/brandfetch" arrow="true" cta="View migration guide">
  Swap `?c=` for `?token=` and map each Brand API field.
</Card>