Skip to main content
We email you before you reach your limit, so it’s never a surprise. What happens next depends on your plan.
Logo.dev uses rate limits to ensure fair use and keep services affordable. All limits are based on monthly request counts.

​
Limits by plan

Limits are based on monthly request counts and scale with your plan. The free tier includes a generous monthly allowance that covers most projects. Logo.dev includes a generous monthly request allowance on every plan, including the free tier. For the current request limits and pricing by plan, see logo.dev/pricing.

​
Enforcing rate limits

We email you as you approach your limit, so you’re never caught off guard. This section is about the monthly request pool. The Brand API is metered separately through credits and enforced hard on every plan: see Credits below. Free (Community) plan: the monthly request limit is a hard cap. Once you reach it, requests stop until the limit resets at the start of the next month, or you upgrade. Paid plans: request-pool enforcement is soft. Your service keeps running if you go over, and we’ll ask about a higher tier if it becomes a consistent pattern. We never move you to a higher plan or bill you automatically. The one exception is auto-reload: it tops up your credits only when you switch it on and set the trigger yourself. Clear fair use violations can lead to a shutoff on any plan, but only after we’ve reached out.

​
What counts as a request

Each API call = one request:
  • Images (img.logo.dev)
  • Search API
  • Stock Ticker API
  • Describe API
Responses that return 202 (still indexing) count too. Every call that reaches the API is one request, whatever it returns: a logo, a 200, a 202, or a 404. When a lookup returns 202, retry after a few seconds instead of in a tight loop. The same request resolves to a 200 (or a 404 when there’s no data) once indexing finishes, so a short backoff avoids spending extra requests on repeated 202s. See errors and status codes for every status.

​
Credits

The Brand API is metered separately: its requests use prepaid credits, not your monthly request pool. Credits cost 1¢ each (100 credits per $1), and each Brand API request uses 5 credits. Every plan includes a monthly credit grant: 500 credits on Community and Startup, 15,000 on Pro, and whatever your contract says on Enterprise. At 5 credits a request that’s 100 Brand calls a month on Community and Startup, and 3,000 on Pro. The grant renews on your billing date and doesn’t roll over. Unlike the request pool, credits are a hard stop on every plan, paid ones included. When you run out, requests return a 402 until the next grant lands or you top up. On Pro, Enterprise, or a custom contract you can buy credits on the billing page. Every other plan upgrades to Pro first. Purchased credits never expire.

​
FAQs

Yes. Every call that reaches the API counts as one request, including a 202 while a domain is still indexing. Retry after a few seconds rather than in a tight loop: the lookup resolves to a 200 (or 404) once indexing finishes, so a short backoff avoids spending extra requests on repeated 202s.
For custom limits or higher volumes, contact us.
On the free plan, requests stop once you reach your monthly cap; upgrade or wait for the reset at the start of next month. On a paid plan, your service keeps running and we’ll ask about a higher tier if you’re consistently over. We email you before you get there either way.
No. If logos aren’t loading, it’s not because of rate limits unless we’ve specifically emailed you. Check your API key and implementation first.
View your real-time usage in your dashboard. The API returns no usage or quota headers to poll instead. For Free plans, note that limits may adjust based on system demands.
On a paid plan, a little over is fine—we won’t stop you immediately, though it’s a good sign it’s time to upgrade. On the free plan the cap is firm: once you hit it, requests stop until the next month’s reset.
No. Logo.dev only enforces monthly request limits—there are no burst rate limits. That said, please be reasonable with your request patterns and follow our fair use guidelines.