Screen recording for bug reports
When a bug is easier to show than to describe, the reporter records the screen while it happens and the video arrives attached to the ticket.
Pro · session replay is included on Free
The reporter's screen recording open in the panel: forty-seven seconds of a checkout, with the card and CVC fields masked, where pressing Place order leaves the button spinning and nothing else happens. Under the video, the panel's own caption reads Screen recording · 0:47.
How it works
1
The reporter starts recording
Record sits in the same row as Screenshot and Attach, and the composer hides itself for the take — the capture pill with its timer and Stop is the only thing left on the page.
2
The widget uploads while it records
Chunks leave every quarter second, so a long take never depends on one upload at the end, and every field on the page is masked in the video.
3
Your team watches it on the ticket
The recording opens in the drawer's lightbox, beside the screenshot, the replay and the logs.
For the bugs a screenshot cannot hold
Timing, animation and multi-step flows are obvious in ten seconds of video and invisible in a still image. The control is in the composer the reporter is already writing in, and it disappears once a take is attached.
The widget while it records and after it did: a pill at the top of the page counting the take against its one-minute ceiling with a Stop button, and below it the same composer twice — offering Screenshot, Record and Attach, then holding the recording as an attachment while the Record button is gone.
Honest about what was captured
A take that hit the sixty-second ceiling arrives labelled Partial, with the reason it stopped, and the evidence around it says which intervals are missing rather than closing the gap quietly.
What the ticket reports about a recording that stopped early: the evidence strip with the screenshot and a partial recording of one minute, the note that recording stopped at max duration, and under them the session's own account of the interval the replay paused for while the report was being written, with the two diagnostic codes the widget wrote for it.
Exact behaviour
- Capture
- Reporter-initiated, 60 seconds maximum, 15 fps, uploaded in chunks while it records
- Retention
- The project's own window — 30 days by default, settable from 1 to 365; idle sessions 90 days
- Privacy
- The reporter starts and stops it; every input is masked in the video
- Browsers
- Wherever the browser exposes getDisplayMedia and MediaRecorder — desktop Chromium, WebKit and Firefox; where it does not, the widget shows no Record button
- Plan
- Pro
- MCP tool
- get_recording · list_sessions
Works with
Questions teams ask before installing
Is screen recording available on the Free plan?
No, it is a Pro capability. Session replay — the DOM recorded as it changes, with inputs masked — is included on Free.
Does the reporter need an account to record?
No. Recording starts from the widget on your page, and the reporter follows the ticket afterwards through a portal link — still without an account.
What happens if the upload is interrupted?
The chunks already uploaded are the recording, and the ticket reports its duration and the reason it ended — max duration, network backpressure, a size cap — instead of playing a video that silently stops early.
Let reporters show you the bug.
Screen recording is part of Pro, at $29/month or $276/year.