Concurrent Browser Limits
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.Current Plans
| Plan | Concurrent Browsers |
|---|---|
| Free | 2 |
| Hobby | 5 |
| Standard | 50 |
| Growth | 100 |
| Scale / Enterprise | 150+ |
Extract Plans (Legacy)
| Plan | Concurrent Browsers |
|---|---|
| Free | 2 |
| Starter | 50 |
| Explorer | 100 |
| Pro | 200 |
API Rate Limits
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.Current Plans
| Plan | /scrape | /map | /crawl | /search | /extract | /crawl/status | /extract/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 |
Batch Endpoints
Batch endpoints follow the /crawl rate limits.FIRE-1 Agent
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 |
Extract Plans (Legacy)
| Plan | /extract (requests/min) | /extract/status (requests/min) |
|---|---|---|
| Starter | 100 | 25000 |
| Explorer | 500 | 25000 |
| Pro | 1000 | 25000 |

