| title | Rate Limits |
|---|---|
| description | Rate limits for different pricing plans and API requests |
| og:title | Rate Limits | Firecrawl |
| og:description | Rate limits for different pricing plans and API requests |
Firecrawl uses subscription-based monthly plans. There is no pure pay-as-you-go model, but the auto-recharge feature provides flexible scaling. Once you subscribe to a plan, you can automatically purchase additional credits when you dip below a threshold. Larger auto-recharge packs offer better rates. To test before committing to a larger plan, start with the Free or Hobby tier.
Plan downgrades take effect at the next renewal. Unused-time credits are not issued.
Concurrent browsers represent how many web pages Firecrawl can process for you at the same time.
Your plan determines how many of these jobs can run simultaneously - if you exceed this limit,
additional jobs will wait in a queue until resources become available. Note that time spent waiting in the queue counts against the request's timeout parameter, so you can set a lower timeout to fail fast instead of waiting. You can also check current availability via the Queue Status endpoint.
| Plan | Concurrent Browsers | Max Queued Jobs |
|---|---|---|
| Free | 2 | 50,000 |
| Hobby | 5 | 50,000 |
| Standard | 50 | 100,000 |
| Growth | 100 | 200,000 |
| Scale / Enterprise | 150+ | 300,000+ |
Each team has a maximum number of jobs that can be waiting in the concurrency queue. If you exceed this limit, new jobs will be rejected with a 429 status code until existing jobs complete. For larger plans with custom concurrency limits, the max queued jobs is 2,000 times your concurrency limit, capped at 2,000,000.
If you require higher concurrency limits, contact us about enterprise plans.
| Plan | Concurrent Browsers | Max Queued Jobs |
|---|---|---|
| Free | 2 | 50,000 |
| Starter | 50 | 100,000 |
| Explorer | 100 | 200,000 |
| Pro | 200 | 400,000 |
Rate limits are measured in requests per minute and are primarily in place to prevent abuse. When configured correctly, your real bottleneck will be concurrent browsers. Rate limits are applied per team, so all API keys on the same team share the same rate limit counters.
| Plan | /scrape | /map | /crawl | /search | /agent | /crawl/status | /agent/status |
|---|---|---|---|---|---|---|---|
| Free | 10 | 10 | 1 | 5 | 10 | 1500 | 500 |
| Hobby | 100 | 100 | 15 | 50 | 100 | 1500 | 25000 |
| Standard | 500 | 500 | 50 | 250 | 500 | 1500 | 25000 |
| Growth | 5000 | 5000 | 250 | 2500 | 1000 | 1500 | 25000 |
| Scale | 7500 | 7500 | 750 | 7500 | 1000 | 25000 | 25000 |
These rate limits are enforced to ensure fair usage and availability of the API for all users. If you require higher limits, please contact us at help@firecrawl.com to discuss custom plans.
The extract endpoints share limits with the corresponding /agent rate limits.
The batch scrape endpoints share limits with the corresponding /crawl rate limits.
The browser sandbox endpoints have per-plan rate limits that scale with your subscription:
| Plan | /browser | /browser/{id}/execute |
|---|---|---|
| Free | 2 | 10 |
| Hobby | 20 | 100 |
| Standard | 100 | 500 |
| Growth | 1,000 | 5,000 |
| Scale | 1,500 | 7,500 |
In addition, each team's plan determines how many browser sessions can be active simultaneously (see Concurrent Browser Limits above). If you exceed this limit, new session requests will return a 429 status code until existing sessions are destroyed.
Requests involving the FIRE-1 agent requests have separate rate limits that are counted independently for each endpoint:
| Endpoint | Rate Limit (requests/min) |
|---|---|
| /scrape | 10 |
| /extract | 10 |
| Plan | /extract (requests/min) | /extract/status (requests/min) |
|---|---|---|
| Starter | 100 | 25000 |
| Explorer | 500 | 25000 |
| Pro | 1000 | 25000 |