Screenshot API pricing: credits versus monthly quotas

Screenshot API pricing comes in two shapes, and the difference matters more than the headline rate. Most providers sell a monthly subscription with a fixed quota. A smaller number sell credits you buy once and spend whenever. Which one is cheaper depends entirely on how your workload behaves, and screenshot workloads behave in a way that suits one model far better than the other.

Screenshot workloads are bursty

Very few teams capture a steady number of screenshots every day. The real pattern is spiky: ten thousand captures during a migration, an audit or a catalogue import, then almost nothing for two months. A directory refreshes its thumbnails on a schedule and then sits idle. An agency reports at month end. A test suite fires on deploys, which cluster.

A subscription charges the same amount in the busy month and the quiet one, and any quota you did not use disappears at the reset date. You are buying capacity, not usage.

What a quota really costs

The number on the pricing page is the price per screenshot only if you use every single one. Work out the effective rate instead: what you paid, divided by what you actually captured.

Take a plan at $79 a month for 10,000 screenshots. That is $7.90 per 1,000 at full usage. Use 3,000 in a given month and you paid $26.33 per 1,000 that month. Skip a month entirely and you paid $79 for nothing. Over a year of realistic, uneven usage, most teams land at two to four times the advertised rate.

• Divide the monthly fee by the screenshots you genuinely expect, not the quota ceiling
• Count the quiet months, because you pay for those too
• Check whether failed captures consume quota. On many providers they do
• Check the overage rate, which is usually well above the in-plan rate
• Check which features are gated behind a higher tier, because that decides your real entry price

How credits work instead

With pay as you go credits you buy a pack once. One credit is one successful screenshot. Credits sit in your account until you spend them, with no reset date and no expiry, so the effective rate is exactly the rate you paid no matter whether you burn through the pack in a weekend or over two years.

A quiet month costs nothing. A busy month costs what it costs. There is no plan to choose, so no feature is locked behind a tier you did not need.

Compare on a real workload, not the headline

The honest comparison is total cost over a year of your actual usage. Sketch out twelve months, put your real expected volume in each, and price both models against it.

For a workload of roughly 10,000 screenshots spread unevenly across a year, a $79 monthly plan costs $948 and deletes most of what you paid for. The same 10,000 credits bought once cost $60 and are still there in month twelve.

What ScreenshotBee charges

Credits, on a volume ladder, with everything included at every level. The rate falls as the pack gets bigger:

• 1,000 screenshots for $9, which is $9.00 per 1,000
• 10,000 screenshots for $60, which is $6.00 per 1,000
• 50,000 screenshots for $225, which is $4.50 per 1,000
• 250,000 screenshots for $875, which is $3.50 per 1,000

Failed captures are never charged, credits from every pack pool into one balance, and full page capture, device emulation, HTML rendering, element captures and scheduling all work on every credit. There is no tier that unlocks the good parts.

Try it before you pay

Every new account starts with 100 free credits and no card. That is enough to wire the API into your stack, run your real pages through it and see what the output actually looks like before any money changes hands. If the captures are not right for you, you have spent nothing.

To spend them, start with the website screenshot API guide, or convert HTML to an image if you are rendering your own templates.