FireCrawl Pricing 2026: Plans, Credits, and Real Cost Breakdown

By Mert Ozdemir, Head of Deliverability · Jun 28, 2026 · 10 min read · Last reviewed Jun 28, 2026

FireCrawl pricing decoded: credit math, plan tiers, rate limits, and worked cost examples at 5K, 50K, and 500K pages for cold email teams.

FireCrawl pricing, explained without the marketing fog

FireCrawl is the API a lot of growth teams reach for when they need to turn raw URLs into clean structured data: company sites, careers pages, news posts, product pages. It handles the headless browser, the proxy rotation, the markdown conversion, and the LLM-friendly output formatting. The pricing page lists a handful of plans and a credit number next to each one, which sounds simple until you actually try to model your monthly bill.

This guide breaks down what a credit really costs, how the Free, Hobby, Standard, Growth, and Enterprise tiers compare, where the rate limits will bite you, and what FireCrawl actually costs at 5,000, 50,000, and 500,000 pages per month. Then it compares FireCrawl to ScraperAPI, Bright Data, and Apify on a per-page basis, and shows where the tool fits inside a cold email workflow that ends with a campaign going out from a real FireCrawl-fed list.

If you are reading this because the snippet on Google looked vague, here is the short version: FireCrawl is fair to mid-priced for clean scrape jobs under about 200K pages a month, gets pricey above that compared to raw proxy providers, and is one of the few APIs where the credit accounting is honest enough that you can actually predict your bill.

How FireCrawl credits work

Every FireCrawl plan is denominated in credits. The credit is the unit FireCrawl charges for each API operation, and the cost depends on what you ask the API to do. The three endpoints that matter for most cold email and enrichment work are /scrape, /crawl, and /extract.

What 1 credit buys you

  • Standard scrape: 1 credit per page. This is a single URL fetched, rendered if needed, and returned as markdown, HTML, or structured JSON.
  • JS-rendered scrape with stealth or actions: 5 credits per page when you ask for stealth proxy mode, page actions (click, scroll, wait), or screenshots. This is the rate that catches teams by surprise.
  • Crawl endpoint: 1 credit per discovered page, billed as the crawler walks the site. A 200-page company website costs 200 credits.
  • Extract endpoint (LLM extraction): 5 credits per page when you pass a schema and let FireCrawl run an LLM over the page to pull structured fields. This is the most expensive operation and the one most teams misuse.
  • Map endpoint: 1 credit per call (not per URL), so mapping a domain to its sitemap is effectively free.

The accounting gets ugly when you combine modes. A schema-based extract with stealth proxy on a JS-heavy page can run 10 credits per page. Across 50,000 LinkedIn-adjacent pages that is 500,000 credits, which lands you in the Growth tier conversation fast.

FireCrawl plans in 2026

FireCrawl publishes five public tiers. Verify the exact numbers on firecrawl.dev before you commit, because pricing has shifted twice since the company launched, but the structure below is current as of mid-2026.

Free

  • 500 credits, one-time, not monthly.
  • 2 concurrent requests, 10 requests per minute on scrape.
  • No team seats, no SLA, community Discord support.
  • Good for: prototyping a scraper, testing schema extraction on 50-100 pages, evaluating output quality.

Hobby

  • Around $16 per month for 3,000 credits per month.
  • 5 concurrent requests, higher per-minute rate.
  • One seat, basic email support.
  • Good for: solo operators, a single enrichment workflow, a small lead list per week.

Standard

  • Around $83 per month for 100,000 credits.
  • 50 concurrent requests on scrape.
  • Up to 3 team seats.
  • Good for: an in-house growth team doing weekly enrichment passes over 10K-30K accounts.

Growth

  • Around $333 per month for 500,000 credits.
  • 100 concurrent requests, priority queue.
  • Up to 5 seats, faster support response.
  • Good for: agencies running enrichment for multiple clients, or a single product team pulling fresh data daily.

