Record Bug Reports That Don't Bounce Back

Every developer has closed a bug with "can't reproduce", and every reporter has written three paragraphs that a ten-second video would have replaced. A recorded repro is the highest-signal bug report there is — here's how to make one on a Mac, fast enough to do it every time.

"Can't reproduce" — solved

Record while you reproduce. The video captures what prose loses: the exact click order, the timing, and the transient states you can't screenshot live — the toast that flashes, the spinner that never resolves, the layout that breaks for one frame. With pause and resume you can keep one recording open across several attempts at a flaky bug, and trim to the successful repro afterwards.

Point at the broken part

Don't make the developer hunt for the failure. An arrow at the broken widget, a spotlight on the wrong number, a caption with the expected-vs-actual — thirty seconds of annotation saves a round-trip in the tracker.

Blur what the tracker shouldn't see

Bugs live in real accounts with real data. Draw a blur region over the customer's name, email or token for the seconds it's visible, and the repro is safe to attach to a public issue — the blur is baked into the export and every still you take from it.

Video for the repro, still for the issue

The ideal issue has both: a short MP4 proving the steps, and one image at the top showing the failure. Scrub to the failing frame, and the camera button copies it — arrows, blur and captions included — as a PNG on your clipboard, ready to paste into GitHub, Jira or Slack. That's annotated screenshots: one capture, both artifacts.

Frequently asked questions