ApiFlash alternative

An ApiFlash alternative that never bills a failed render

ApiFlash competes on being simple and inexpensive, and at some volumes it is cheaper than we are. That is a fact about the tables, not an argument we can talk around — so it is on this page rather than in a footnote.

Stay where you are if

Sticker price decides it. At 1,000 and at 10,000 screenshots their published table is the lower one, as of the date on the card below.

Move here if

Failed renders and repeat captures are eating that difference. Neither is billable here, and the error codes stay stable across releases.

What moving looks like: Change the base URL and key, map the options — the names and defaults are ours — then price your own mix of cache hits and failures against both tables.

apiflash alternative · request and resultPAGECAPTURE / 01
The same job, in our contract
curl -G https://api.pagecapture.dev/v1/take \
  -H "X-Access-Key: $PAGECAPTURE_KEY" \
  --data-urlencode "url=https://example.com" \
  -d "format=jpeg" \
  -d "image_quality=85" \
  -d "block_cookie_banners=true" \
  -o pagecapture.jpg
Capture result
succeeded
https://example.com
Noma
Shop now
NEW COLLECTION

Objects for slower mornings.

Thoughtful essentials, made in small batches from natural materials.

Explore the collection
No. 01 · Hinoki
PLANT-BASEDMADE IN SMALL BATCHESREFILLABLE
Artifact
PNG · 1440×900
Billing
1 credit
Engine
stable

Failures are never billed here

Check how each vendor counts a failed render before comparing headline tiers — it moves the effective price more than the tier does. Our answer is in the error catalog: no code is billable, and the tests assert it.

Cache is scoped to your organization

Repeat captures of the same render spec are free and never leak between accounts. Pages captured on a schedule get cheaper.

A stable error contract

The error_code is the contract and the HTTP status derives from it. Client behaviour written against the codes survives our releases.

Async delivery without a queue of your own

Submit, receive a request id, get a signed webhook. Redelivery is safe because the ledger constraint makes it safe, not because you deduplicate.

What this costs here

Priced on successful captures that miss cache

Every number in this table is computed from the published plans — failures and organization-scoped cache hits are removed before the plan is chosen, because they are not billable.

ScenarioBillable successesSmallest included planPublished monthly price
10,000 screenshots per month8,820Growth$47.00

Assumes 10% cache hits and 2% failures. Change either assumption and the billable count changes with it — that is the point of charging for success.

What these vendors publish

ApiFlash, in their own numbers

These figures are quoted from each vendor's own pricing page, with the date we last checked it. They are not converted to our billing unit, because they do not measure the same thing.

ApiFlash

Simplicity and low cost on top of AWS Lambda.

Free tier
100 screenshots per month
Entry plan
US$ 7 / 1,000 screenshots per month
10,000 screenshots
US$ 35 per month
100,000 screenshots
US$ 180 per month

Published by the vendor, checked 2026-08-14.

apiflash.com

ApiFlash is trademarked by their respective owners and mentioned only to describe the comparison people are searching for. No affiliation is claimed.

Questions this raises

Is PageCapture affiliated with ApiFlash?

No. PageCapture is an independent product with its own implementation. ApiFlash is a trademark of its owner and is mentioned only to describe the comparison people are searching for.

Is PageCapture cheaper than ApiFlash?

Not at the volumes their table publishes: at one thousand and at ten thousand screenshots, ApiFlash is the lower sticker price as of the date on the card above. Read both tables and price your own mix of cache hits and failures — that is the comparison that decides it, not a headline.

Is it a drop-in replacement?

No. The concepts are familiar but the parameter names and defaults are ours. Map the contract, run both providers against your own fixtures and compare artifacts before moving traffic.

What is missing today?

Billing first, since price is why you are on this page: checkout is not wired to a merchant of record yet, so invoicing and tax handling are not what a finance team expects. On the render side there is no managed proxy pool behind ip_country_code and no GPU pool behind request_gpu_rendering. If your migration depends on any of those, this is not the moment to move.