Company Logo API Comparison 2026: Context.dev vs Logo.dev vs Brandfetch

If you've ever tried to display company logos in your app, you already know: manual uploads don't scale, web scraping breaks constantly, and the old standby — Clearbit's free Logo API — shut down on December 1, 2025.

Three services have stepped up as replacements in 2026: Context.dev, Logo.dev, and Brandfetch. Each takes a different approach, and the right one depends on what you're building.

Disclosure: This comparison was written by the Context.dev team. We've done our best to evaluate each service fairly, but we obviously have a horse in this race. We encourage you to try all three — they each offer free tiers.

Below we walk through real pricing, actual API responses, and the specific scenarios where each provider wins.

The Post-Clearbit Landscape

Clearbit's Logo API was the default choice for years. Free, unauthenticated, dead simple: hit https://logo.clearbit.com/{domain} and get back a PNG. A lot of production apps relied on it.

When HubSpot acquired Clearbit and shut down the free API in late 2025, every team using it had to find an alternative. That migration is still ongoing, and it's shaped how all three providers position themselves.

The replacement you pick isn't just a logo endpoint anymore. The market has split into two categories:

1. Logo CDN services that serve images fast with minimal overhead
2. Brand data platforms that return logos alongside colors, fonts, metadata, and more

Which category you need is the first decision worth making.

The Three Contenders at a Glance

Context.dev: The Full Brand Identity Platform

Context.dev (formerly Brand.dev) takes the broadest approach of the three. It's a brand data platform that returns logos, colors, fonts, and metadata — everything you'd need to programmatically theme an interface around a company's identity.

How It Works

The primary endpoint is a brand retrieve call that accepts a domain and returns a full brand object:

import ContextDev from 'context.dev';
 
const client = new ContextDev({ apiKey: process.env.CONTEXT_DEV_API_KEY });
 
const { brand } = await client.brand.retrieve({
	domain: 'stripe.com',
});
 
// brand.logos → array of logo objects with url, type, mode, colors, resolution
// brand.colors → brand color palette with hex values and names
// brand.fonts → typography data with family, fallbacks, usage percentages
// brand.socials → official social media links
// brand.description, brand.slogan, brand.address, brand.stock...

You can also look up brands by email, company name, stock ticker, or ISIN code. That flexibility is useful for CRM enrichment where you might not always have a clean domain.

For high-volume logo-only needs, Context.dev offers Logo Link, a CDN endpoint that serves logo images directly without an API call:

<img src="https://logos.context.dev/?publicClientId=YOUR_ID&domain=stripe.com" />

Logo Link runs on a separate quota from API credits, has no per-second rate limits, and delivers images with roughly 20ms average latency from a global CDN. Similar to what Clearbit's old free endpoint did, but authenticated.

What You Get Back

The logo objects include more metadata than you might expect:

{
	"url": "https://media.context.dev/...",
	"mode": "light",
	"type": "logo",
	"group": "primary",
	"colors": [{ "hex": "#635BFF", "name": "Stripe Purple" }],
	"resolution": {
		"width": 512,
		"height": 214,
		"aspect_ratio": 2.39
	}
}

You get multiple variants: horizontal logos, icon-only marks, and versions for light and dark backgrounds. Each includes extracted colors and resolution data, which is useful if you're building programmatic theming or similar features.

Beyond logos, the full brand response includes colors (primary and secondary palettes with named values), fonts (families, fallbacks, and usage percentages across the site), social profiles, physical address, industry classification via NAICS codes, stock data, and links to key pages like careers, pricing, and privacy policy.

AI-Powered Extraction

Context.dev also exposes AI endpoints that go beyond static brand data:

• AI Products extracts structured product catalogs from any domain, returning names, descriptions, features, pricing, and images
• AI Query lets you define custom data points to extract from any website, essentially structured web scraping with natural language instructions
• Web Scrape to Markdown converts any URL to clean markdown, useful for feeding content into LLM pipelines
• Screenshots capture full-page or specific-page screenshots (pricing, careers, blog, etc.)
• Styleguide extracts a complete design system including color roles, typography scales, shadows, and component patterns

