The Brand API Register
One-off lookups

Logo.dev API

Logo.dev serves a company's logo from an image URL with its domain, and a brand profile with colours from its API. Free with a link to Logo.dev; paid from $33.

Last updated 2026-11-10

Logo.dev is built for logos. Put an image URL with a domain in it on your page and the company's logo appears. A separate Brand API returns a profile: the name, description, colours, social links, the square logo, a wide logo and social banners. Logo.dev says the team that built the Clearbit Logo API builds it.

It suits products that show a logo next to each company name, such as CRMs, dashboards and search results, and want the cheapest way to do it.

  • Logos Yes
  • Colours Yes
  • Fonts No
  • Guidance No
  • Files Partly

What does Logo.dev return?

  • LogosThe CDN returns the company's square logo as JPG (default), PNG or WebP, with light and dark themes and greyscale; it does not serve SVG. The Brand API returns the square logo and the wide logo (brandmark) as temporary download URLs; it reports the source file's format, such as PNG, SVG or WebP, and downloads come as JPG, PNG or WebP up to 800 px.
  • ColoursThe Brand API returns brand colours, most dominant first, each with RGB, hex and OKLCH values.
  • FontsThe Brand API profile does not include fonts.
  • GuidanceNo voice or guideline data; the profile has the name, description, colours, social links, logo, brandmark and social banners.
  • FilesThe Brand API returns the brand's social banner images.

How is it billed?

  • CDN requests count against a monthly allowance; Brand API and MCP calls spend credits instead.
  • A brand lookup costs 5 credits, a brandmark 3, a logo 2, and search 1 per 1,000 searches.
  • One API credit is 1 cent, so a brand lookup costs $0.05.
  • Each brand domain is billed once per route per 24 hours; 404 and 202 (still indexing) responses are free.
  • Startup, Pro and Enterprise can buy more credits at $10 per 1,000, from $5; bought credits never expire, and there is no overage billing.

What are the limits?

  • Community: the monthly CDN allowance is a hard cap, with per-minute limits per account and per IP. Paid plans have no per-minute CDN limit and a soft monthly allowance.
  • API: 100 requests a minute and 5 concurrent on Community and Startup; 500 a minute and 15 concurrent on Pro.
  • Search: 500 requests a minute on Community and Startup, 5,000 on Pro.

What do the terms require?

  • Commercial projects on the free Community plan must show a visible link to Logo.dev on a public production page; paid plans and personal projects don't.
  • Load CDN images in your users' browsers and apps; don't fetch them from a script or proxy them through your server.
  • On every plan you can store what the Logo.dev API returns, logo files included, and serve it from your own servers.
  • Not allowed: a competing logo API, a logo search or download tool as your main product, bulk scraping for redistribution, or resale without transformation.

Who keeps it current?

  • When a company changes its logo, Logo.dev updates the image behind the same CDN URL.
  • Anyone can report a wrong, missing or outdated logo at logo.dev/update.
  • Paid plans get webhooks when a followed brand changes its logo, name, colours or socials: up to 5,000 brands on Startup and 50,000 on Pro.

How do you call it?

<img src="https://img.logo.dev/stripe.com?token=LOGO_DEV_PUBLISHABLE_KEY" alt="Stripe logo" />
curl --header "Authorization: Bearer LOGO_DEV_SECRET_KEY" "https://api.logo.dev/v2/brands?domain=apple.com"

When should you use something else?

  • For SVG logos or font names, use Brandfetch. Logo.dev's image URL doesn't serve SVG and its profile has no fonts. See Brandfetch vs Logo.dev.
  • For type and spacing, see Logo.dev vs Context.dev.
  • For logos fetched by a script, don't use the image URL: Logo.dev asks that images load in your users' browsers and apps. Call the Brand API from your server instead; you may store what it returns.

Sources