Runs onWrit CloudDesktopSelf-hosted
On this page
Screenshot
The screenshot step captures the current page as an image and stores it with the run — proof of state, a visual record of what the workflow saw, or input for visual comparison.
In a workflow, this is a step object with "type": "screenshot". Steps run in order, and each step can read the outputs of the steps before it. See the full workflows reference for the 30+ step types.
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Fields
| Field | Type | Description |
|---|---|---|
quality | number | Optional image quality setting. |
Example
A single screenshot step as it appears in a workflow's steps array:
{
"type": "screenshot",
"config": {}
}How it behaves
- Screenshots are attached to the run and visible in its timeline.
- Monitors have their own visual-baseline machinery; this step is for workflow runs.
Where it runs
The screenshot step executes wherever the run executes. On your local or BYO agent there is no compute charge and the agent can reach intranet-only systems; on Writ cloud the run is metered by running time (~$0.12 per browser-hour, from your plan’s included usage wallet.
What next
- Workflows - the full step vocabulary and the workflow object.
- Recorder - capture steps by clicking through a site.
- Managed endpoints - turn the workflow into a REST endpoint, or an MCP tool.