How to Record a Bug Report Video Developers Can Act On

Here is how to record a bug report video: open the page where the bug happens, open the browser console, start a screen recording, and reproduce the bug while saying each step out loud: what you clicked, what you expected and what actually happened. Then add your browser, operating system and URL, stop, and paste the link into the ticket with a short written summary.

That is the whole method. The rest of this guide gives you a checklist to run before you hit record, a narration template you can read from, and the habits that make developers say “got it” instead of “can’t reproduce”.

Why a bug report video beats text alone

Written bug reports miss the small things: the button you clicked twice, the half-second flicker, the field you left empty, the scroll position. A developer then guesses, cannot reproduce it, and the ticket goes back and forth for days.

A bug report screen recording shows the exact path. Developers see your clicks, the timing and the error in one go. Add a camera bubble and your voice, and they also hear what you expected to happen, which is often the most important part.

Video alone has a weakness, though. Developers do not want to watch a five-minute video to find the one second that matters. So the goal is a short, structured video plus text they can skim. More on that below.

Before you hit record: the bug report checklist

Run through this list first. It takes two minutes and saves a lot of follow-up questions.

• Can you reproduce it? Try it at least twice. Note if it happens every time or only sometimes.
• Steps to reproduce written down in order, starting from a known point (for example, “logged in, on the Dashboard”).
• Expected result: what should happen.
• Actual result: what happens instead, including any error message text.
• Browser and version. Type chrome://version in Chrome or edge://version in Edge.
• Operating system and version. On Windows, Settings > System > About. On a Mac, Apple menu > About This Mac.
• URL of the page, and the account or test data you used.
• Console open. Press F12 (or Ctrl + Shift + J on Windows, Cmd + Option + J on Mac) and pick the Console tab so errors show up on screen.
• Private data hidden. Use a test account if possible, close unrelated tabs, and turn on Do Not Disturb.

How to record a bug report video, step by step

You can use any screen recorder for this. Here is how it works with Showplain, which records in Chrome or Edge with nothing to install. If you are new to browser recording, our guide to recording your screen in Chrome covers the basics.

1. Set the scene. Open the page just before the bug, with the console docked at the side or bottom.
2. Start a recording. In Showplain, choose screen and camera (or screen only), allow your microphone, and in the share picker choose the browser window (not the single tab) where the bug happens. Sharing a tab records only the page itself, so a docked console would not show up.
3. Introduce the bug in one sentence. “When I save a draft with an empty title, the page freezes.”
4. Reproduce it at normal speed. Do what a user would do, so the developer sees the real timing.
5. Repeat it slowly with narration. Say each step as you click. Pause on the error and read the message out loud.
6. Show the evidence. Point at the console errors, the wrong value or the broken layout. Hover over the error so the full text is visible.
7. Say the environment. Browser, version, OS and the account you used.
8. Stop. The share link is copied right away because the video uploads while you record. Paste it into the ticket.

Bug report narration template

Keep this open in a sticky note while you record. You do not have to read it word for word.

1. SUMMARY   "The [feature] does [wrong thing] when I [action]."
2. SETUP     "I'm logged in as [test user], on [page/URL]."
3. STEPS     "First I click [X]... then I type [Y]... then I press [Z]."
4. EXPECTED  "I expected [correct result]."
5. ACTUAL    "Instead, [what happens]. Here's the error in the console: [read it]."
6. CONTEXT   "This is Chrome [version] on [Windows 11 / macOS version].
              It happens every time / about 1 in 5 tries.
              It started [today / after the last release], as far as I know."

Bug report screen recording tips

• Keep it short. One to three minutes is ideal. One bug per video.
• Move the mouse slowly and pause for a second after each click, so viewers can see what changed.
• Do not edit or cut. A continuous recording proves the steps happen in that order. If you need to stop and think, use pause instead.
• Zoom in (Ctrl or Cmd and +) if the bug is in small text or a small icon.
• Show the Network tab too if a request fails. A red line with a 500 status is useful.
• Say “this is the bug” at the exact moment it happens. It makes that spot easy to find in the transcript later.

How to report a bug with video: what goes in the ticket

A video link with no text is hard to search and hard to triage. Paste this into the ticket with your link:

Title: [Feature] [does wrong thing] when [action]

Video: [link]

Steps to reproduce:
1. ...
2. ...
3. ...

Expected: ...
Actual: ...

Environment: Chrome [version], [OS + version], [URL], [test account]
Frequency: every time / intermittent
Console error: [paste the first red line]

Why chapters and transcripts help developers skim

A developer looking at a ticket queue wants to know three things fast: what is broken, how to reproduce it, and where in the video it happens. Notes next to the video answer those without pressing play.

With Showplain, every bug report video gets:

• A searchable transcript. Your spoken steps become text the developer can copy straight into the ticket as repro steps. They can also search for the error message you read out loud.
• A short summary and key points. Enough for a product manager to triage the bug without watching it.
• Clickable chapters (Pro). Sections like “Steps”, “The error” and “Environment” let a developer jump straight to the moment the bug happens.
• Action items (Pro). Requests you say out loud, such as “please check the save endpoint”, can be pulled out as a short to-do list.

The transcript, summary and key points are on the Free plan. Chapters and action items are part of Pro, and new accounts get 14 days of Pro free with no card (see pricing). Following the narration template above helps here too: when you say “expected” and “actual” out loud, those lines are easy to find in the transcript. Our guide to screen recordings with a transcript and summary explains each type of note.

Developers and QA testers can watch the link without creating an account. Links are private, unlisted and use long random addresses, you can turn off downloads, and you can delete a video at any time. That matters when a bug report shows customer data.

Showplain works in Chrome and Microsoft Edge on a computer. It does not record on phones, so for a mobile app bug, use your phone’s built-in screen recorder and upload the file. Showplain can also take an MP4 or WebM you upload and add the same AI notes.

Common mistakes in bug report videos

• No narration. A silent video shows what happened, not what you expected.
• Starting mid-way. Begin from a known state, such as the logged-in dashboard, so the steps can be repeated.
• Too much at once. Three bugs in one video means three tickets nobody can close. Record one video per bug.
• No environment details. “It’s broken” is not enough. Browser, version and OS often explain the bug.
• Leaving private data on screen. Customer emails, payment details and tokens should stay out of the shot.

The same short, structured style works for the rest of your team’s updates too. See our template for async video updates, or create a free Showplain account and record your next bug report in Chrome or Edge.