Pricing

Pay for useful page results, not a fixed plan

Start with successful runs, then add automation, throughput or retention only when a workspace needs them.

Choose monthly volume

Move the slider or type a run count. Prices update in the cards.

0.002 EUR/run

Above the minimum invoice.

Monthly cost at this usage

RenderLog

Best default

Usage-based product

20.00 EUR

30.00 EUR

No base subscription. Failed runs and cache hits should not be billed. The first invoice starts after 3.00 EUR is accumulated.

ScreenshotOne

Monthly quota plus overage

$79

Strong API option with quotas, request limits and extra render pricing.

ApiFlash

Fixed screenshot quota, no public overage

$35

Public pricing stops at 100,000 screenshots. Larger volume is custom, so there is no transparent overage price to compare.

Urlbox

Tiered render plans

$99

Mature screenshot API with plan thresholds, storage options and higher base pricing at scale.

Public screenshot API pricing pages checked on May 19, 2026. Feature scope and limits can change.

What the price covers

RenderLog starts as a screenshot API, then keeps the operational layer around each result. Competitors are useful for narrow capture workloads, but the extra review and automation layer usually has to be built elsewhere.

Pricing

Usage first, modules later

Pay per successful result. Add monthly modules only when you need more automation, throughput or retention.

Most public plans sell monthly buckets, then add overage or hard limits.

Outputs

More than screenshots

Screenshots, PDF, HTML, Markdown, generated files and previews are part of the run model.

Many screenshot APIs optimize for image output first and add other formats later.

Review

Built-in review trail

Baselines, visual review, labels, logs, artifacts and team decisions stay with each run.

API-only tools often leave approval, baselines and history to your own system.

Automation

One workflow for API and visual checks

Manual checks, API runs and scheduled Check Suites share the same result history.

Fixed plans usually separate API calls from monitoring workflows.

Scale

Separate add-ons

Raise throughput, automation and retention separately, so growth follows the real workflow.

Higher capacity often means moving to a larger plan with features you may not use.

Base price and optional modules

The base run already covers API output and review history. Monthly modules raise limits when a workspace needs more scheduled capacity, throughput, retention or analysis.

Successful runs

0.003 EUR/run 0.002 EUR/run

API, dashboard and Check Suite results

Included

Screenshots, PDF, HTML, Markdown, file output, run history, logs, baselines, previews, async API and webhooks

Early users keep 0.002 EUR/run for their first year. Failed runs without a real result are not billed.

Automation

59 EUR/mo

Scheduled checks that need more cases, launches or viewports

Included

250 suite launches/day, 30m minimum interval, 1000 Check Cases/suite and 3 viewports/case

Each successful Check Case result is still billed as a run.

High Throughput

89 EUR/mo

Production API traffic with short bursts

Included

Up to 300 successful runs/min

Works with dashboard, API and Check Suites.

Retention 1 Year

99 EUR/mo

Long history and audit-friendly result files

Included

History filters up to 365 days for result files, logs, baselines and previews. Managed storage up to 3 TB.

Base filters stay within 30 days. Active baselines stay protected.

FAQ

Is there a free trial?+

There is no separate free trial because the first invoice is delayed until usage reaches EUR 3. You can start with real runs without paying a large plan upfront.

How does the EUR 3 minimum invoice work?+

If monthly usage is below EUR 3, we carry the amount forward. Payment is charged later when the accumulated invoice reaches EUR 3.

What is a run?+

A run is a successful render that returns a real result. It can be a screenshot, PDF, HTML, Markdown, generated file or video.

Do failed runs count?+

No. Failed or bad runs without a real result are not billed.

Do cached results count?+

No. Returning an existing cached result should not count as a billable run.

When do I need Automation?+

Use Automation when recurring website checks need shorter intervals, more pages per suite or more viewports per page.

Can I use my own storage?+

Yes. S3-compatible storage is supported for larger workspaces.

Price the page work you actually run

Start with the page or API result that already needs a decision. RenderLog keeps the output, baseline and review history together from the first useful run.

Start using RenderLog