Free logo APIs in 2026: 5 real providers and their limits

Quikturn is the strongest free logo API fit for a finance team that searches by company name, domain or ticker; Brandfetch fits browser-embedded logos without attribution; Logo.dev fits a high-volume domain-led app. This 2026 comparison covers five services that actually serve company logos, not favicons or developer-profile avatars. The limits below are vendor-published allowances, not results from an independent coverage test.

Why this matters

A limit is only useful if it applies to the operation you need. A browser-hosted image, a server-side download and a brand-data lookup can have different allowances under the same vendor name. In 2026, check the lookup identifier, delivery method, attribution, caching rights and output before committing to a provider.

A domain is also not a legal entity. For a deal-team logo wall, test ambiguous company names, subsidiaries, recent rebrands and tickers against a real target list. A successful image response does not prove the mark is current or cleared for your use.

What makes the best free logo API?

• Useful lookup keys: Can you start with the domain, company name or ticker you actually have?
• Comparable free allowance: Is it per month, per day or a one-time trial allotment? Does a separate brand-data request consume credits?
• Usable output: Can you get the logo variant and resolution required for the final placement?
• Delivery rights: Can you embed only, or fetch and cache an image for your own workflow?
• Production terms: Is attribution required? Are there burst limits or origin restrictions beyond the headline quota?

These criteria rank suitability for a use case, not independently measured logo accuracy. The provider pages were checked on September 28, 2026; vendor allowances can change.

The 5 free logo APIs at a glance

Method: These figures come from each provider's current pricing or product documentation, not from a matched workload. A daily cap is not converted into a monthly promise. Quotas do not measure match quality, latency or rights to use an individual trademark. The table deliberately excludes Wikimedia, Wikidata, Wikipedia, GitHub, GitLab and favicon endpoints: they are not comparable hosted company-logo APIs.

1. Quikturn: best free logo API for finance identifiers

Quikturn's current API plan lists logo retrieval by domain, company name or ticker and 1 million free requests per month. Its free plan requires attribution and lists a 50-request-per-minute limit for server keys. Quikturn also has a web app and PowerPoint workflow for analysts; that is useful if the same company list has to become a slide rather than just an app image.

Quikturn pros:

• Name, domain and ticker lookup address different inputs in a finance workflow.
• The 1 million monthly allowance is explicit on its pricing page.
• A non-developer can work with company logos in the web app instead of making API requests.

Quikturn cons:

• The free API requires attribution.
• A 50-request-per-minute server-key ceiling matters for bursty backend jobs even when the monthly quota is ample.
• Published coverage is not proof that every private company in your target list resolves correctly.

Best for: Developers serving a banker-facing product and teams that also need deck production. Verdict: Buy for a pilot with your own company list; review the exact asset and usage rights before client delivery.

2. Brandfetch: best for direct logo display without attribution

Brandfetch's current Logo API overview states a soft fair-use allowance of 500,000 requests per month, with no attribution. It accepts domains and identifiers such as tickers and ISINs, and offers icon, symbol and logo variants. Its standard Logo API is designed for logos embedded directly in a user-facing application, not for collecting files into an asset store.

Brandfetch pros:

• No attribution requirement on the standard free Logo API.
• Multiple identifiers and logo variants support a wider set of UI placements than a favicon.
• The current documentation spells out throughput and usage rules alongside the monthly allowance.

Brandfetch cons:

• Programmatic image fetching is not allowed under the standard usage guidelines; caching needs a custom arrangement.
• The service requires a client ID, direct hotlinking and a suitable referring origin.
• The fair-use allowance is soft, not a guarantee of unlimited traffic above it.

Best for: An application that renders logos directly in a browser. Verdict: Buy for that display pattern; skip the standard terms for a backend asset-ingestion pipeline. A separate Brandfetch migration guide still says 1 million per month. This comparison uses the 500,000 figure on its current Logo API overview and recommends confirming the applicable account allowance before launch.

3. Logo.dev: best for a domain-led app migration

