Skip to main content
A cloud browser session is a normal CDP endpoint, so screenshots work the way your framework takes them, and they save wherever your code runs.

Where screenshots are saved

The most-asked question first: screenshots taken through Playwright or Puppeteer are written by your code, to a path you choose. Nothing is stored on the session unless you enable recording.

Full page, not just the viewport

By default a screenshot captures the visible viewport. For the whole page, top to bottom:
Playwright stitches the scroll automatically. The result contains page content only, no URL bar or browser chrome, because CDP screenshots capture the rendered page, not the window.

Resolution

Screenshot dimensions follow the browser’s screen size, set at session creation with browserScreenWidth and browserScreenHeight (320–6144 × 320–3456). Set them explicitly if screenshots must match a target resolution:

Screenshots vs recording

Screenshots are moments; recording is the whole session as video (enableRecording: true at create, recordingUrl after stop). For debugging agent behavior, recording is usually what you want; for artifacts and QA evidence, screenshots.

From agent tasks

Ask the agent to take screenshots as part of a task and collect them from the run’s workspace files.