Captured context
web
Exactly what ships with a report, with every cap spelled out. If it isn't listed here, it doesn't leave the page.
Always captured
| option | type | default | description |
|---|---|---|---|
| console | ring buffer | 100 entries | log / info / warn / error, each truncated to 500 chars. Captured from init onward. |
| network | ring buffer | 50 requests | fetch and XHR: method, URL, status, duration. Request and response bodies are never read. |
| errors | ring buffer | 20 entries | Uncaught JS errors and unhandled promise rejections, with file:line when available. |
| navigation | breadcrumbs | 30 routes | pushState / replaceState / popstate trail — how the tester got here. |
| environment | object | — | Viewport, browser, language, timezone, user agent, connection type. |
| DOM snapshot | gzipped | ≤ 800 KB | rrweb snapshot of the page, inputs masked. Rebuilt in the dashboard, sharp at any zoom. Skipped if over the cap. |
Captured on demand
| option | type | default | description |
|---|---|---|---|
| screenshot | JPEG | ≤ 3 MB | Only when the tester uses Capture & annotate. Blur regions are pixelated before upload. |
| annotations | shapes[] | ≤ 200 | Vector annotations: brush (point list), arrow, rect, blur — with coordinates and color. |
| session recording | gzipped | ≤ 3 MB | Only during a test session. rrweb event stream across page loads, merged at send time. |
| click journey | list | ≤ 200 | Only during a test session. Timestamped clicked elements with their visible label. |
noteThe whole report is capped at 8 MB; individual media that would blow the cap are dropped rather than failing the report. The technical context always gets through.
What is never captured
- Request or response bodies — ever.
- Input values — masked in both the DOM snapshot and session recordings; passwords are always masked.
- Cookies, storage contents, auth headers.
- Anything under a tester's blur annotation.