The other two providers don't offer these capabilities.

Pricing

Credits are consumed at different rates: brand retrieval costs 10 credits, web scraping costs 1 credit, and Logo Link uses a separate quota entirely. Overage pricing ranges from $6 to $19 per 10K credits depending on your plan.

Brand data is cached and refreshed quarterly. Cached responses (about 70% of requests) return fast; first-time lookups for uncached domains can take 10-30 seconds as the system indexes the brand in real time. Logo CDN URLs are guaranteed valid for one year.

Best For

If you need more than logo images — brand colors, fonts, metadata — Context.dev gives you that in a single API call. Typical use cases: SaaS onboarding that auto-populates brand colors, sales tools generating personalized decks, fintech platforms theming transaction feeds, or AI apps that need structured brand context.

Logo.dev: The Clearbit Replacement

Logo.dev was built by the original creators of the Clearbit Logo API. It's the most direct successor to what Clearbit offered: a fast, simple CDN that returns logo images from a URL.

How It Works

The integration is dead simple. You construct a URL, and you get back an image:

<img src="https://img.logo.dev/stripe.com?token=YOUR_TOKEN" />

That's it. No SDK needed, no JSON parsing, no client library. You can drop it into an <img> tag, a CSS background, or any context that accepts an image URL. The token parameter is a publishable key that's safe to use in client-side code.

For server-side use cases that need richer data, Logo.dev offers a Describe API on the Pro plan:

curl -H "Authorization: Bearer YOUR_SECRET_KEY" \
  https://api.logo.dev/describe/stripe.com

This returns JSON with logos, brand colors, social links, a company description, and a blurhash field for rendering placeholder images while the logo loads.

Logo.dev also supports lookups by stock ticker (/ticker/AAPL), cryptocurrency symbol (/crypto/BTC), and ISIN code (/isin/US0378331005).

What You Get Back

From the image CDN, you get a rendered logo in your choice of format (JPG, PNG, or WebP) at sizes up to 2048px with retina support. You can request light or dark theme variants, greyscale versions, and even specify exact dimensions.

If a logo isn't in the database, Logo.dev generates a fallback monogram, a styled letter-based placeholder using the first letter of the company name. So you never get a broken image in dashboards or lists.

The Describe API returns structured data, but it's more limited than what Context.dev offers. You get colors and social links, but no fonts, no design system extraction, no AI-powered queries.

Pricing

Logo.dev's free tier is generous: 500K requests per month is enough for a lot of production apps. The catch is that you must display a "Logos provided by Logo.dev" attribution link. If that's a dealbreaker for your UI, the $50/mo Startup plan removes it.

There are no per-second or per-minute rate limits on any plan. Logo.dev uses proactive enforcement — they'll email you before taking any action if you exceed your monthly quota. They don't cut you off without warning.

The Describe API — structured brand data beyond images — is only on the Pro plan at $180/mo. If you need logos and metadata, that's more expensive than Context.dev or Brandfetch for similar data.

CDN Performance

Logo.dev runs on 200+ edge locations and claims sub-50ms response times with 99.9%+ uptime. They monitor millions of companies daily for logo changes and update within 24 hours.

Best For

Logo.dev is the right choice if you need logo images and nothing else. For teams migrating from Clearbit, it's the easiest switch: the URL structure is similar, the integration is a single <img> tag, and the free tier covers most small-to-medium apps. If your use case is "show company logos in a list," this does it with minimal effort.

Brandfetch: The Brand Asset Toolkit

Brandfetch is somewhere between Logo.dev's simplicity and Context.dev's breadth. It started as a brand asset platform (you might know their Chrome extension for grabbing brand guidelines) and has since added a developer-focused API.

How It Works

Brandfetch offers two distinct products:

Logo API (free): A CDN endpoint similar to Logo.dev:

<img src="https://cdn.brandfetch.io/stripe.com?c=YOUR_CLIENT_ID" />

