Home / Web scraping APIs / Apify
Apify pricing
Apify has no public price for 100,000 JavaScript-rendered pages a month; what it does publish, and why that is not a bill, is set out below.
Checked Oct 9, 2026 on Apify's own pricing page
Your workloadType an exact volume, change the success rate or copy a link to this jobEdit
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 Apify bills you for
What you pay
Every Apify plan
| Plan | Billed monthly | Billed yearly, per month | Included | Past the allowance | Concurrent requests |
|---|---|---|---|---|---|
| Starter | $19.00 | $17.00saves 11% | $19 | move to a bigger plan | not published |
| Scale | $199.00 | $179.00saves 10% | $199 | move to a bigger plan | not published |
| Business | $999.00 | $899.00saves 10% | $999 | move to a bigger plan | not published |
Apify is also sold as one of the cloud browsers (200 browser hours a month: no public price).
About this price and its sources
How Apify turns prepaid platform spend into resource and Actor usage, what remains workload-specific, and who it suits.
How the bill builds up
- Base rateNot publishedNo matching published billing rule
- × JavaScript renderingNot publishedSee the stated assumption in the calculation
- × Premium proxyNot requiredNot part of this workload
- ÷ Success rate0.95Failure billing is not published; this is an assumption
- = per 1,000 pages keptTotal unknown
Credits and multipliers
JavaScript rendering
Billed failures
Success rate
Concurrency
Free tier
Renews monthly The bill at your volume
100,000 pages per month · No complete published bill
Read the chart as a table
| Volume | Bill | Offer |
|---|---|---|
| 10,000 | No public price | no self-serve plan |
| 25,000 | No public price | no self-serve plan |
| 50,000 | No public price | no self-serve plan |
| 100,000 | No public price | no self-serve plan |
| 250,000 | No public price | no self-serve plan |
| 500,000 | No public price | no self-serve plan |
| 1,000,000 | No public price | no self-serve plan |
Follow each billed unit
-
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
Failure billing is not published, so this assumes all 105,263 attempts are billed.
- ∅
Cash per month
No public price for this job
See the note above.
Bars share one linear scale across the 2 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.
Price changes
- Aug 31 to Sep 1, 2026: Starter: $29 → $19 a month (−34.5%).
Read daily from Apify's pricing page. Every confirmed change on every API, with a feed.
No public price. The vendor's published terms do not give a complete price for this job.
Published exact bills for comparable products
Same 100,000 JavaScript-rendered pages a month at a 95% success rate, ranked by what you would actually be billed. APIs without a full public price aren't ranked. Showing 6 of 16; see the rest.
What Apify does not publish
- Actor prices, RAM-hours, storage, transfer and proxy usage cannot be calculated from this page-count workload.
What Apify is
Apify is a cloud platform for running Actors, which are packaged programs for web scraping, browser automation, and data workflows. Teams can write their own Actors or use offerings in Apify Store. This makes it materially different from Bright Data Web Scraper API, Zyte API, and ScrapingBee: those nearby choices lead with managed endpoints or predefined extraction services, while Apify leads with a runtime, storage, scheduling, proxies, and a marketplace of independently priced Actors. It is for developers and data teams that want a place to operate scraping jobs, not just a URL-in, response-out API. Sources: Apify pricing, Apify Store, Bright Data Web Scraper pricing, Zyte pricing, and ScrapingBee pricing, checked Jul 26, 2026.
How billing works
A paid plan provides prepaid platform spend rather than one universal request allowance. An Actor run can consume compute based on allocated memory and runtime, plus storage, data transfer, proxy traffic, and any Actor-specific event charges. Rented Actors may also carry their own charges. Retries create additional runs and therefore can consume additional resources. The common buying mistake is to treat a compute unit as the price of a scraped page. A compute unit measures computing resources, while the cost per useful record depends on the Actor, memory allocation, runtime, retries, transfer, proxy use, and event schedule. Sources: Apify pricing and Apify usage and resources documentation, checked Jul 26, 2026.
What Apify does not publish as one answer
- A platform-wide price per page, request, or delivered record, because Actors use different resources and may define different paid events. Sources reviewed: Apify pricing and Apify Store, checked Jul 26, 2026.
- One multiplier that converts an Actor’s advertised output into total platform cost (Apify usage and resources documentation, Jul 26, 2026).
- Effective monthly figures for annual billing in the public plan table, although an annual discount is advertised (Apify pricing, Jul 26, 2026).
- A universal success-only rule. Resources are consumed while a run executes, including runs that fail (Apify usage and resources documentation, Jul 26, 2026).
Who it suits
Apify suits teams that need scheduled jobs, reusable code, datasets, proxies, and a choice between building and renting Actors. It is especially reasonable when engineers can test the exact Actor and record its real resource profile before committing volume. It is less suitable for procurement that needs one public success-only rate for a standardized request, or for a buyer unwilling to inspect Actor-specific charges. The reason is structural: Apify sells a programmable platform, so cost predictability comes from workload testing and configuration control rather than from one global unit. Sources: Apify pricing, Apify Store, and Apify usage documentation, checked Jul 26, 2026.
Apify head to head
Both bills for the same job, and the volume where the cheaper one changes.