Logo.dev's Community plan lists 500,000 monthly requests and 500 monthly credits. Its table counts a Logo API or Search API request as one request and a Brand API call as five credits; do not treat the 500 credits as another 500,000 brand-data calls. Logo.dev offers a hosted logo endpoint suitable for a domain-based application, with other identifiers supported in its product documentation.

Logo.dev pros:

• The monthly image-request allowance is explicit.
• A hosted logo is a straightforward replacement for a domain-driven image integration.
• Search and richer brand data are available, with separate accounting shown on the plan table.

Logo.dev cons:

• Community use requires a visible attribution link on the production site under its attribution rules.
• The brand-data credit allowance is much smaller than the logo-image request allowance.
• The free plan limits some output variants; check the requested file type against the plan before relying on it.

Best for: Developers primarily displaying company images in a web product. Verdict: Buy for a domain-led pilot; hold if your main task is exporting high-resolution assets into decks.

4. LogoKit: best for small UI icons keyed by domain or ticker

LogoKit's plan comparison lists 5,000 logo requests per day on Free, covering brand, stock and crypto logo access. The same plan table lists a maximum resolution of 64 × 64 pixels. Server-side logo access and infrastructure caching are not listed for Free.

LogoKit pros:

• A daily allowance is clear for a small, steady display workload.
• Domain and market-identifier workflows are available in the provider's product descriptions.
• Stock and crypto icons sit alongside company logos for financial interfaces.

LogoKit cons:

• The free image size is a poor fit for large PowerPoint placements.
• Free usage requires attribution according to its migration guidance.
• A daily ceiling can stop a burst even when the month's total would have been modest.

Best for: Small app icons or watchlists, not a finished logo wall. Verdict: Hold for deck work; buy for a small UI pilot if 64 × 64 pixels is sufficient.

5. Context.dev Logo Link: best for testing hosted domain logos

Context.dev's pricing page lists 10,000 logo pulls on the Free tier as a one-time allowance. It separately lists 1,000 credits per month and up to 100 monthly brand retrievals. These are distinct counters: a free Logo Link trial is not an ongoing 10,000-per-month entitlement. Its Logo Link guidance describes direct hosted-image embedding with a public client ID and referring-domain restrictions.

Context.dev pros:

• Logo Link provides a hosted image for a known domain.
• The broader brand product can return more than an image when that is your actual need.
• The published free allowance is enough to test a limited set of domains.

Context.dev cons:

• The logo allowance is one-time, so it cannot be compared directly with the recurring plans above.
• Logo Link's usage guide disallows downloading, persisting or rehosting the image.
• Domain-based display does not by itself resolve an ambiguous company name in a deal list.

Best for: Evaluating direct image display alongside brand-data retrieval. Verdict: Hold until you know the ongoing allowance and usage terms for your deployment.

How these providers were ranked

The order prioritizes explicit recurring free logo allowances and fit for company-identity workflows, then production restrictions and output. It is a buying framework, not a claim that one provider returned more correct logos in a controlled test. For a fair 2026 pilot, give each service the same list of public companies, private companies, subsidiaries and recent rebrands; record wrong matches, absent assets, usable formats and any fallback images separately.

Which free logo API should you choose?

Choose Quikturn when your data begins as company names or tickers and the output also has to work for analysts building slides. Choose Brandfetch for direct, attribution-free browser display under its hotlinking rules. Choose Logo.dev for a domain-led image integration; LogoKit for compact icons; Context.dev Logo Link for a bounded trial. Do not choose by the headline request count alone: the server-key pace, asset format and permitted delivery method can decide whether a free plan works at all.

If you are replacing a retired endpoint, first inventory where images are displayed and whether your app downloads or caches them. A provider that permits a browser image is not automatically a substitute for a server-side asset pipeline. For the migration context, see Quikturn's Clearbit replacement guide, but verify current vendor quotas against the primary sources above rather than older roundup tables.

FAQ

One last thing

In a market map, a polished fallback can hide a missed company match. Treat every fallback as an exception for analyst review, not as proof the correct logo was found. That check matters more than the biggest published quota.