Brand API (paid): A REST endpoint that returns full brand data:

curl -H "Authorization: Bearer YOUR_API_KEY" \
  https://api.brandfetch.io/v2/brands/stripe.com

The Brand API supports lookups by domain, stock ticker, ISIN, and cryptocurrency symbol. In 2025-2026, Brandfetch added explicit type routes (/v2/brands/domain/stripe.com, /v2/brands/ticker/AAPL) to avoid identifier collisions.

They also ship an official JavaScript SDK:

import Brandfetch from 'brandfetch';
 
const bf = new Brandfetch({ apiKey: 'YOUR_KEY' });
const brand = await bf.fetch('stripe.com');

What You Get Back

The free Logo API returns logo images in WebP (default), PNG, JPG, or SVG format. You can request three logo types: icon (square mark), symbol (brand symbol), or logo (full wordmark). Light and dark variants are supported, and you can specify custom dimensions.

Brandfetch offers several fallback options when a logo isn't found: their own branding, a transparent image, a lettermark, or a 404. You pick which behavior you want.

The paid Brand API returns a richer dataset: multiple logo variants, color palettes, font information, brand images/banners, company descriptions, and social links. If a brand isn't in Brandfetch's dataset, the API will index it in real time before returning results.

Brandfetch also emphasizes first-party brand verification. Brands can claim their profile on Brandfetch and verify their own assets, which gives you higher data quality than pure scraping-based approaches.

Brandfetch also launched a Transaction API in 2025, which converts payment labels (the cryptic strings on bank statements) into merchant brand data. If you're building a fintech product, this matters — the other two don't offer it.

Pricing

Brandfetch's free Logo API tier doesn't require attribution, which is an advantage over Logo.dev's free tier. However, the limits are described as "fair use" rather than a hard number, which introduces some ambiguity.

The Brand API at $99/mo gives you structured brand data (logos, colors, fonts, metadata) for 100 brands per month at the base level. Overage is $0.10 per additional brand call. Brandfetch offers a 20% discount for startups and nonprofits for the first 12 months.

Compared to Context.dev's Starter plan ($49/mo for 3,000 brand retrievals), Brandfetch's Brand API is more expensive per brand lookup. However, the pricing structures are different enough that a direct per-unit comparison can be misleading; evaluate based on your expected volume.

Best For

Brandfetch works well if you need brand kits (logo variants, colors, fonts) and care about first-party brand verification. The Transaction API makes it the only real option for fintech payment-label enrichment. And the free Logo API without attribution is a good deal for teams that want logo images in production at zero cost.

Head-to-Head Feature Comparison

Here's how they compare across the dimensions that matter in practice.

Data Breadth

Context.dev has the most data. Logo.dev is intentionally narrow — that's the point. Brandfetch is in the middle.

Developer Experience

Logo.dev wins on simplicity — if you just want logos in <img> tags, nothing is faster to set up. Context.dev has the most complete SDK with typed responses and error classes. Brandfetch's JavaScript SDK is solid but only covers one language.

Pricing Value Analysis

To make pricing tangible, let's look at three common scenarios:

Scenario 1: Startup dashboard showing logos for 500 companies/month

• Context.dev: Free tier covers this (50 brand retrievals via API + Logo Link for image serving)
• Logo.dev: Free tier covers this easily (500K image requests/mo)
• Brandfetch: Free Logo API covers image serving; Brand API at $99/mo if you need metadata

Scenario 2: SaaS platform needing logos + brand colors for 5,000 companies/month

• Context.dev: Starter at $49/mo (3,000 brand retrievals included; overage for remaining 2,000 at $19/10K credits = ~$38 extra, so ~$87/mo total)
• Logo.dev: Pro at $180/mo for Describe API access (gives colors + metadata)
• Brandfetch: Brand API at $99/mo base + overage at $0.10/call for 4,900 extra calls = ~$589/mo

Scenario 3: Enterprise app with 50,000 brand lookups/month

