Company Logo API: What Still Works After Clearbit Died
On 16th November 2026, I asked the internet's address book for logo.clearbit.com, the web address developers used for years to fetch any company's logo, and the answer came back: no such address exists. HubSpot had deprecated the Clearbit Logo API on 18th March 2025 and shut it down completely on 8th December 2025.
The stake here is simple: you are shipping broken images silently. If you are building a customer dashboard and relying on a dead web address, your users see grey boxes or broken image icons where a brand logo should be. It makes a professional SaaS look broken. As Reddit user bsick_ said in the deprecation thread back in March 2025: "Man this sucks!! I'm already having issues with other apis".
Finding a free replacement is harder than it looks. I tested img.logo.dev/stripe.com on 16th November 2026 and the server refused the request with status 401, because Logo.dev requires a publishable key. It is not a drop-in replacement for a free public service.
I measured what actually works today. NinjaPear's Company Logo API is free. On 16th November 2026, it returned valid logo image links for stripe.com, notion.so, calm.com, midjourney.com and anthropic.com, with responses between 31 and 463 milliseconds.
This guide shows you how to wire this into your frontend and how to handle the transition when your previous logo source vanishes.
Is the Clearbit Logo API still working?
No. The Clearbit Logo API is completely offline. HubSpot deprecated the service on 18th March 2025 and shut it down completely on 8th December 2025. You can find the details in the HubSpot community notice and the Clearbit changelog.
I verified this myself with a DNS lookup on 16th November 2026. The address logo.clearbit.com no longer points anywhere. It is a dead end.
The real danger for developers is that this failure is silent. Countless tutorials and Stack Overflow answers still recommend the old one-line image tag. When you use it, your build does not throw an error. The image simply fails to load in the browser. If you do not check your frontend carefully, you ship broken images to your users.
What can you use instead of the Clearbit Logo API?
NinjaPear's Company Logo API is the replacement I would put first, and it is what the rest of this guide uses. It is free, it needs no attribution, and the same API key also gets you the company's funding, headcount and other core details through 29 MCP tools. You are not buying a logo endpoint bolted onto a billing plan. You are getting one surface of a company intelligence API.
The market has other names, and it is worth knowing their caveats before you wire any of them in.
Logo.dev positions itself as the one-to-one Clearbit replacement. Read their pricing page closely, because I did on 17th November 2026: the free tier requires attribution, meaning you must show a link like "Logos provided by Logo.dev" wherever your logos appear, or in your footer. Only a paid plan removes it. Their endpoint also requires a publishable key: I tested img.logo.dev/stripe.com on 16th November 2026 and got status 401 back without one. NinjaPear requires no attribution at any tier, and the logo endpoint is free.
Other names come up in the Reddit threads: Brandfetch, thecompaniesapi.com, logokit.com, brandicons.dev, logostream.dev for stock logos by ISIN, and Simple Icons if all you need are famous open-source brand icons. Two caveats repeat in those threads. First, most of these services are key-gated and billed, not free. Second, many of them only return the square symbol, not the full wordmark with the company name spelled out. Developers are still looking for a reliable way to get full wordmarks or lockups.
How do you call NinjaPear's Company Logo API?
NinjaPear's Company Logo API is free and simple. You make one API call: a GET request with the company's website and your API key in the header.
Here is how you can do it with curl:
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://nubela.co/api/v1/company/logo?website=stripe.com" \
--output logo.png
If you are building a backend service, here is a Python snippet to save the image for you:
import requests
headers = {"Authorization": "Bearer YOUR_API_KEY"}
url = "https://nubela.co/api/v1/company/logo?website=stripe.com"
response = requests.get(url, headers=headers)
if response.status_code == 200:
with open("logo.png", "wb") as f:
f.write(response.content)
On 16th November 2026, I measured how long the API took for stripe.com, notion.so, calm.com, midjourney.com and anthropic.com. Every call returned a valid logo image link in 31 to 463 milliseconds. Note that the API returns the logo image file itself, not a box of data you have to unpack.
I should be plain about one thing: this is not a drop-in public image URL like the old Clearbit tag. Because it requires an API key, you cannot put the request directly in an HTML image tag, or your key would leak to every visitor's browser.
The solution here is a proxy pattern. You create a tiny endpoint on your own server that fetches the image from the API and serves it to the frontend. This keeps your key private while still delivering the logo to the user.
What happens when the logo is missing?
Not every company has a high-resolution logo available. Before you make the call, clean up the website address: strip the https://, the www. and any trailing slash, and use lowercase.
If we do not have the logo, the API tells you clearly that we do not have it, and you pay nothing. Treat that answer as data. Log it and serve a neutral placeholder instead. The industry standard for this is a colored square with the company's first initial in it.
Logo.dev handles this automatically with monogram fallbacks. If you are using your own proxy, you will have to build this fallback yourself. When a call fails, serve your placeholder instead of a broken image icon.
Lastly, do not retry these calls in a tight loop. If the logo is missing once, it is unlikely that it will appear a millisecond later. Log the failure and move on to the next website.
Which one should you pick?
NinjaPear's Company Logo API is the best pick for almost everyone reading this. It is free, it requires no attribution, there is no "powered by" badge to put in your footer, and the same API key returns company details, funding and headcount through 29 MCP tools. When looking at a company data enrichment tools comparison, most commercial options are locked up in expensive bulk plans. I have analyzed what Reddit users actually pay for and the preference is usually for specific, reliable, free-to-try endpoints. If you are exploring Clearbit alternatives and migration paths, a structured API with no attribution beats a badge you have to display.
The niche exceptions: if you only need famous open-source brand icons, Simple Icons works and needs no API at all. And if you want a content delivery network that serves images straight into an image tag and you are willing to carry their attribution link on a free plan or pay to remove it, Logo.dev exists. For everything else, the free endpoint with no strings is the one I would ship.
The Clearbit shutdown is the real lesson here. A free one-line dependency can vanish overnight. Put a proxy in front of whatever logo source you pick so that you can swap sources without ever touching your frontend code. Keep the date in mind: 16th November 2026. Dead services and live ones were all measured on the same day.