API output
Render a page result
Call RenderLog from a backend job, CI pipeline or product feature to create screenshots, PDFs, HTML, Markdown or stored files.
Pages change without warning
Catch visible page changes before customers do
Render a page once or keep checking it on a schedule. RenderLog shows what changed, keeps the accepted baseline and leaves the evidence ready to review.
Built on Cloudflare infrastructure for reliable browser-based page checks.
Latest run+1 diff
How it works
Choose the path by the job
Use the API for files. Save a website check when the same page needs owners, baselines, alerts and repeat runs.
Visual checks
Watch a page over time
Save high-value URLs with viewports, waits and flow steps when a page needs repeatable visual control.
What both paths share
Approve the baseline
Choose the result that represents the accepted state. Later runs compare against that decision.
Run it where work happens
Start checks manually, from CI, through the API or on a schedule when Automation is enabled.
Review only meaningful changes
Open changed cases, keep the result and notify Slack, Teams or a webhook when action is needed.
Keep the operational trail
Keep result files, labels, logs and billing context attached to the same page or API run.
Coverage
What stays with every page run
Render outputs
Screenshots, PDFs, HTML, Markdown and files use the normal successful-run price. Async video keeps the same run history and adds a separate per-video run rate.
Baseline review
Promote an accepted state, compare later runs and keep the reason for the decision.
Saved website checks
Group priority pages with viewports, waits, flow steps and owners.
Real page controls
Use headers, cookies, selectors, waits, blocked requests and device presets.
Use cases
Where teams use RenderLog first
Start where a missed page change already costs trust, support time or release confidence.
Product releases
Review visible changes after a release
Trigger a Check Suite from CI, wait for the page to settle and review only screens that changed.
Fits pricing, signup, checkout, payment and account pages.
Marketing sites
Keep landing pages from drifting
Save the accepted version, then catch broken CTAs, shifted sections, missing blocks and pricing edits.
Run checks after CMS updates, campaigns and pricing changes.
Client work
Show clients the page state, not opinions
Agencies keep a visual record for client sites, run regular checks and show exactly what changed.
Use it for weekly reports, content updates and post-release checks.
Content teams
Protect content pages tests rarely cover
Docs, help centers and long pages can break without failing a test suite. Give them baselines and history.
Compare pages after CMS edits, translations and template changes.
Make the next page change reviewable
Pick one page that matters, approve its current state and let the next run show whether anything visible changed.