Screenshot Multi
Screenshot Multi opens a URL in a headless browser and captures one screenshot per combination in a capture matrix (browser × screen resolution from your execution context catalogs).
Runs asynchronously: after you start a job, status moves through Pending → Queued → Completed (or Failed / Submit failed). Refresh the listing or open details when Completed.
Starting a run
Required fields when creating a run:
| Field | Description |
|---|---|
| Page URL | Full HTTPS/HTTP address to open |
| Capture matrix | Default matrix - built-in preset; Custom matrix - you supply capture rows |
| Project | Current project (from context) |
Optional:
| Field | Description |
|---|---|
| Wait until | When navigation is considered done: Load, DOM content loaded, Network idle, Commit |
| Full page | Capture full scrollable page vs viewport |
| Navigation timeout (ms) | Max wait for page load (default applies if omitted) |
Custom matrix
When Capture matrix = Custom matrix, each row defines:
- Browser (from execution context catalog)
- Screen resolution (from execution context catalog)
The service runs one capture per row. Partial failures are listed separately; successful captures still produce screenshots.
Listing
Project util listing columns:
- Execution, Status, Page URL, Screenshots, User, Created at, Completed at
- Row action → details
Statuses:
| Status | Meaning |
|---|---|
| Pending | Created, not yet submitted to the runner |
| Queued | Accepted by the runner, work in progress |
| Completed | Finished successfully (see screenshot count) |
| Failed | Run failed (see Error on details) |
| Submit failed | Could not hand off to the runner |
Details page
Run summary
- Start parameters: page URL, wait mode, full page, timeout, matrix preset
- Counters: Captures total, Captures succeeded, Captures failed, Duration (ms)
- Error message when status is Failed or Submit failed
Screenshots
Gallery of captures tied to the run. Each item shows preview when the file service returns a valid link.
Screenshots are files in team storage (category screenshot), linked to the util run - not embedded in the database row.
Capture errors
Rows where a matrix cell failed (browser/resolution + error text). Other cells may still have screenshots.
Events
Audit-style timeline (queued, callback received, completed, etc.) for support and debugging.
Lifecycle actions
| Action | Where |
|---|---|
| Create | Start a new screenshot.multi run |
| Details | View parameters, screenshots, errors, events |
| Status | Lightweight status check (API; same fields as listing status) |
| Delete | Remove the util run (and related cleanup on the backend) |
Limits and behaviour (MVP)
- Previews on details - the server resolves preview links when you open details. Large runs (many screenshots) may take a moment to load the gallery.
- Download - not bundled in the first details response; use download when the UI offers it (file service issues a fresh link). See Files and temporary links.
- Link expiry - preview URLs expire; reopen details or use refresh/download to get a new link.
- Runner availability - depends on Browser Tools service configuration for your environment; Submit failed usually means the handoff did not succeed.
- Storage - screenshots count toward team file storage; uploads and quota follow team billing rules when enforced.
See also
- Utils overview
- Files and temporary links
- Execution context - browser and resolution catalogs for custom matrix
| Version | 1.2.1 |
| Last updated | 2026-06-28 |