How to record a screen recording bug report in Chrome

A written bug report often turns into twenty messages: “Which button?” “What did the toast say?” “Can you scroll up?” A short screen recording shows reproduction steps, the broken state, and context in one file — especially when your team is async or across time zones.

This guide is a practical workflow for bug report screen recordings in Chrome with Showesome: what to capture, how to set up Screen Only mode, and how to export MP4 for tickets, Slack, or email.

Why video beats a screenshot thread

Screenshots miss motion, timing, and console output. Text alone cannot show that a spinner never stops or that a modal blocks the wrong layer. A 60–90 second clip with a clear title (“Checkout — payment spinner stuck”) often closes a ticket faster than a paragraph of guesses.

Teams already use screen recording for async updates and remote handoffs. Bug reports are the same idea with a tighter script: reproduce once, narrate briefly, export, attach.

Before you record

• Use Screen Only when the UI alone should tell the story — no camera bubble covering buttons. Compare recording modes if you are unsure.
• Close noise — unrelated tabs, notifications, and desktop clutter compete with the bug. One window or one Chrome tab is usually enough.
• Match the reporter’s environment when it matters — same account type, feature flag, or logged-out state. If the bug only appears in a private window, see recording in Incognito.
• Plan three beats — (1) starting state, (2) steps to reproduce, (3) expected vs what actually happens. You can record in one take or as two short clips if you redo a click.

1. Set up Showesome for a bug repro

1. Open the Showesome icon in the Chrome toolbar (pin it if you have not — enable and pin the extension).
2. Choose Screen Only at the top of the popup.
3. Pick your microphone if you want a short voiceover (“I click Pay, then the spinner never finishes”). Mute is fine for silent repros — see record screen with audio when you need mic + tab sound.
4. Optional: hide the floating control bar in Settings if it would cover the UI you are demonstrating (keyboard shortcuts covers controls visibility).

2. Record the reproduction

1. Click Start Recording.
2. In Chrome’s share dialog, pick Chrome tab (best when the bug is in one tab) or Window if the issue spans multiple panels in the same app. For tab-specific bugs, enable Also share tab audio only when sound is part of the repro — record a Chrome tab with audio.
3. Walk through the steps slowly — pause on each click so viewers can follow.
4. End on the error state — toast, empty state, wrong data, or frozen spinner. Say out loud what you expected if you are narrating.

Keep it short. One focused clip beats a five-minute tour of the whole product. If you need a second segment (“here is the same flow on staging”), record it separately and label both files clearly.

3. Spotlight the broken control (optional)

When the screen is busy, viewers still hunt for the right pixel. With Focus Mode, double-tap Cmd or Ctrl, click the button or field that fails, then continue the repro. Press Esc to return to full screen when you are done highlighting.

Use Focus Mode for one or two key moments — not every click — so the clip stays easy to follow.

4. Export MP4 and attach it where your team works

When you stop recording, the clip is already in your Showesome library in Chrome. To share outside the extension:

1. Open Recordings History from the popup (library guide).
2. Open preview for the clip (preview and export).
3. Convert to MP4 if needed, then Download MP4.
4. Attach the file to Jira, Linear, GitHub, Notion, Slack, or email — or upload to Drive / YouTube if your team prefers a link.

Title the message like a headline: “Settings save — 500 error after Submit”, not “bug video 3”. Link related tickets in the thread so the MP4 stays the proof, not the only source of truth.

What to include in the ticket (besides the video)

Include	Why it helps
Environment	OS, Chrome version, role/account type
Steps	Numbered list matching what you recorded
Expected vs actual	One line each — reviewers scan this first
URLs or build	Staging vs production, feature flag if relevant
Console or network	Optional second clip or screenshot if engineers need logs

The recording shows what happened; the table still gives engineers text they can search and copy.

Quick checklist

1. Screen Only in the popup — UI stays unobstructed.
2. One tab or window — reproduce the bug, not your whole desktop.
3. Three beats — start state → steps → broken result (under ~90 seconds when possible).
4. Slow cursor, short narration — or silent if the UI speaks for itself.
5. Focus Mode on the one control that matters, if the layout is dense.
6. Preview → Convert to MP4 → Download — attach with a clear title in your tracker or chat.

Related reading

• Screen recording tips for remote teams — when async video replaces another meeting
• How to record a Chrome tab with audio — tab picker and tab audio
• Common screen recording mistakes — cursor chaos and cluttered screens
• Your recordings library — find and manage clips
• Preview, export, and optional cloud backup — MP4 and optional upload
• Getting Started — first recording in the real extension UI
• Support — FAQs and contact for extension issues