RenderLog guides

Guides for page checks, API output and visual review

Use these guides to decide what to capture, what to monitor and when to add baselines, alerts or longer history. Each article starts from a real page task, not a generic testing checklist.

Start here

Best path to start

Pick the path closest to the page you need to protect or render.

Monitor pricing pages before they break quietly
4 min read

Monitor pricing pages before they break quietly

Pricing pages change often and fail in ways uptime checks miss. Keep the visible page, the accepted state and the next pricing decision in one review path.

Use this when: Watch the full pricing page, not only one selector or API response.

pricing page monitoringvisual monitoring
Read guide
Daily digests for routine visual check results
3 min read

Daily digests for routine visual check results

Use immediate alerts for broken pages and daily digests for stable check history that should not interrupt the whole team.

Use this when: Use every run for urgent checks and broken-page signals.

notificationsvisual monitoring
Read guide
Retention filters for recent and one-year history
3 min read

Retention filters for recent and one-year history

Use base history for recent review. Add one-year retention when older result files, accepted baselines or audit evidence must stay within reach.

Use this when: Base history focuses on the last 30 days.

run historyretention
Read guide
Failure rules for wrong screenshot results
3 min read

Failure rules for wrong screenshot results

Failure rules keep bad captures out of review so teams spend time on real page changes, not pages that loaded the wrong state.

Use this when: Use presets for common failures such as challenge pages, CAPTCHA and login walls.

visual checksscreenshot automation
Read guide
GET or POST for screenshot API runs
3 min read

GET or POST for screenshot API runs

Start with GET for a quick render. Move to POST when the request needs secrets, longer input, storage routing or repeatable steps.

Use this when: Use GET for a quick URL to screenshot, PDF, HTML or Markdown run.

screenshot apirender api
Read guide
Review visual diffs with baselines and ownership
3 min read

Review visual diffs with baselines and ownership

A screenshot becomes review material when the team can see the accepted state, the new state and who owns the next decision.

Use this when: A baseline marks the state the team has accepted.

visual diffsbaseline review
Read guide
Manual website screenshots before automation
3 min read

Manual website screenshots before automation

Start manually when a page needs a quick visual answer, then save the same setup for automation only if the check repeats.

Use this when: Validate a reported layout issue without waiting for a schedule.

manual capturesvisual QA
Read guide
Turn page captures into decisions
3 min read

Turn page captures into decisions

A page capture earns trust when the next person can see the file, setup, accepted state and review decision together.

Use this when: Capture the current page from the dashboard or API when the team needs evidence.

product guidevisual check automation
Read guide