Screenshot credits or a subscription? Choose based on your workload
Erik LindqvistSep 26, 20266 min read
Find out how easy it is to capture and share pixel-perfect screenshots at scale using Allscreenshots. Sign up for a free account and start integrating your first screenshot API call today.
Not every screenshot workload happens neatly once a month.
A product may need 2,000 thumbnails during an import and almost nothing after that. A team might archive a customer portal at the end of each quarter. An agency can have a busy launch week followed by six quiet weeks. In those cases, paying for capacity that resets every month can feel like the wrong shape of purchase.
That is why Allscreenshots offers two ways to pay: a recurring subscription for predictable, ongoing workloads, and one-time screenshot credits for work that is occasional, seasonal, or difficult to forecast.
Neither option is universally better. The useful question is: does your screenshot usage follow the calendar?
What screenshot credits are
Screenshot credits are a fixed balance purchased once. They do not start a subscription, they do not renew automatically, and they do not expire. A completed screenshot uses one credit.
The current credit packs are:
Credits
One-time price
Price per screenshot
1,000
$5
$0.005
5,000
$20
$0.004
10,000
$35
$0.0035
Every new account also starts with 100 screenshot credits, so you can test a real workflow before deciding how you want to pay for it.
Purchased credits work across the same capture surfaces: the API, Playground, async jobs, bulk captures, compositions, and schedules. If you also have a paid plan, its monthly allowance is used first. Your purchased balance stays available and takes over when that allowance runs out.
Credits add screenshot capacity. They do not change your plan's rate limits, concurrency, support level, or access to plan-specific features such as webhooks and geolocation.
When credits are the better fit
Your workload is irregular
Credits work well when usage arrives in batches instead of a steady stream.
Suppose you refresh a directory of 1,500 company thumbnails every quarter. A monthly allowance would be mostly unused for two months out of three. A 5,000-credit pack can cover three full refreshes, with the remaining credits still there when the next job arrives.
The same pattern appears in:
Data imports and content migrations
Launch-day QA and campaign reviews
Quarterly audit evidence
Occasional competitor or pricing research
Rebuilding a website thumbnail cache
Client projects with a defined number of deliverables
You buy capacity for the project, not for the time between projects.
You want a fixed project cost
A one-time pack is easy to attach to a project budget. If a migration needs roughly 8,000 captures, a 10,000-credit pack gives the project a clear maximum screenshot cost and leaves a useful buffer for retries or late additions.
There is no need to remember to cancel a temporary subscription when the work is finished. The unused balance remains available for the next project.
You need a safety buffer
Credits are also useful alongside a subscription. A monthly plan can cover the normal workload, while a credit balance handles an unusual traffic spike, a larger-than-normal batch, or a schedule that runs more often during a launch.
This is often more practical than upgrading for one busy month and downgrading again afterward. The credits wait in the account until the monthly allowance is exhausted, then keep captures running.
You are still learning your usage pattern
Early products rarely know their long-term screenshot volume. Buying a small pack lets you run a real workload and observe the result before choosing a recurring plan.
That gives you better information than estimating from a prototype: how often users trigger captures, how many URLs appear in a typical batch, and whether schedules make the workload predictable over time.
When a subscription is the better fit
A subscription is usually better when screenshots are part of a product's normal operation rather than a distinct project.
If you generate customer previews every day, run visual checks on every deployment, or monitor hundreds of pages on a schedule, a monthly allowance is easier to forecast. The allowance renews automatically, so nobody has to watch a finite balance or purchase another pack.
Paid plans also include operational benefits that credits alone do not provide:
Higher request rate limits
More concurrent captures
Successful-capture-only billing
Webhook and email delivery
Higher-tier features such as geolocation, direct storage uploads, and stealth mode
Priority support on qualifying plans
The subscription is paying for more than a bucket of screenshots. It is also paying for throughput, automation, and the service level around a production workload.
As a simple example, a product that reliably generates 2,000 screenshots every month is usually better served by the Starter plan than by repeatedly buying packs. The workload is predictable, the allowance renews, and the higher limits help those screenshots finish sooner.
A quick comparison
Choose credits when…
Choose a subscription when…
Usage is occasional or seasonal
Usage repeats every month
You have a finite batch or project
Captures are part of the product's normal operation
Unused capacity should remain available
You want capacity to renew automatically
You want a one-time purchase
You need higher throughput or paid-plan features
You need overflow for an unusually busy month
You need predictable production capacity
The middle ground is often the best answer: use a subscription for the baseline and keep credits as non-expiring overflow.
Credits are now easier to find
We recently updated the dashboard to make this choice clearer.
The Overview page now shows your screenshot-credit balance with a direct Get more credits link. On the Billing page, Subscription plans and Credit packs are separate options, so buying additional screenshots no longer looks like it requires a recurring plan.
The credit-pack view also explains what the balance can be used for and shows the free plan's capabilities alongside it. You can make the purchase based on the workload you have, without first translating it into a subscription tier.
Start with the workload, not the pricing model
If your screenshots arrive at a steady monthly rate and power an ongoing workflow, choose a subscription. If they arrive as a migration, a quarterly batch, a launch, or a client project, credits are likely the cleaner option. If both are true, combine them.
You can compare the full plan limits on the pricing page, or open Billing to choose a plan or buy a one-time credit pack.
The billing model should follow the work—not force the work into a monthly shape.