Apify Pricing Explained: Plans, Actor Fees and Cost Examples

A practical guide to Apify’s plans and billing, with worked examples, documented user experiences and checks to make before scaling a workflow.

perfectpoint
11–16 minutes
Apify Pricing cover with a $19 plan and credit receipt and Actor and usage labels.

Apify pricing looks simple until the first invoice. The bill depends on the plan you pay for, the usage that plan includes, and the way the specific Actor you run charges. A small job can live on the Free plan indefinitely, and a paid subscription doesn’t buy unlimited scraping. One user on r/apify asked whether running an Actor means paying for a subscription on top, because they only wanted 8–10 profiles a day. It’s the right question, and this guide answers it without counting anything twice.

What Do Apify’s Pricing Plans Include?

Four plans cover almost everyone. Free is $0 and gives you $5 of usage. Starter is $19 a month with $19 of usage, Scale is $199 with $199, and Business is $999 with $999. Compute units cost $0.20 on Free and Starter, $0.16 on Scale and $0.13 on Business, all per Apify’s official pricing page. Those figures were checked on November 9, 2026. Older reviews still quote a $29 Starter plan, so ignore them.

Think of Free as a lab. There’s no card, you get most of the platform, and there’s a hard stop at $5, which is exactly what you want while you find out what a job costs. Starter is where freelancers and small teams usually land, because it’s the first plan that lets you keep running past the included amount and settle the difference later. Scale and Business are for workloads that already burn serious volume: the compute rate drops and the Store discount tier improves. Custom plans exist for companies that need negotiated terms. Anyone publishing their own Actors lives on a separate Creator plan. That’s a different business from a buyer’s bill, and it has its own breakdown in How Much Can You Earn Selling Apify Actors?

Keep two kinds of capacity apart. A plan caps the total memory all your running Actors can hold at once. Each individual run also gets its own memory allocation, and that’s the setting that moves the cost of the run. Annual billing changes how you pay, and the pricing page marks it with a 10% reduction. Read the checkout screen instead of dividing a yearly figure by twelve.

A bigger plan isn’t a discount. Here’s the arithmetic on the published rates, and the conclusion is my own judgment. Take a job that burns 100 compute units a month. On Starter that’s $20 of compute, so the month costs about $20 in total. On Scale the same job costs $16 of compute but $199 flat, and the credit you didn’t use evaporates at the end of the cycle. A lower rate pays for itself only when the volume is already there.

A $19 monthly payment provides a $19 usage allowance that a workflow consumes.
Included usage is part of the plan payment, not an automatic second charge.

How Credits, Pay as You Go and Overages Work

Money moves in a fixed order, and once you see it most of the confusion goes away. You pay the plan fee. Your usage drains the included credit, which can be spent in Apify Store or on your own Actors. Whatever exceeds the credit becomes overage, provided your account is allowed to go there. The credit isn’t a second charge stacked on the fee. A $19 plan with $19 of credit is $19 of commitment, not $38.

Credit doesn’t carry over. It expires when the billing cycle ends, so a quiet month wastes it. On Free the story stops at $5: you wait for the next cycle, and Apify’s help center says that limit can’t be raised. On paid plans, a limit in your billing settings decides how far overage can run. It starts equal to your prepaid amount, so a fresh paid account can’t overspend until you raise the limit on purpose. Each plan has a ceiling, and the help article on platform limits lists $100 for Starter at the time of writing.

Dates trip people up too. Apify’s billing guide is vendor documentation, not an independent review. It says Current period follows your billing cycle, while Historical usage is organized by calendar month and shows usage before later discounts. The two screens can disagree for perfectly innocent reasons. Invoices are the source of truth for what you were charged, and overage can be invoiced before the cycle ends.

Here’s a working model for a monthly paid plan. The cycle charge before tax is the plan payment, plus eligible usage above the included credit, plus anything billed separately. The first term is fixed. The second stays at zero until you pass the credit. The third covers items that sit outside it. The model breaks down for Free, annual prepayment, proration, coupons and negotiated contracts.

A paid-plan example uses $19 of credit and $5 of permitted overage for a $24 cycle total before tax.
In this hypothetical monthly example, $24 of eligible usage produces $5 of overage above the $19 credit.

How Actor Pricing Changes the Calculation

Every Actor in Apify Store bills in one of two ways, and the Actor’s Pricing tab tells you which. Your plan and credit stay the same. What changes is the thing being counted.

Pay per event

The developer defines what’s chargeable: a returned result, a start, a file upload. You pay the listed price for each event. Most event-priced Actors fold platform usage into that price, so adding compute on top would charge you twice on paper. Some Actors bill usage separately, and the name never tells you which kind you’re looking at. You can also set a maximum charge when you start a run. The docs say the Actor winds down at that limit and you’re never billed above it.

