Apify Website Screenshot Actor Pricing in India: Estimate Monthly Costs

Short answer: Apify’s Website Screenshot Generator Actor is free to use, but Apify platform usage is billed separately. There is no verified universal monthly price in Indian rupees: your total depends on your plan, the Actor’s actual resource use, any applicable extra usage, currency conversion, and taxes or government charges. Estimate your bill by running a representative batch, reading its actual cost in Apify Billing, and scaling that observed cost to your expected monthly volume.

The Actor stores screenshot files in a Key-value Store and writes their links to a dataset. Its repository says the Actor is free and that users pay for Apify platform usage. Check the [official Actor repository](https://github.com/apify-projects/store-screenshot-url) and the [Apify pricing page](https://apify.com/pricing) for current details.

What you may pay for

Apify platform usage can include several components. A free Actor does not mean every run has zero cost.

Cost component	What it means for an estimate
Compute units (CUs)	Actor run resources, based on allocated memory and run duration. Browser rendering can consume resources while pages load and screenshots are produced.
Storage operations	Operations associated with storing screenshots and writing output records may contribute to usage.
Data transfer	Moving page data or screenshot files can incur usage depending on the plan and current rates.
Proxy usage	Proxy costs may apply if the Actor run uses paid proxy services.
Actor-specific charge	Store Actors can use different pricing models. Confirm whether the current Actor page lists a per-event or other charge and whether platform usage is included.

Apify defines a CU as a unit for measuring resources consumed by Actor runs and builds. Its documentation gives an example of 1024 MB allocated for one hour consuming 1 CU. That explains the unit; it does not tell you how many CUs one screenshot will use. The [CU and Actor usage documentation](https://docs.apify.com/platform/actors/running/usage-and-resources) describes the calculation and where to inspect a run’s usage.

How to estimate your monthly cost

Check the exact Actor offer. Open the Website Screenshot Generator page in Apify Store. Review its current pricing model and any event charge. The repository describes the Actor as free, but confirm the live offer before estimating.
Choose a representative sample. Run a small batch using the settings and page mix you expect in production. Include the types of pages that affect your workload, such as heavier JavaScript pages, and use the same scrolling and delay settings.
Read the actual run usage. Inspect the run details and Billing usage. Record the total cost and usage, including compute, storage, transfer, proxy, and any Actor-specific charge that applies.
Count successful screenshots. Divide the measured cost by the number of successful screenshots in the sample. Keep failed or incomplete captures visible in your notes so you understand the workload and do not mistake attempts for delivered screenshots.
Scale to your monthly volume. Multiply the observed cost per successful screenshot by your expected number of successful screenshots per month. Treat this as an estimate, not a guaranteed quote.
Check plan rates and invoice details. In Apify Console, open Billing and review the Pricing tab for your account’s current rates. Check your subscription, usage history, invoice currency, and any applicable taxes or government charges.

Estimated monthly platform usage = (measured batch cost ÷ successful screenshots in batch) × expected monthly successful screenshots

This calculation is useful when your workload resembles the sample. It can mislead if monthly pages differ substantially in size, run duration, concurrency, capture settings, or proxy use. Run a separate representative sample for a materially different workload.

Worked example without an invented India price

Suppose your own Billing page shows that a representative batch cost B in your account’s billing currency and produced S successful screenshots. If you expect M successful screenshots in a month, the observed estimate is (B ÷ S) × M, before any charges or adjustments that differ from the sample.

For example, enter the actual batch cost and counts from your run into this small calculator. It deliberately accepts the account’s observed cost rather than assuming a price per screenshot:

batch_cost = float(input("Measured batch cost in your billing currency: "))
successful_shots = int(input("Successful screenshots in that batch: "))
monthly_shots = int(input("Expected successful screenshots per month: "))
if successful_shots <= 0:
    raise ValueError("The batch must contain at least one successful screenshot")
print("Estimated monthly platform usage:", batch_cost / successful_shots * monthly_shots)

Python’s calculation is currency-neutral. It does not convert USD to INR or determine Indian tax treatment. Use the currency and charges shown in your own billing account or invoice.

Plan rates and India-specific limits

Apify documentation accessed October 3, 2026 lists example CU rates of $0.20 per CU on Starter and $0.16 per CU on Scale. These are plan examples, not a monthly screenshot price or a quote for an individual account. CU price alone cannot establish cost per screenshot because the run’s resource consumption and other platform charges matter.

No source reviewed establishes a universal India-specific INR total or a particular tax percentage. Do not convert a documentation example into a guaranteed rupee amount. Your account’s current Billing Pricing tab and invoice are the right references for its applicable rates, currency, and charges. Apify’s [Billing documentation](https://docs.apify.com/platform/account/billing) describes the Pricing, usage, and invoice views.

Improve estimate quality and control spend

Use a batch large enough to reflect your normal work, but small enough to review before scaling.
Include representative page types and the same screenshot settings, scrolling, and delays you expect to use.
Record successful output count as well as total run cost. Re-run the sample if the workload changes materially.
Review current plan rates and usage limits in Billing before increasing volume. Apify’s Billing area includes usage and limit controls; understand the account’s overage settings before relying on a monthly estimate.
Compare Store Actor offers by pricing model and whether platform usage is included. Compare them using the same workload and measured results.

cURL, Python, and Node.js: automate the estimate

The examples below calculate a projection from values you read from an actual Apify run. They do not start an Actor or presume its API identifier. Enter costs in one consistent currency and use successful screenshot counts.

cURL

curl -sS -G 'https://example.invalid/estimate' \
  --data-urlencode 'batch_cost=REPLACE_WITH_MEASURED_COST' \
  --data-urlencode 'successful_shots=REPLACE_WITH_SUCCESS_COUNT' \
  --data-urlencode 'monthly_shots=REPLACE_WITH_MONTHLY_COUNT'

cURL alone cannot perform a local calculation without a calculator endpoint. Rather than calling a fabricated service, use this portable shell calculation with values from your run:

batch_cost=12
successful_shots=400
monthly_shots=3000
awk -v cost="$batch_cost" -v shots="$successful_shots" -v monthly="$monthly_shots" \
  'BEGIN { if (shots <= 0) { print "successful_shots must be positive" > "/dev/stderr"; exit 1 } printf "Estimated monthly usage: %.6f\n", cost / shots * monthly }'

Replace the sample inputs with your own observed values; the numbers shown are only illustrative calculator inputs, not Apify pricing or a typical result.

Python

batch_cost = 12.0  # replace with the cost shown for your measured batch
successful_shots = 400
monthly_shots = 3000
if successful_shots <= 0:
    raise ValueError("successful_shots must be positive")
estimate = batch_cost / successful_shots * monthly_shots
print(f"Estimated monthly platform usage: {estimate:.6f} (same currency as batch_cost)")

Node.js

const batchCost = 12.0; // replace with the cost shown for your measured batch
const successfulShots = 400;
const monthlyShots = 3000;
if (!Number.isFinite(batchCost) || successfulShots <= 0 || monthlyShots < 0) {
  throw new Error('Enter a finite cost, positive success count, and non-negative monthly count');
}
const estimate = (batchCost / successfulShots) * monthlyShots;
console.log(`Estimated monthly platform usage: ${estimate.toFixed(6)} (same currency as batchCost)`);

The example inputs are placeholders for demonstrating arithmetic. They are not claims about how much Apify charges or how many screenshots a run produces.

Troubleshooting an estimate

Symptom	Likely cause	What to do
The Actor says free, but Billing shows a charge.	Actor price and platform usage are separate; a Store Actor may also have its own pricing model.	Inspect the exact Actor pricing details, run usage, and Billing breakdown.
Your measured average changes between runs.	Page mix, render time, memory, concurrency, proxies, or settings differ.	Compare like-for-like batches and keep separate estimates for distinct workloads.
The estimate is zero or impossible.	The sample has no successful screenshots, or cost/count inputs were entered in the wrong units.	Use a nonempty successful batch and enter the cost in one consistent billing currency.
Your projected bill differs from the invoice.	The projection may omit storage, transfer, proxies, Actor charges, plan credits, overages, currency conversion, or taxes.	Use invoice and historical usage as the final record; update the model with all applicable components.
The Console rate differs from a published example.	Rates depend on plan and may change over time.	Use the current Pricing tab for your account rather than relying on an older documentation example.

Performance, reliability, and cost considerations

Browser-based screenshot runs consume resources while the browser opens pages, waits for content, and captures output. Apify’s usage documentation notes that browser work is more resource-intensive than plain HTTP work and that heavier pages can use more resources. Batch size and run frequency also affect resource use. Measure the real Actor workload rather than inferring a per-image rate from CU price.

For reliable budgeting, keep run settings stable, retain the sample’s run details, and refresh the estimate when page mix or volume changes. A sample-based projection is an operational planning aid; the account’s actual usage and invoice remain authoritative.

Or skip the browser setup

For a direct screenshot API, [ScreenshotNeo](https://screenshotneo.com) returns a screenshot or PDF from one GET request. The [API documentation](https://screenshotneo.com/docs/) covers its options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Cookie banners, newsletter popups, and chat widgets are removed before capture; each cleanup step can be turned off.
Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; response headers report the page verdict and billing status.
An MCP server lets AI agents, including Claude and Cursor, use screenshot and page information tools.
1,000 screenshots per month are free with no card. Paid plans start at $5 for 3,000 screenshots.

FAQ

Is the Website Screenshot Generator Actor free?

The official repository says the Actor is free to use, while Apify platform usage is billed separately. Check the live Store listing for its current pricing details.

How much does Apify charge per screenshot?

The sources do not establish a fixed per-screenshot rate. Measure your own representative batch and divide its applicable cost by successful screenshots.

Can I get a definite monthly estimate in Indian rupees?

Only your current account rates, measured workload, invoice currency, and applicable taxes can support a personalized INR estimate. The published examples do not establish a universal India price.

Where do I confirm the final amount?

Review the account’s Billing usage, Pricing, and invoice. Apify identifies invoices as the source for previous charges.