BobbinQuick answer
Open DevTools before you reproduce the bug and tick Preserve log in Console and Network. Record the repro with your voice. Then right-click the Console and choose Save as... (a plaintext .log file), and in Network click Export HAR (sanitized), which leaves out Cookie, Set-Cookie and Authorization headers. GitHub accepts .log and .zip attachments but doesn't list .har, so zip the HAR first.
Why three files beat one
| File | Answers | How you get it |
|---|---|---|
| Screen recording (MP4) | What did you do, and what did you see? | A screen recorder such as Bobbin |
| Console log (.log) | Which errors and warnings did the page print, and when? | DevTools Console → right-click → Save as... |
| HAR file (.har) | Which requests failed, how slow they were, what came back | DevTools Network → Export HAR (sanitized) |
Bobbin does not read or record browser logs; it has no access to them. That is part of why it needs so few permissions. The log steps below use Chrome's built-in DevTools.
Step by step
1. Open DevTools and keep the logs
- Open DevTools with F12, or Ctrl+Shift+I (Cmd+Option+I on a Mac).
- Network: tick Preserve log so requests survive page loads. DevTools only records requests while it is open, which is why you open it first.
- Console: open the Console settings and tick Preserve log. If your app logs debug messages, set the levels to include Verbose.
- Clear both panels just before you start, so the files only contain this repro.
2. Record the repro
- Click the Bobbin icon, tick Microphone, press Start recording.
- Share the window if you want DevTools visible in the video (useful when an error appears as you click). A single-tab recording shows the page content only.
- Do the steps slowly. Say what you expect, then what happens. Read out any error text.
- Stop with Alt+Shift+S and press Download.
3. Save the Console log
Right-click an empty area of the Console and choose Save as.... Chrome saves the current messages as a plaintext .log file. Copy console in the same menu puts them on the clipboard instead, which is handy for pasting the key error into the ticket.
4. Export the network requests (HAR)
In the Network panel, click Export HAR (sanitized)... in the action bar, or right-click a request and choose Copy → Save all as HAR (sanitized). The sanitized export leaves out Cookie, Set-Cookie and Authorization headers. Only export "with sensitive data" if a developer you trust asks for it, and send it privately.
Check before you attach
- A sanitized HAR still contains URLs, query strings, request bodies and responses, which can include email addresses, IDs or tokens in URLs. Open it in a text editor and search for anything private.
- Console logs can print user data. Skim the
.logfile too. - Watch the video back. Notifications, other tabs and bookmarks are easy to miss.
- On a public GitHub repository, uploaded files can be viewed without signing in.
Attach them to the ticket
- GitHub: drag the files into the issue. GitHub accepts
.mp4/.mov/.webmvideos (10 MB on free plans, 100 MB on paid plans),.logand.jsonup to 25 MB, and.ziparchives. It doesn't list.har, so zip the HAR. A ready bug_report.yml issue form has an Evidence field for exactly this. - Jira or Linear: attach all three; see the Jira and Linear templates.
- Line them up: in DevTools Settings → Preferences → Console, turn on Show timestamps before recording, and mention the clock time when the bug happens in the video.
In our tests Bobbin's 1080p files came to about 250–270 MB an hour, roughly 4–4.5 MB a minute; a busy screen with lots of motion can be larger. A 1–2 minute repro is usually small enough to attach. How to structure it: the 60-second bug report video.
From The Bug Report & QA Kit
Want the full bug-reporting set? The full kit: 10 bug templates for GitHub, Jira, Linear and Markdown, 9 release checklists (126 checks), the severity guide, 8 bug-video scripts and trackers.
See the QA kit ($15, one-time) PDF + ZIP · 7-day refund · more free samples on the page
Checked on 26 October 2026 from their own pages: Chrome DevTools: Console features reference · Chrome DevTools: Network features reference · GitHub Docs: Attaching files. Products change; check the linked page before you rely on it.
Loom, Vidyard, Tella, Tango, Screencastify, Screenity, Zoom and Slack are trademarks of their respective owners. Bobbin is not affiliated with them. Prices and plan limits from their public pages as of 22 Oct 2026.