Pay per usage

The developer takes nothing extra. You pay for what the run consumes: compute units, storage operations, data transfer, and residential or SERP proxies where they’re used. Apify’s own docs concede that this model is easy to read after a run and hard to predict before one, and they recommend a small test on limited scope.

When both apply

Some Actors charge an event price and platform usage together, and the pricing page shows that shape too. Store discounts exist (Bronze, Silver and Gold, depending on your plan), but Actor owners decide whether to offer them. A Gold plan doesn’t give you a Gold price on an Actor that opted out.

Keep three quantities apart: a page visited, an item returned, and a record you can actually use. Per-result pricing bills the second. Your real cost per usable record depends on the third.

Be skeptical of “from” prices. On November 9 the pricing page’s sample card for Google Trends Scraper showed $1 per 1,000 results plus platform usage on Starter, while the Actor’s own page said “from $3.00 / 1,000 results” in its header. That’s two numbers for one Actor on the same day, and neither tells you what your run costs until you read the Pricing tab.

The Actor in the next section is fictional: events only, resources included, $2 per 1,000 items. It’s there to make the arithmetic visible, not as a quote.

A decision diagram separates event pricing with included or separate resources from usage pricing.
Read the Actor’s pricing model before adding resource charges.

Three Worked Apify Cost Examples

Hypothetical calculations, not measured runs or customer invoices. All three assume a monthly paid plan and leave out taxes, currency conversion, add-ons, promotions, proration and outside tools.

Example 1: below the included credit. Starter costs $19 and includes $19 of credit. The fictional Actor charges $2 per 1,000 returned items, resources included. A run that returns 4,000 items costs 4 × $2 = $8. You still pay $19, and the remaining $11 of credit expires unused. The total isn’t $27, even though adding the two figures is tempting.

Example 2: above the included credit. Same plan, same Actor, 12,000 items: 12 × $2 = $24. If your configured limit allows it, you pay $19 plus $5 of overage, so $24 before tax. It isn’t $43. On Free the same job simply stops at $5, which at this rate covers 2,500 items.

Hypothetical event-only workloads cost $8 or $24 in usage and lead to $19 or $24 in total monthly payment.
Consumption below the credit does not reduce the monthly plan payment; permitted consumption above it creates overage.

Example 3: a usage-priced workload. Say 120 runs in a 30-day month, each given 2 GB of memory for half an hour. That’s 2 GB × 0.5 hours = 1 compute unit per run, 120 in total. At Starter’s current $0.20 per unit, compute comes to $24. Add 0.5 GB of residential proxy traffic at $8 per GB, which is $4, and $0.50 for storage operations and data transfer. Eligible usage is $24 + $4 + $0.50 = $28.50. The $19 credit absorbs part of it and leaves $9.50 of overage, so the cycle total is $19 + $9.50 = $28.50. No event fee applies, because this Actor bills by usage.

Examples 2 and 3 both cross the credit and land on a total equal to usage. That happens because the plan fee and the credit match, and it makes a handy sanity check on your own numbers.

Treat the consumption in Example 3 as assumptions. A compute unit measures resource use, not a fixed number of pages, and nothing here promises that a 2 GB, thirty-minute run will do any particular amount of work.

What Makes the Same Workflow Cost More?

Compute is allocated memory multiplied by time, so anything that makes a run longer or heavier raises the count. Apify’s documentation ranks the usual culprits. Launching a full browser costs far more than reading plain HTML, and Cheerio-style crawling is described as up to 20 times faster. Lots of short runs pay the start-up penalty again and again, which a larger batch avoids. Heavy pages can take up to three times the resources of an average one. On usage-priced Actors, retries after failed requests add cost, and proxy traffic, storage operations and data transfer are billed separately, including dataset reads and writes after a run ends. Squeezing memory down isn’t a free saving either. A starved run that crawls or fails can cost more than a well-sized one.

Check the schedule next. With everything else equal, an hourly job plans 24 times as many runs as a daily one. That doesn’t mean a 24-times invoice, since the runs may be smaller, but a refresh rate nobody needs is the first thing I’d cut when a bill looks wrong.

Quality changes the arithmetic too. Say a hypothetical job consumes $8 of eligible usage and, after you throw out duplicates and junk, leaves 3,200 usable records. $8 ÷ 3,200 × 1,000 comes to $2.50 per 1,000 usable records. If you load the whole $19 Starter payment onto that one job, $19 ÷ 3,200 × 1,000 is about $5.94. Both answers are right, for different questions. The first asks what the work consumed, and the second asks what the month cost you. Neither is a marketplace price, and the 3,200 is made up.

