Limelight
How to Record a Bug Report Video on Your Mac
A great bug report shows the exact steps that trigger the problem, and the exact keys pressed are often the missing clue.
For a fast repro, the macOS built-in is right there. Press Shift-Command-5, record the full screen or a selection around the app, reproduce the bug, and stop with Control-Command-Escape. macOS saves a .mov to the Desktop that you can attach to a ticket. QuickTime works the same way. This is genuinely fine for a simple, obvious bug where the developer just needs to see it happen. The limitation is that a flat capture does not highlight what you clicked or which keys you pressed, and those details are frequently the difference between a reproducible report and a back-and-forth.
Limelight makes repro steps unambiguous. It records locally and offline, automatically zooms into every click so the developer sees precisely which element you interacted with, and smooths the cursor so the pointer path is easy to follow. Most importantly for bug reports, Limelight bakes on-screen keystrokes into the video, so if the bug only triggers after a specific shortcut or an odd key sequence, that sequence is right there on screen. This is a feature most recorders, including Screen Studio, lack, and it removes a huge amount of guesswork from reproduction.
You can also annotate the repro as you go. Limelight's freehand annotations let you circle the broken element or draw an arrow to the error message, baked straight into the video so no separate markup step is needed. One caveat: Limelight does not record audio yet, so if you want to talk through the steps, record a separate voice track with QuickTime or Shift-Command-5 and attach it, or simply write the steps in the ticket. For most bug reports the silent, zoomed, keystroke-annotated video plus a short written summary is the clearest possible package.
Trim the recording before you attach it so the developer's time is respected. In Limelight's editor, cut everything before the repro begins, ripple-delete dead space, and speed up any slow setup so the video gets to the failure quickly. Adjust the zoom to land on the moment things break. Export mp4 for the issue tracker. Because nothing is uploaded, a repro that touches a confidential internal build stays on your machine until you attach it. Limelight is free to start, with Pro at $2.99 per month or $34 one-time.
Why Limelight
- ▸Baked-in on-screen keystrokes reveal the exact key sequence that triggers a bug
- ▸Auto-zoom shows precisely which element you clicked at each step
- ▸Freehand annotations circle the broken UI without a separate markup tool
- ▸No audio yet, so add a separate voice track or written steps to the ticket
- ▸Records offline, keeping confidential internal builds on your Mac
Cursor spotlight free · from $2.99/mo or $34 lifetime · macOS 14+
Or get Pro — from $2.99/mo · See how it works →
free to start, then go Pro from $2.99/mo or a $34 one-time lifetime license. macOS 14+, notarized by Apple.
FAQ
- Why is Limelight good for bug reports specifically?
- It bakes on-screen keystrokes into the video and auto-zooms every click, so developers see the exact keys and elements involved. That removes the guesswork that flat captures leave, making bugs far easier to reproduce.
- Can I narrate the reproduction steps?
- Not in Limelight, since it does not record audio yet. Record a separate voice track with QuickTime or Shift-Command-5, or write the steps in the ticket alongside the silent, annotated video.
- Will the recording leak our internal build?
- No. Limelight records locally and uploads nothing, so a repro of a confidential or unreleased build stays on your Mac until you attach it to a ticket yourself.