Watch the pages that matter most
Track product UI, docs, pricing pages, and other targets that change often.
Early access for teams shipping UI changes every week
Visual bugs still slip through
Catch visual regressions across product, docs, and marketing before release
RenderLog captures real pages and selectors, keeps baselines per target, and gives your team one place to review every visual change.
Starts at 0.003 EUR per screenshot. Only successful renders count and usage below EUR 3 carries forward.
Compare screenshot tools
Built for teams that want screenshot automation and review in one workflow, not a pile of capture scripts.
Why teams switch
Review every change with context
See the new capture next to its baseline and history before anyone approves release.
Turn checks into a release habit
Save settings once, run on schedule, and notify the team when something moves.
Why screenshot APIs stop being enough
Raw captures stop being enough once more than one person needs to review UI changes. Teams need baselines, history, and a release workflow they can trust.
Swipe to explore
Stable screenshots on real pages
Handle login, waiting, cookie banners, and unstable loading states without one-off scripts.
One place to review every visual change
See the baseline, new version, and diff in one place instead of rebuilding context from CI logs and storage.
Checks that fit your release flow
Run checks on a schedule, send webhooks, and give product, design, and engineering the same source of truth.
What you can do today
Swipe to explore
Capture full pages or selectors
Watch a whole page or focus on one component, banner, or pricing block.
Keep baselines and compare versions
Approve a clean baseline for each target and review every new version against it.
Schedule runs and trigger alerts
Run checks automatically and notify your team when something changed.
Handle auth, waiting, and dynamic pages
Use headers, cookies, waits, and device presets when the page needs more than a vanilla screenshot.
The core workflow is already included
Start with capture, baselines, history, and review. Add longer retention or saved scenarios only when your workflow truly needs them.
Pay only for successful renders
Timeouts, browser errors and network failures are not billed.
Extend retention only when it matters
Move from 30 days to 180 when approvals or audits need more history.
Add saved scenarios when needed
Keep multi-step flows for pages that need clicks, typing, or waiting.
Export motion when a still image is not enough
Create a short GIF or MP4 from a scenario run when a still image is not enough.
See pricing details
No separate subscription is required for the core workflow. Usage below EUR 3 carries forward.
Pay per use
Successful screenshots cost 0.003 EUR. If monthly usage stays below 3.00 EUR, the balance carries forward until the threshold is reached.
Estimate monthly usage
Slider up to 100,000. Use the input for up to 1,000,000.
Rate0.003 EUR
Usage subtotal30.00 EUR
AddonsOptional features billed monthly.
Estimated monthly total30.00 EUR
If monthly usage stays below 3.00 EUR, we carry the balance forward and charge later when the threshold is reached.
Read the product guideEarly access pricing may change before general availability. See our Terms of Service and Privacy Policy.
Payments and taxes are handled by Paddle at checkout and are not included in the displayed price.
Feature comparison
RenderLog combines the API with a dashboard for history, baselines and automation.
| Feature | RenderLog | ScreenshotOne | Urlbox | ScreenshotMachine |
|---|---|---|---|---|
| Full page capture | Yes | Yes | Yes | Yes |
| Selector capture | Yes | Yes | Yes | Yes |
| Multi step scenarios (Scenario Runner) | Yes | Partial | Partial | Partial |
| Scheduled automations | Yes | No | Partial | No |
| Webhooks for runs | Yes | Yes | Yes | No |
| Dashboard with history and diffs | Yes | Partial | Partial | No |
| Baselines and diff scores | Yes | No | Partial | No |
| Retention controls (Retention Plus) | Yes | No | No | No |
Partial means limited coverage. Features may change.
Guides
Understand the workflow before you commit to a tool
The guides show what is live now, how early access works, and how to set up captures, baselines, and scheduled checks without guesswork.
5 min read
Review visual diffs, baselines and alerts in RenderLog
A screenshot only becomes useful review material when the team knows what is approved, what changed and who should react next.
Open guide5 min read
Schedule screenshot automations with RenderLog
A scheduled screenshot is useful when the page already has an owner, a rhythm and a reason to be checked again.
Open guide4 min read
Manual website screenshots with RenderLog
Manual capture is the fastest path from a URL to a useful visual answer and often the right first step before automation.
Open guideWhat comes next after the core workflow
The next roadmap steps focus on the parts of the first product plan that still reduce setup work and help teams review changes faster.
Per-viewport baseline workflow
Pick a baseline from run history for each viewport and update it without rebuilding the whole check.
Selector assistant for non-technical users
Suggest stable selectors from the live page, hide noisy blocks, and let users pick targets without writing CSS from scratch.
Inherited render defaults
Set headers, cookies, wait rules and viewport presets at workspace or product level, then override only where needed.
Workspace invites and roles
Invite teammates as admins or viewers and handle workspace moves without breaking ownership.
Suggest a feature via support@renderlog.com
Frequently asked questions
What counts as a screenshot?
A successful render for a single URL and option set. Full page and selector shots each count as one screenshot.
Do failed renders count?
No. Timeouts, network failures and browser errors are not billed.
How does billing work?
We bill only successful screenshots. The invoice is created on the 1st. If a month stays below 3.00 EUR, the balance carries forward. That threshold is about 1,000 screenshots.
Can I capture a selector?
Yes. Use the selector parameter for element shots or configure it in an automation.
Do you store HTML or cookies?
We store rendered images and minimal metadata. Headers and cookies are used only during render.
How long is history kept?
Base retention is 30 days. Retention Plus keeps history for 180 days.
Do you support scenarios?
Scenario Runner adds waits, clicks, typing and multi step flows.
See the workflow before you wire anything up
Read the workflow first. If you are comparing tools, then look at how RenderLog differs from API-only screenshot services.