Enterprise

  • Custom pricing, typically starts around $2,000-$3,000 per month for 2-5M credits, volume discounts as you go up.
  • Dedicated IPs, custom rate limits, SOC 2 paperwork, SLA, dedicated Slack channel.
  • Unlimited seats in practice, although it is negotiated.
  • Good for: SaaS products embedding FireCrawl as the scrape backbone, or data teams doing 1M+ pages per month.

One thing to note: FireCrawl runs an annual prepay discount that knocks roughly 20% off the monthly numbers above if you commit for a year. Credit packs (one-time purchases that do not expire) are also available for teams with bursty workloads.

Rate limits, retention, and the fine print

Plan price is half the equation. Rate limits and operational constraints are the other half.

Concurrency

Free is 2 concurrent, Hobby is 5, Standard is 50, Growth is 100. If you are firing scrapes from a queue and your concurrency exceeds the plan limit, FireCrawl rate-limits with 429s and your worker has to back off. At Standard you can comfortably run a 50-worker pool, which is enough to crawl about 100,000 pages in a few hours if each scrape is around 2 seconds.

Per-minute caps

Each plan also has a per-minute scrape cap. Hobby is around 100 requests per minute, Standard is around 1,000, Growth is around 5,000. The Crawl endpoint has its own lower cap because it discovers URLs internally.

Job retention

Scrape job results are stored for 24 hours on Hobby, 7 days on Standard, 30 days on Growth, and configurable on Enterprise. If you do not pull results within the window, you re-pay the credits to re-run the scrape.

Team seats

Hobby gets 1 seat, Standard gets 3, Growth gets 5. Adding seats beyond the plan limit costs roughly $20 per seat per month, so a 7-person team on Growth is paying around $373 per month all-in.

Worked example 1: 5,000 pages per month

You are a solo growth operator. Each week you build a list of 1,000-1,500 prospect accounts, hit each company website's homepage and /about page, and pass the markdown to an LLM to pull the founding year, headcount estimate, and what the company actually sells. Two pages per account, 5,000 pages per month.

  • Standard scrape: 2 pages x 2,500 accounts = 5,000 credits.
  • Plan needed: Hobby ($16/mo, 3,000 credits) is short. Standard ($83/mo, 100,000 credits) is overkill but is the next tier.
  • Alternative: stay on Hobby and buy a 5,000-credit one-time pack, which is around $20. Total: $36/mo equivalent.

At this volume, FireCrawl is cheap and reliable. The trap is if you also run schema-based extract on each page (5 credits each), the same workflow becomes 25,000 credits and you are firmly on Standard at $83.

Worked example 2: 50,000 pages per month

You run a 4-person growth team enriching about 10,000 ICP accounts per week. Each account gets 5 pages scraped: homepage, /about, /careers, /pricing, and the top blog post. That is 50,000 pages per week if you refresh weekly, but most teams refresh monthly, so call it 50,000 pages per month.

  • Standard scrape: 50,000 credits, fits inside the Standard plan ($83/mo).
  • Schema extract on each page: 250,000 credits, requires Growth ($333/mo) or a 200K credit top-up on Standard ($150-ish), total around $230-$330/mo.
  • Effective cost: $0.005-$0.007 per page.

This is the sweet spot. FireCrawl beats DIY headless Chrome plus residential proxies once you factor in engineering time, and the schema extract endpoint replaces a separate LLM call. Compare to feeding raw HTML into GPT-4o-mini at around $0.0015 per page in tokens, plus a proxy bill of $0.001 per page, plus your own scraper code.

Worked example 3: 500,000 pages per month

You are running a SaaS that re-enriches a database of 500,000 companies monthly. You only need clean markdown of the homepage and /about, no schema extract.

  • Standard scrape: 1,000,000 credits.
  • Plan: Growth ($333/mo for 500K credits) plus a 500K credit overage pack (around $250), or move to Enterprise. Enterprise at this volume lands around $1,500-$2,000/mo with negotiation.
  • Effective cost: roughly $0.003-$0.004 per page on Enterprise.

