Recording a session
Show the bug instead of describing it.
Some bugs only happen after three clicks in the right order. Record them. The developer gets a replay of the page with every console error and failed request lined up beside it.
Press Record
In the dock, press Record. Recording covers this page only — never other tabs, never your desktop, and it never asks to share your screen.
Do the thing
Use the page as you normally would until the bug appears. The recording bar counts errors and failed requests as they happen.
Stop & describe
Press Stop & describe. A composer opens with the recording already attached — Recording attached · 42s. Tell the team what happened and press Send with recording.
A recording only reaches the team through a Jot. If you close the composer without sending, the recording is discarded.
What is recorded
Not video — the page's structure and changes, replayed in the developer's browser. Every input field is masked before anything leaves your browser, and passwords are always masked. See Privacy & masking for the details.
Recording is the one part of Jot that downloads extra code. Pages where nobody presses Record never pay for it.
In a mobile or desktop app
In apps built with Flutter or React Native, Record and Stop & describe work the same way. The recording shows the app's own screen — never other apps — with the console, network calls, screen changes and taps lined up beside it. Taps are positions only; what you type is never recorded. Password fields and anything the app marks as private are blacked out on the device, before the recording exists. Jot keeps the last two minutes.
If the app crashes, Jot asks the next time it opens whether to send the crash to the team. Say yes and it arrives as a Bug Jot, with whatever was recorded.