"It doesn't work" is the least helpful bug report there is. A short bug report video shows the developer exactly what you did, what you expected and what actually happened. This guide covers how to record one on Android so that QA testers, clients and teammates can report problems that get fixed quickly.
Why a bug report video beats a paragraph of text
Written reports leave gaps. The reporter forgets a step, uses a different name for a screen, or describes the error message from memory. The developer then spends time guessing, tries to reproduce it, fails, and asks more questions.
A screen recording removes most of that guessing. It captures the order of taps, the timing, the exact error text and what the screen looked like just before the problem. Combined with a few lines of written context, it is often enough for a developer to find the cause on the first try.
Before you record: reproduce the bug
A video of a bug you can't repeat is still useful, but a video of a bug you can trigger on demand is gold. Before recording:
- Try to repeat it. Go through the same steps two or three times and note whether it happens every time or only sometimes.
- Find the shortest path. Remove unnecessary steps until you have the minimum sequence that causes the issue.
- Prepare test data. Use a test account and fake data, never a real customer's details.
- Clear distractions. Turn on Do Not Disturb so personal notifications don't appear. Our guide to screen recording without notifications explains how.
How to record a clear bug report video
Show the starting point
Start the recording a few seconds before the first step, on a screen the developer will recognise, such as the home screen of the app. If the version number is visible in the app's settings or about screen, show it briefly at the start.
Narrate the steps
Turn on the microphone and say what you're doing: "I'm opening the cart, now changing quantity to three, now tapping checkout." Then say what you expected and what happened instead. Narration makes the video useful even if the viewer skims.
Capture the failure clearly
When the bug appears, stop moving for a couple of seconds. Let the error message, wrong number or frozen screen stay visible. Many bug videos are useless because the tester immediately taps away from the problem.
Recording settings
For visual glitches and animation bugs, record at 60fps (a Premium setting in Cinematic Recorder) so quick flickers are visible. For most other bugs, a standard resolution keeps the file small enough to attach to a ticket. If you need help choosing, see the best screen recording settings for Android. If the bug is about sound, enable internal audio (Android 10+), keeping in mind some apps block audio capture.
Light editing that helps developers
Bug videos don't need cinematic polish, but a little editing saves the reader's time:
- Trim the start and end so the clip begins just before the first step and ends after the failure.
- Auto zoom and click animations make it obvious which button was pressed, which matters when two buttons are close together. See cursor and click effects.
- Focus highlight on the error message or wrong value.
- Don't speed up the failure moment. Timing can be part of the bug.
Because edits are non-destructive, you can always go back to the untouched original if a developer asks for it.
What to write alongside the video
The video shows the problem; a few lines of text make it searchable and complete. A simple template:
| Field | Example |
|---|---|
| Title | Checkout button does nothing after changing quantity |
| Device and Android version | Phone model, Android 13 |
| App version | Version shown in settings |
| Steps | 1. Open cart 2. Change quantity to 3 3. Tap Checkout |
| Expected | Payment screen opens |
| Actual | Nothing happens; button greys out |
| How often | Every time / 2 out of 5 tries |
Attach the video file, or upload it to your team's shared drive and paste the link.
Privacy and file size
Bug videos travel: into issue trackers, chat groups and sometimes to outside contractors. Before sending, watch it once and check for personal names, phone numbers, emails or payment details. Cinematic Recorder keeps your recordings on your phone and never uploads them, but once you share a file, it's out of your hands. Read how to hide personal information in videos for practical steps, then let automatic privacy blur cover whatever slipped through — it runs on your phone.
Keep clips short — under a minute is ideal — so they upload quickly on mobile data.
FAQ
How long should a bug report video be?
As short as possible while still showing every step. Most good bug videos are between 15 and 60 seconds.
What if the bug only happens sometimes?
Record a longer session while repeating the steps, then trim to the moment it happens. Note in the ticket how many tries it took.
Why is my recording black on some screens?
Some apps, such as banking or streaming apps, block screen capture on purpose. That is a security feature, not a recorder bug. See why some apps show a black screen.
Should I record with my face on camera?
Usually not for bug reports. Keep the focus on the screen; the camera bubble is better for tutorials and client updates.
A clear bug report video turns a frustrating "it's broken" into a fix. Reproduce, record the shortest path, pause on the failure, and add a few lines of context — your developers will thank you. In Cinematic Recorder, this kind of work video is commercial use, so it needs Premium or Lifetime; the free plan is for personal use only.
Related features