Firecrawl Pricing 2026: Plans, Credits, and Cost Planning
Firecrawl uses a credit-based model. Scrape and crawl cost 1 credit per page; map costs 1 credit per call. Free tier: 1,000 credits every month, no credit card required. Paid plans, billed yearly: Hobby $16/mo (5k credits), Standard $83/mo (100k), Growth $333/mo (500k), Scale $599/mo (1M). Monthly billing is $19, $99, $399 and $749.
2026 Pricing Tiers
| Plan | Credits | Billed yearly | Billed monthly | Pay-as-you-go | Concurrent browsers |
|---|---|---|---|---|---|
| Free | 1,000/mo, no card | $0 | $0 | Not available | 2 |
| Hobby | 5,000/mo | $16/mo ($190/yr) | $19/mo | 1,000 credits per $5 | 5 |
| Standard | 100,000/mo | $83/mo ($990/yr) | $99/mo | 2,000 credits per $5 | 25 |
| Growth | 500,000/mo | $333/mo ($3,990/yr) | $399/mo | 2,500 credits per $5 | 50 |
| Scale | 1,000,000/mo | $599/mo ($7,190/yr) | $749/mo | 5,000 credits per $5 | 100 |
| Enterprise | Custom | Custom | Custom | Custom | Custom |
Free credits reset every month and do not roll over. Yearly billing saves $38 on Hobby, $198 on Standard, $798 on Growth and $1,798 on Scale versus paying monthly (firecrawl.dev/pricing, checked 2026-11-10).
Credit Consumption by Feature
| Feature | Credits |
|---|---|
| Scrape | 1/page |
| Crawl | 1/page |
| Map | 1/call (regardless of links) |
| Search | 2/10 results |
| JSON format (LLM extraction) | +4/page |
| Interact (browser session) | 2–7/browser minute, 1-minute minimum |
| Agent | 5 daily runs free; dynamic pricing |
Scrape and crawl are the main consumers. Map is efficient: one call can return thousands of URLs for 1 credit. Watch JSON-format extraction: it takes a page from 1 credit to 5.
Cost Planning Formula
effective_credits ≈ pages_scraped + pages_crawled + map_calls + (search_results ÷ 5) + (json_pages × 4) + (browser_minutes × 2 to 7)
Add 10–25% buffer for retries and instability.
Example: 50,000 pages/month, 12% retry overhead → budget ~56,000 credits. Standard plan (100k) fits; Hobby (5k) does not.
Where Teams Burn Credits
- Unscoped crawls — Crawl entire domains instead of mapping first
- Redundant rescrapes — Reprocess unchanged pages on short schedules
- Extraction on low-value pages — Run schema extraction on every page
- Unbounded retries — Retry failures indefinitely without caps
Use /map to scope URLs. Cache content hashes to skip unchanged pages. Apply extraction only to high-value paths.
Free Tier Strategy
- 1,000 credits a month: test extraction quality, schema design, proof of concept
- Not for production planning; validate with a controlled paid pilot first
Overage and Pay-as-You-Go
Paid plans can top up in $5 increments: 1,000 extra credits on Hobby, 2,000 on Standard, 2,500 on Growth, and 5,000 on Scale. The Free plan has no pay-as-you-go. When your balance hits zero, Firecrawl adds one increment and charges the card on file. You set a monthly spend cap in billing settings; a cap of 0 turns pay-as-you-go off.
Purchased credits stay on your account until you use them, but they expire if you cancel. Plan credits on Hobby, Standard and Growth do not roll over. Annual Scale plans roll unused plan credits over for 1 month, and annual Enterprise plans for 2 months (billing docs).
Compare with Alternatives
For under ~500k pages/month, Firecrawl credit pricing is often competitive. For millions of lightweight pages or heavy anti-bot needs, Apify compute units may scale better. See Firecrawl vs Apify for a detailed comparison.
Run a 7-day pilot on your target domains. Track credits per successful record to forecast real cost.
Estimate from pages scraped + crawled + map requests. Add 10–25% buffer. Track credits per valid record in a pilot.
Unscoped crawls, rescraping unchanged pages, and extraction on low-value pages are the main sources.
No. Use it for validation only. Production planning should use a paid pilot with your real domain mix.
Hobby, Standard and Growth plan credits do not roll over. Annual Scale plans roll unused credits over 1 month and annual Enterprise 2 months. Pay-as-you-go credits stay until used but expire if you cancel.
A scrape that returns no document costs 0 credits. A page that comes back with an error status such as 403 or 404 is still returned and costs 1 credit. Browser sessions are billed per minute whether or not they succeed.
