RenderLog

Teams that ship product releases, run marketing sites, do client work or manage content pages often make changes through CI pipelines, CMS edits, campaigns or translations without a reliable way to see what actually changed on the rendered page. Code tests rarely cover visual drift, so broken CTAs, shifted sections, missing blocks, lost headings or metadata can slip through unnoticed. Agencies showing clients UI changes have no shared visual record to point to instead of opinions. Without a stored baseline and review trail, a generated screenshot or check result becomes just another loose file rather than something a team can compare against and act on.

RenderLog lets users create a workspace, define URLs, selectors and viewports, then tune rendering with headers, cookies and waits for tricky pages before locking a baseline result as the accepted state. Later runs are compared against that baseline, and only meaningful visual or content diffs need review, with notifications sent to Slack, Teams or a webhook. The same run can produce screenshots, PDFs, HTML, Markdown or async video, and checks can be triggered manually, from CI, via API or on a schedule through Automation. Saved no-code web tests support content and form-state assertions in a real browser, while the API path is meant for generating files like screenshots or PDFs directly from a backend job or pipeline.