Skip to main content
Logo.dev is a logo image API that returns a company’s icon from a domain, ticker, ISIN, crypto symbol, or name, through an image URL on img.logo.dev. This page compares it with the Brandfetch Logo API on coverage, free usage, formats, and options, and shows how to move an existing Logo.dev integration to Brandfetch by changing the image URL.

Brand quality & time to value

Both APIs resolve in a single request, so time to first logo is about the same either way. The real difference shows up once you’re live and requesting logos for domains you haven’t hand-picked in a demo: Brandfetch publishes its actual coverage numbers. A logo resolves for 95% of brands in the core distribution, and 86% even at the extreme long tail of small, non-tech businesses. Logo.dev doesn’t publish comparable figures, so there’s no way to check how it performs outside the brands you happen to test.

Quick comparison

How requests compare

Both APIs work the same way: a CDN URL built from a domain (or other identifier), with your key passed as a query parameter. Logo.dev
Brandfetch

Switch from Logo.dev

Moving from Logo.dev to Brandfetch is a change to the image URL, because both APIs are image URLs that you put in an <img> tag with a public key. Logo.dev passes its options as query parameters, while Brandfetch puts them in the path and keeps only the client ID in the query, so a typical Logo.dev URL for a dark page translates like this: Logo.dev
Brandfetch
Most Logo.dev options map directly to a Brandfetch one, and the table below lists the common ones. The difference to watch for is theme, which the two APIs use in opposite ways and which Brandfetch applies only to logo and symbol, so the icon URL above has none: Logo.dev returns the brand’s icon, which on Brandfetch is the default icon type. Brandfetch also gives you the full horizontal logo and the symbol, in light and dark versions, which you pick by replacing icon in the path. Every option is listed in Logo API parameters, and you can get a client ID for free in the developer dashboard.

Why teams choose Brandfetch

  • No attribution, on any plan. Logo.dev’s free “Community” tier requires a visible link back to Logo.dev for commercial use. Brandfetch never asks for one.
  • SVG and type variants straight from the CDN. Logo.dev’s CDN serves raster images only and returns the full brandmark through its paid API, while Brandfetch serves SVG and the icon, logo, and symbol variants from the same free image URL on every plan.
  • Reliable at scale. Brandfetch runs at 99.9% uptime and is trusted in production by Canva, Typeform, and Experian.

Beyond logos

The Logo API is one of several Brandfetch APIs that share the same brand dataset, so a product that starts with logos can add more brand data later without another provider:
  • The Brand API returns a brand’s logos in every format, its colors, fonts, images, and company data as JSON.
  • The Brand Context API returns a written summary of what a company does, who it sells to, and how it sounds, ready to put in an LLM prompt. Logo.dev has no equivalent.
  • The Brand Search API turns a company name into a domain for autocomplete, and is free for up to 500,000 requests a month.
  • The Transaction API identifies the merchant behind a card or bank transaction and is generally available, while Logo.dev’s transaction lookup is a beta service with its own separate key.
  • The MCP server gives AI assistants such as Claude and Cursor access to all of the above.

FAQ

Yes. Brandfetch’s Logo API takes the same identifiers through the same kind of image URL, and its free tier allows 1,000,000 requests a month with no attribution, compared with 500,000 requests and a required link for commercial use on Logo.dev’s free tier.
You change the image URL, and nothing else in your app needs to move. Most apps build that URL in one helper or component, so you change the host, move the options into the path with the table above, and swap the key for your client ID.
The theme value is probably copied as it was. Logo.dev’s theme=dark describes a dark background, while Brandfetch’s theme/dark asks for the dark version of the logo, so a logo shown on a dark page needs theme/light on Brandfetch.
Not in the image URL. Call the Brand Search API with the name, keep the domain of the brand you or your user picks, and use that domain in the Logo API URL. Storing the domain also makes later lookups exact, since several companies can share a name.
Yes, on every plan, including the free one. Add .svg after the logo or symbol type in the URL, while icons are served as raster images.

Get started

Logo API overview

See the full feature set and implementation guide

Get your client ID

Free account, no credit card required