Quick answer
Drag and drop the video file into the issue or comment box, or click below the box to browse for it. Videos can be .mp4, .mov or .webm, up to 10 MB in repositories owned by a user or organization on a free GitHub plan and 100 MB on a paid plan. GitHub recommends H.264 for the widest playback. At 1080p, 10 MB is roughly two minutes of screen recording.

1. Record the bug
- Click the Bobbin icon in Chrome's toolbar and choose Start recording.
- Tick Microphone if you want to narrate. Tick Webcam if you want your face in the corner (the bubble is drawn into tab, window and screen recordings).
- Press Start and pick what to share in Chrome's picker. After the 3-second countdown, show the problem. Pause with Alt+Shift+U; stop with Alt+Shift+S.
- Press Download. You get an MP4 where Chrome supports it (Chrome 126 or newer) and WebM otherwise.
Free: no account, no watermark, no time limit, up to 1080p at 30 fps. Nothing is uploaded until you attach it yourself. For what to say while you record, see how to record a bug report video.
2. Attach it to the issue
- Open the issue, or start a new one, and click into the description or a comment box.
- Drag the video file from your Downloads folder and drop it into the box. Or click the area below the comment box to browse for the file.
- Wait for the upload to finish. GitHub inserts a link to the file in the text, and the video shows as a player once you submit.
GitHub uploads the file as soon as you attach it, even before you submit the issue. You can also attach videos from the command line with GitHub CLI.
3. Size and format
| GitHub | Video limit per file | Roughly this much 1080p |
|---|---|---|
| Repository owned by a user or organization on a free plan | 10 MB | About 2 minutes |
| Repository owned by a user or organization on a paid plan | 100 MB | About 20 minutes |
Durations are estimates from our own 1080p test files with Bobbin (about 4–4.5 MB a minute for normal screen content), rounded down; a busy screen makes bigger files. GitHub accepts .mp4, .mov and .webm, and notes that whether a video plays depends on the viewer's browser, so it recommends H.264. Bobbin saves MP4 where your browser supports it (Chrome 126 or newer) and WebM otherwise; in our tests its MP4 files used H.264 video.
4. Keep it under the limit
- One bug, one take. Reproduce it once, start to finish. Pause with Alt+Shift+U while you set up the next step.
- Record a tab or a window, not a big screen. Smaller areas make smaller files.
- Stay at 1080p and 30 fps, the free maximum. It is plenty for a ticket.
- Messed up? Discard the take and start again; nothing has been uploaded anywhere.
Still too big? Split it into two clips, or put the file in shared storage and paste the link: see video upload size limits and how to share a large screen recording.
5. Write the text around it
Add the steps to reproduce, expected and actual result, and the time in the video where it goes wrong. A ready-made issue form is in the free GitHub bug report issue template. If a developer will want the console output too, see how to save console logs and a HAR file. Reviewing code rather than reporting a bug? See how to record a pull request walkthrough.
Before you post in a public repository, check the video for tokens, email addresses and customer data: anyone who can see the issue can watch it.
From The Bug Report & QA Kit
Need templates for the rest of the bug report? 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 31 October 2026 from their own pages: GitHub Docs: Attaching files. Limits and plans change; check the linked page before you rely on it.