Scraping API PricesAll products / Firecrawl
Firecrawl pricing
How Firecrawl credits vary across scraping, crawling, search, extraction, and browser use, what remains open, and who fits.
Every available option was priced in advance from published vendor rules. Changing a control only switches between those checked options; nothing is sent anywhere and no account is needed.
Your job
What Firecrawl counts
What you pay
Successes you want
100,000 pages
Your stated workload. Every vendor on this site is priced against this same number.
- ÷ 0.95
Attempts you are billed for
105,263 requests
Firecrawl bills failed fetches, so a 5% failure rate is billed work.
- × 1
What the meter counts
105,263 credits
One attempt is one billed unit for this workload.
- =
Cash per month
$399.00 /mo
Growth. Cheapest of every eligible purchase option, not the first plan that fits.
Bars share one linear scale across the 3 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
100,000 pages divided by 95% success → 105,263 credit → Growth $399.00/mo = $3.99 per 1,000 pages kept
The arithmetic, line by line
- pages: 1 credit per pagesource
- request.js_render: no multiplier published, treated as included
- billed on 105,263 attempts, not 100,000 successes, because this vendor charges for failed requestssource
- consumes 105,263.16 credit per month
- cheapest way to buy that: Growth, 500,000 included = $399.00 per monthsource
- 394,737 of the included allowance goes unused, 79% of what you buy
Cheaper for this job
Same 100,000 JavaScript-rendered pages a month at a 95% success rate, ranked by what you would actually be billed. Unknown totals never enter the numeric order.
Every Firecrawl plan
| Plan | Monthly | If billed yearly | Prepaid pack | Included | Simultaneous sessions |
|---|---|---|---|---|---|
| Hobby | $19.00 | $16.00 | n/a | 5,000 credit | 5 |
| Standard | $99.00 | $83.00 | n/a | 100,000 credit | 50 |
| Growth your job | $399.00 | $333.00 | n/a | 500,000 credit | 100 |
| Scale | $749.00 | $599.00 | n/a | 1,000,000 credit | 100 |
What consumes a unit
This is where a bill actually grows. One operation is not one billed unit, and the multiplier is published here rather than on the pricing page.
| Operation | Costs | Per | Source |
|---|---|---|---|
| request.basic | 1 credit | page | source |
| crawl.page | 1 credit | page | source |
| search.query | 2 credit | 10 result | source |
| browser.session_time | 2 credit | browser_minute | source |
| request.ai_extraction | 5 credit | page | source |
| request.premium_proxy | 5 credit | request | source |
| request.pdf_parse | 1 credit | page | source |
What Firecrawl does not publish
- The fixed credit cost of Agent is not published.
- The exact token direction and payload accounting for Extract are not published in the selected billing guide.
- Credit-pack sizes and prices were not obtainable from the public pricing-page text.
- The schema has one meters_combine field, but Firecrawl mixes replacement pricing, additive features, and separately billed browser time.
What Firecrawl is
Firecrawl is a web data platform with scrape, crawl, map, search, monitor, structured extraction, agent, and browser-interaction operations. It is aimed at developers building retrieval, research, enrichment, and agent workflows that need web content in application-ready formats. Olostep, Hyperbrowser, and Apify are the nearest named comparisons. Firecrawl differs from them by centering one API family on turning sites into content and context while also exposing search, an agent, and a browser sandbox. Sources: Firecrawl pricing, Firecrawl browser documentation, Olostep, Hyperbrowser pricing, and Apify pricing, retrieved 2026-07-26.
How billing works
The shared accounting unit is a credit, but the workload unit changes by feature. Basic scrape, crawl, map, and monitor usage follows pages; search follows returned-result groups; browser interaction follows elapsed browser minutes; enhanced access and structured extraction can consume more credits; and Agent uses dynamic pricing. Some browser-interaction paths also bill the initial scrape separately. Firecrawl does not charge Firecrawl-side timeouts or server errors, but it does charge when it fetches a page and the target site returns an error response. The common buying mistake is to equate one page with one credit across every endpoint. Sources: Firecrawl pricing, browser documentation, Interact documentation, and extraction guide, retrieved 2026-07-26.
What Firecrawl does not publish
- A fixed credit cost for Agent, which the pricing page labels dynamic. Source reviewed: Firecrawl pricing, retrieved 2026-07-26.
- A complete public conversion for structured extraction that separates input, output, and other token accounting. Source reviewed: Firecrawl extraction guide, retrieved 2026-07-26.
- A universal overage rate for exhausted monthly plans; the public page points to credit packs or higher plans instead. Source reviewed: Firecrawl pricing, retrieved 2026-07-26.
- One combination rule covering base scrapes, enhanced modes, browser interaction, extraction, and Agent. Sources reviewed: Firecrawl pricing, Interact documentation, and stealth-mode documentation, retrieved 2026-07-26.
Who it suits
Firecrawl suits teams that want scrape, crawl, search, and browser interaction under one developer API and can measure the exact endpoint mix. It is less suitable for procurement that needs one fixed cost per successful page regardless of feature, or for an Agent-heavy budget that requires a published fixed run rate. The reason is that simple page retrieval maps cleanly to credits, while advanced extraction, browser time, and Agent introduce different or dynamic meters. Sources: Firecrawl pricing, browser documentation, and extraction guide, retrieved 2026-07-26.
Answer
Firecrawl's dated 2026-07-26 price snapshot gives $399.00 for 100,000 JavaScript-rendered pages on its Growth offer. This older figure is excluded from rankings; check the vendor before buying.
Recorded 2026-07-26 from the vendor's own pricing page.A vendor page moved or could not be matched closely enough. Treat this as an older snapshot and check the vendor before buying.