RenderLog is a no-code web testing and visual regression tool with a render API. Pay per successful run from 0.002 EUR, with no base subscription.
Researched and fact-checked by Bartu Cavusoglu · Updated October 26, 2026
RenderLog is a no-code web testing and visual regression product. A team saves a page, an app flow or a UI component state, approves how it should look, and later runs show whether anything visible has changed against that approved version.
It also works as an API for rendered output. Developers can request screenshots, PDFs, HTML, Markdown or stored files from a backend job, CI pipeline or product feature. Both paths share one run history, so results, labels and logs stay together.
The setup follows six steps: create a workspace and API key, define URLs, selectors and viewports for each target, tune rendering with headers, cookies and waits, lock a baseline, automate checks with schedules and webhooks, and review diffs in the dashboard.
A saved check stores the page setup once and can be started manually, from CI, through the API or on a schedule. When a run differs from the baseline, the changed cases are opened for review, and alerts can go to Slack, Teams or a webhook.
The testing side covers content and form-state assertions, saved web tests with viewports, waits and flow steps, and baselines that keep the reason for each approval. Page controls include headers, cookies, selectors, blocked requests and device presets for pages that are hard to render.
The output side covers screenshots, PDF, HTML, Markdown, generated files and async video. Non-document runs include Web Vitals in run details. Run history keeps logs, previews and baselines, and larger workspaces can use S3-compatible storage.
RenderLog is a no-code web testing and visual regression tool. It compares current pages with an approved baseline and also offers an API for screenshots, PDFs, HTML and Markdown.
RenderLog has no base subscription and bills per successful run at 0.002 EUR/run. The site lists 0.003 EUR/run and says early users keep 0.002 EUR/run for their first year. Video is priced separately, and add-ons cost 59, 89 and 99 EUR/mo.
There is no separate free trial. The first invoice is delayed until usage reaches EUR 3, and smaller amounts carry forward, so you can start with real runs without paying a large plan upfront.
No. Timeouts, browser errors and bad results without a real result are not billed. Returning an existing cached result also does not count as a billable run.
The site names Slack, Microsoft Teams and webhooks for notifications, CI pipelines and the API for triggering runs, and S3-compatible storage for larger workspaces.
No code is needed for saved web tests, which you set up with URLs, selectors, viewports and waits in the dashboard. The API is available for teams that want to call RenderLog from backend jobs or CI.
Use Automation when saved web tests need shorter intervals, more scenarios per suite or more viewports per page. It costs 59 EUR/mo and allows 250 suite launches per day, a 30 minute minimum interval, 1000 Check Cases per suite and 3 viewports per case.
Base history filters stay within 30 days. The Retention 1 Year add-on at 99 EUR/mo extends filters to 365 days for result files, logs, baselines and previews, with managed storage up to 3 TB.