Tasks
How to record a screen recording for a bug report
A good bug recording answers three questions: what you did, what happened, and what you expected. Most recordings only answer the second.
Start before the problem
Begin recording a few seconds before you reproduce the issue. The steps leading up to a bug are usually more useful than the bug itself.
Narrate as you go
Turn on the microphone and say what you are clicking and what you expected to happen. It takes no longer and removes an entire round of follow-up questions.
Include the console if it matters
For web bugs, open developer tools and record the tab with the console visible. Errors on screen are worth more than a description of them.
Keep it short
Thirty seconds that show the problem beat five minutes that contain it. Record several short clips rather than one long one.
Read next
- How to record your screen with sound
The two different kinds of audio in a screen recording, and which browsers can capture each.
- How to record your screen and webcam together
Add a camera overlay to a screen recording, and how it is combined into one file.
- How to record a single browser tab
Tab recording, which is the cleanest option and the only one that reliably captures audio.