A user on r/automation described a useful YouTube-data integration that also produced irrelevant or old results, unexpected fetching and budget trouble. It’s one unverified account with no Actor name, settings or invoice, so nobody can diagnose it from the post. My inference is about method only: check output quality and spending controls together, because a run can be cheap and still useless.

What Real Users Reveal About Cost and Value

Both success stories below were published by Apify, and they describe very different decisions.

Diligent AI runs about 40,000 Actor runs a month, according to Apify’s case study. Cofounder Ahmed Gaber reports a 30% cost reduction after moving from a SERP API to Apify’s Google Search Scraper. That’s a vendor-published comparison against one alternative, with no invoice to inspect. His build-versus-buy reasoning carries more weight: a custom Facebook scraper hovered near 80% accuracy and kept needing maintenance, and he says engineering time mattered more to the company than revenue.

Sponja’s Roee Tsur, in another Apify-published account, reports under $20 of Actor spend for a three-Actor pipeline. It surfaced 897 US companies advertising webinars and 244 likely webinar owners. The same piece describes wrong-company matches, caught by flagging any small company that showed more “owners” than employees.

Gaber is weighing a recurring production dependency, where reliability and engineering hours dominate. Tsur is bounding a single prospecting task and checking results before trusting them. His under-$20 figure covers Actor spend only, not his time, outreach or any revenue, and it reflects June 2026 prices. If you’re turning this into a client service, labor and delivery sit on top of the platform bill, as our piece on selling scraping services shows. Two selected stories don’t settle what the skeptical user above experienced. They do suggest that managed convenience has real value, provided you decide in advance what counts as acceptable data and where the spending stops.

Returned items are reviewed into usable records and exceptions before cost per usable record is calculated.
The relevant cost depends on usable output and on which expenses you allocate to the job.

Estimate Your Own Bill Before Scaling

Estimating a bill is a sequence of small checks. This guide gives you a method, not a calculator, and you can repeat it for any workflow.

  1. Decide what you need: which fields, how many records, how often.
  2. Open the exact Actor’s Pricing tab. Write down the billable unit and whether platform usage is included.
  3. Set controls, and know what each one guarantees. A per-run maximum charge on an event-priced Actor, an Actor’s own item-count input and your account’s usage limit are three separate things. Apify’s limits article calls platform limits estimates, with actual spending able to deviate by up to 10%, so I wouldn’t treat any of them as an exact universal stop.
  4. If you choose to, run a small bounded sample, then read the run’s usage and judge the output. I haven’t run this test for the article, though Apify recommends it.
  5. Project the same workload at your real volume, then again at a heavier scenario. Keep the assumptions visible. A buffer is your own margin, not something Apify guarantees.
  6. Compare eligible consumption with your credit, check other charges, and reconcile against cycle dates and invoices.
A bounded sample is reviewed for usage and quality, then used to revise scope or estimate a larger workload.
Check both consumption and usable output before increasing the workload.

Plan choice follows from the measurement. Free suits a test or a very light job. Starter fits when measured usage sits near or above $19 and you want runs to continue past the credit. Scale and Business earn their fees when usage fills the credit and the lower compute rate or higher account capacity matters. To lower the bill, use plain HTTP instead of a browser when the site allows it, favor larger batches over many tiny runs, and refresh no more often than you need. Self-hosting is a different allocation, trading platform fees for engineering time, servers and proxies. It isn’t free just because no invoice arrives.

Before you raise the volume, open the Actor’s Pricing tab and write down its billable unit.

Apify Pricing FAQ

Do I have to subscribe to use an Actor? No. Free needs no card and includes $5 of usage, though an individual Actor can have its own conditions, so read its Pricing tab. Once the $5 is gone, Free is blocked until the next cycle.

Is Apify API usage a separate subscription? Check the Actor and service you’re calling. A local script that calls a cloud Actor still runs it on Apify, so the same credit, Actor pricing and limits apply.

Can I buy unlimited pay as you go usage without a plan? Not as the pricing page describes it. Usage draws on a plan’s prepaid amount, and paid overage stops at the limit you set, within the plan’s maximum. Enterprise is a custom arrangement.

Do unused credits roll over? No. They expire at the end of the billing cycle.

Can a failed run still incur charges? It can. Resources may be consumed or events may occur before a failure, and billing depends on the model and the Actor. Check the run’s cost and the Pricing tab. If a charge looks wrong, Apify’s docs point you to the Actor’s Issues tab or support.

What happens if I upgrade, cancel or hit my limit? Upgrading is prorated, and you can downgrade or cancel in billing. A cancelled plan runs to the end of the cycle, and usage you already incurred can still be charged. At your limit, raise it within the plan’s ceiling or move up a plan. On Free, wait for the next cycle.

WRITTEN BY

perfectpoint

Leave a Reply

TAGS

Keep the thread going.