• Context.dev: Pro at $149/mo (20,000 included) + overage for 30,000 at $9/10K = $176/mo total
• Logo.dev: Enterprise (custom pricing, likely $500+/mo)
• Brandfetch: Enterprise (custom pricing)

At higher volumes needing more than images, Context.dev's credit-based pricing is more predictable. Logo.dev is cheapest for pure image serving. Brandfetch's per-call overage adds up at scale.

Data Freshness and Coverage

All three providers monitor for brand changes and aim to keep logos current:

• Context.dev re-indexes tens of millions of brands quarterly, with a 24-hour turnaround for update requests. Logo CDN URLs are guaranteed valid for one year.
• Logo.dev monitors millions of companies daily and claims updates within 24 hours of a rebrand.
• Brandfetch claims 44M+ brands in their database with real-time indexing for brands not yet in the dataset. Their first-party verification model means some brands are actively maintained by the companies themselves.

Brandfetch claims the largest database, but size alone doesn't tell you much — what matters is coverage for your user base. All three cover the major companies well; differences emerge in the long tail of smaller businesses and regional brands.

Reliability and Performance

Logo.dev's monogram fallback means no broken images, and their no-rate-limits policy simplifies capacity planning.

Migration from Clearbit

If you're coming from Clearbit's Logo API, here's what each migration looks like:

To Logo.dev: Closest to a drop-in replacement. Change the base URL from logo.clearbit.com to img.logo.dev and add a ?token= parameter. Logo.dev was built by the original Clearbit team specifically for this migration path.

To Context.dev: Slightly more involved but gives you more data. Replace the Clearbit URL with Logo Link for image serving (similar simplicity), or integrate the full SDK to get brand colors, fonts, and metadata alongside logos. Context.dev publishes a detailed migration guide.

To Brandfetch: Replace the Clearbit URL with the Brandfetch Logo API CDN endpoint. Similar level of effort to Logo.dev for basic logo serving; add the Brand API SDK if you need richer data.

When to Use Which

Direct recommendations:

Pick Context.dev if:

• You need brand colors, fonts, or design data alongside logos
• You're building personalized onboarding, dynamic theming, or branded document generation
• You want AI-powered data extraction (product catalogs, custom queries, web scraping)
• You need screenshots or design system extraction
• You want the most data per API call
• Cost efficiency matters at scale for brand data lookups

Pick Logo.dev if:

• You only need logo images, nothing else
• You're migrating from Clearbit and want the simplest possible switch
• You need the highest free-tier volume for logo images (500K/mo)
• Simplicity is your top priority (no SDK, just a URL)
• You value no per-second rate limits

Pick Brandfetch if:

• You're building a fintech product and need the Transaction API
• First-party brand verification matters to your compliance requirements
• You want a free logo CDN without attribution requirements
• You need SVG logos specifically
• You value an active changelog and rapid feature iteration

The Bigger Picture

Clearbit's shutdown was disruptive, but the replacements are better than what we had before. Each service does something different:

Context.dev is a brand data platform — logos are one piece of a larger dataset that includes colors, fonts, metadata, and AI extraction. If you need more than images, this is where you'd start.

Logo.dev serves logo images fast and simply. For teams that just need logos, the overhead of a full brand platform doesn't make sense.

Brandfetch spans three products (Logo API, Brand API, Transaction API) serving different use cases. First-party brand verification is a real advantage for data quality.

You can also mix them. A fintech dashboard might use Logo.dev for fast image rendering and Context.dev for brand theming on detail pages. A payments app might use Brandfetch for transaction mapping and their free Logo API for display.

Getting Started

All three have free tiers. Try them with your actual data:

• Context.dev: Sign up free — 500 API credits + 10K Logo Link requests
• Logo.dev: Create a free account — 500K logo image requests/month
• Brandfetch: Register for the Logo API — free logo serving with fair-use limits

Run a few hundred of your most common domains through each one. Check logo quality, look at what metadata comes back, measure response times. That'll tell you more than this article can.