RenderLog guides
Older RenderLog guides and product notes. Page 2.
Start here
Pick the path closest to the page you need to protect or render.
API output
Choose this when a product, backend job or customer task needs screenshots, PDFs, HTML, Markdown or stored files.
No-code web tests
Use this when the same URL, viewport and page state need visual regression, assertions, history and review.
Pricing pages
Start here when plan cards, discounts, checkout links or localized prices can drift after product changes.
A useful visual diff should show what changed, whether it is expected, and who needs to decide.
Use this when: Approve the page after a deliberate release or design change.
A page deserves a schedule when the same URL, flow, or state keeps landing on someone's review list.
Use this when: After-deploy checks for pricing or signup pages.
Start with one manual capture when you need proof now. Automate later if the same page keeps coming back.
Use this when: Validate a reported layout issue without waiting for a schedule.
A page check becomes useful when the next person can see the setup, accepted state, and decision in one place.
Use this when: Start with one manual page capture or API run.
Turn the next important page into a saved result, a reviewed baseline or a recurring check instead of leaving it as a one-off issue.