Brandfetch vs Logo.dev

Both return a company's logo from its domain. Brandfetch returns more, including SVG, font names and images; Logo.dev costs less, from $33, and allows storage.

Last updated 2026-11-10

Both look up a company's logo from its domain, both serve logos through an image URL you put in a page, and both have an API for the full profile and an MCP server for agents. Brandfetch returns more; Logo.dev costs less.

BrandfetchLogo.dev
JobOne-off lookupsOne-off lookups
What it gives you
LogosYesYes
ColoursYesYes
FontsPartlyNo
GuidancePartlyNo
FilesPartlyPartly
Access and cost
You sendA domain, URL, email, ticker, ISIN or crypto symbolA domain, ticker, ISIN, crypto symbol or name
AuthenticationAPI key; a client ID for the Logo APIPublishable key for images; secret key for the API
Free tier100 brand fetches, once; 1M logo requests a month500,000 logo requests and $5 of API credits a month
Paid from$129 a month (Growth Starter)$33 a month (Startup)
MCP serverYesYes
Checked2026-11-102026-11-10

Choose Brandfetch if

  • You need SVG logos, font names or the brand's images, not only the logo.
  • You want a written summary of a brand's voice, from the Brand Context API.
  • You show a lot of logos without attribution: the Logo API is free up to 1,000,000 requests a month and needs no attribution.

Choose Logo.dev if

  • You need logos and colours and want the lower paid plan: $33 a month against $129.
  • You want to keep logos on your own servers. Logo.dev allows it on every plan; Brandfetch lets you cache Brand API data for 30 days, then refresh or delete it.
  • Your project is personal, or you can show a link to Logo.dev: then the free plan is enough.

What do they have in common?

  • Their image URLs are meant to load in your users' browsers. Neither allows fetching those URLs from a script.
  • Both send webhooks on paid plans when a brand you follow changes.
  • Anyone can report a wrong or outdated logo to either.

Sources