At 500K pages, raw proxy providers like Bright Data become competitive on a pure per-request basis, but you eat the engineering cost of building your own renderer, retry logic, and markdown converter. FireCrawl is still cheaper once total cost of ownership is included, but the gap narrows.

FireCrawl vs ScraperAPI vs Bright Data vs Apify

Per-page cost is the cleanest way to compare. The numbers below assume JS rendering on, no extra features, public 2026 pricing.

FireCrawl

About $0.0008 per page on Standard, $0.0006 on Growth, $0.0004 on Enterprise. Includes browser rendering, markdown output, schema extract is extra. Best for teams that want clean output, not raw HTML.

ScraperAPI

About $0.001 per JS-rendered request on the Business plan ($299 for 3M API credits, where JS render costs 10 credits). Raw HTML output, no markdown conversion. Cheaper if you already have a parser. See the ScraperAPI breakdown for plan specifics.

Bright Data

About $0.0015 per request for Web Unlocker, $0.001 per request for Scraping Browser at volume. The most reliable on hard targets (LinkedIn, Amazon, sites with strong bot detection), but the API surface is heavier. The Bright Data overview covers pool types and pricing tiers.

Apify

About $0.0005-$0.002 per page depending on which Actor you use. Apify is a marketplace of pre-built scrapers, so you are paying for the Actor plus compute. Best when an existing Actor matches your target. See the Apify guide for compute unit pricing.

Summary: FireCrawl wins on output quality and developer experience under 200K pages. Bright Data wins on hard targets. ScraperAPI wins on raw cost if you have parsing in-house. Apify wins when there is already an Actor for your exact target site.

The honest take: if you are reading this to pick a tool for cold email enrichment, FireCrawl is the right default for the first 100K pages a month. Switch to Bright Data or a hybrid stack only when you hit specific blocked targets or cross 500K pages.

When FireCrawl is worth it for cold email enrichment

Cold email lives or dies on what you say in line 1 of the email. "Saw you just opened a Series B" lands. "Hi {first_name}, I saw your company does great work" gets filtered to spam. FireCrawl is the cheapest way to get the inputs for line 1 at scale.

Three enrichment patterns FireCrawl handles well

  1. About page summary. Scrape /about, pass to an LLM with a 200-token prompt, return a one-line "what they actually do" string. About 6 credits per company including extract. 10,000 companies = 60,000 credits = $50.
  2. Careers page intent signal. Scrape /careers or /jobs, look for specific role keywords (Head of RevOps, VP Sales, AE hiring). Hiring an AE is one of the strongest cold email signals there is. About 1-5 credits per company depending on whether you extract role data.
  3. Recent news or blog post. Use the /crawl endpoint scoped to /blog or /news, take the top 3 posts, summarize. Gives you a real reference point for line 1.

Compare this to paying for Clay credits, Apollo data, or ZoomInfo enrichment. FireCrawl is the raw material; tools like LeadMagic and Clay are the orchestration layer. Many teams use FireCrawl inside a Clay table as an HTTP API call, which is cheaper than buying Clay's premium enrichment credits for the same task. The Clay vs Bitscale vs Ocean.io comparison covers when to use orchestration tools instead of raw FireCrawl calls.

Alternatives to FireCrawl

If you want cheaper raw HTML

ScraperAPI and Bright Data are both cheaper per request if you do not need markdown or schema extract. The trade is you write more code. For high-volume operations where you have a parser already, this saves money fast.

If you want pre-built scrapers

Apify has Actors for LinkedIn company pages, Google Maps, Yelp, and most major review sites. If your target matches an existing Actor, skip building anything.

If you want a full enrichment platform

Clay, LeadMagic, and Ocean.io bundle scraping with waterfall enrichment from multiple data providers. More expensive per record, less code to write.

If you want self-hosted

FireCrawl is open source. You can self-host on a Hetzner box with your own proxy provider for around $200-$400 per month in infrastructure, which beats the Growth plan if you have engineering capacity. The catch is proxy management, browser maintenance, and the operational time.

