What it solves
Use steps for click, type, wait, and targeted screenshots to capture dynamic experiences.
Feature
Automate browser actions before capture so SPAs, modal flows, and gated content are rendered in the right state.
Use steps for click, type, wait, and targeted screenshots to capture dynamic experiences.
Live example
Trigger chart tooltips, run searches, expand tree nodes, open drawers — any interaction a real user would perform. Capture the exact state you need, not just the initial page load.
Step commands
Each step in the steps array maps to a browser action. Combine them in any order to reach the exact state you need before capturing.
click Click any element by CSS selector.
{ "command": "click", "selector": "#accept-btn" } type Type text into an input or textarea.
{ "command": "type", "selector": "#search", "value": "term" } wait Pause for a fixed number of milliseconds.
{ "command": "wait", "value": 1.5 } scroll Scroll the page or an element into view.
{ "command": "scroll", "selector": "#section" } screenshot Capture immediately, optionally scoped to a CSS target.
{ "command": "screenshot", "target": ".chart-container" } Use cases
Fill credentials, submit the form, and capture the authenticated dashboard — all in one job.
Hover over data points, switch chart tabs, or select date ranges before capturing dashboards.
Open dialogs, side panels, or dropdowns to document UI states that are not visible on load.
Type a query, wait for results, then capture — useful for visual regression on search UIs.
Advance through checkout or onboarding flows to capture any step for QA and compliance records.
Combine steps with video=true to record a full interaction replay as mp4, webm, or gif.
See request examples and endpoint details in the API docs.