If you only need a few pages

Just use a headless Playwright script with rotating proxies from Bright Data, IPRoyal, or Smartproxy. Below 10,000 pages a month, the API premium is not worth it.

How to make FireCrawl credits go further

Most teams waste 30-60% of their credit budget on avoidable mistakes. The tactical list:

  1. Cache aggressively. Company homepages do not change daily. Store scraped markdown in Postgres or S3 with a 14-day TTL. A 50,000-page workflow becomes a 5,000-page workflow on the second run.
  2. Use the /map endpoint before /crawl. Map costs 1 credit total and gives you the URL list. Then scrape only the URLs you actually need, not every page the crawler discovers.
  3. Skip JS rendering when you can. Most static marketing sites work fine without rendering. Test with rendering off first; only flip it on when output is broken. Saves 4x on credit cost.
  4. Do extract in your own LLM, not FireCrawl's. FireCrawl's extract endpoint is convenient but charges 5 credits per page. If you have an LLM pipeline already, scrape with 1 credit and run extract for $0.0001 per page on Gemini Flash or GPT-4o-mini.
  5. Use webhooks for large crawls. Polling for results burns rate limit budget. Webhook callbacks free up your concurrency for real scrapes.
  6. Batch by domain. Hitting 100 pages on one domain in sequence is fine. Hitting 100 different domains in parallel is fine. Hitting 100 pages on one domain in parallel from one IP gets you blocked. FireCrawl handles a lot of this internally, but batching helps the scheduler.
  7. Watch the schema extract token count. A 50-field schema on a long page can cost 5 credits but also 8,000 LLM tokens behind the scenes. Tight schemas with 3-5 fields are faster and cheaper.

Together these usually cut a Growth-tier bill back down to Standard.

From scraped data to actual replies

FireCrawl turns the open web into structured lead data. That is half the job. The other half is sending email from infrastructure that lands in the inbox, not the spam folder. Most teams build a beautiful enrichment pipeline, paste 5,000 cleaned leads into a sequencer running on cheap shared SMTP, and watch reply rates sit at 0.3%.

Puzzle Inbox provides real Google Workspace and Microsoft 365 mailboxes on dedicated tenants. Not SMTP relays, not shared servers, not the recycled domains that get burned in two weeks. Pre-Warmed inboxes ship on Puzzle's generic .info, .help, and .site domains so you can start sending in 24-72 hours, with delivery handled over WhatsApp or email. Standard inboxes ship on your own customer domain when you want the brand match. Everything connects via OAuth, no SMTP or IMAP credentials, which is what every major sequencer expects in 2026 anyway.

The pairing works like this: FireCrawl pulls 10,000 enriched company records per week at around $100 of credits. Puzzle Inbox delivers 50 dedicated mailboxes at predictable per-mailbox pricing. Your sequencer of choice rotates across the inboxes with realistic per-mailbox volume, and the cold email actually lands in the inbox of the prospect FireCrawl just enriched. See how it works and pricing for the full breakdown. Domain strategy details live in the cold email domain strategy guide.

Bottom line on FireCrawl pricing in 2026

FireCrawl is fairly priced for what it does. Hobby works for solo operators. Standard at $83 is the right plan for most cold email teams up to about 30,000 enriched accounts per month. Growth at $333 covers agencies and SaaS products into the low six figures of pages. Enterprise is where the negotiation matters and where alternatives become competitive.

The cheapest version of any FireCrawl bill is the one where you cache results, skip JS rendering when you can, and run schema extraction in your own LLM. Do those three things and a $333 Growth plan covers what a naive setup would push to $1,500.

Related Reading

Ready to start sending?

Puzzle Inbox provisions pre-warmed Google Workspace and Outlook 365 cold email inboxes ready to send within 24-72 hours. See the pricing page, the how-it-works walkthrough, or the our-process page for full details.

Discussions From the Community