Quick answer
Record the browser window with the diff and the running app, talk for about two minutes, and drag the file into the PR description. GitHub accepts .mp4, .mov and .webm videos up to 10 MB on free plans and 100 MB on paid plans. 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. So keep a free-plan video to about two minutes at 1080p. Bobbin just saves a file: it has no GitHub integration.

When a video helps (and when it doesn't)
- Worth it: UI changes, anything with a before-and-after, a refactor that touches many files, a change reviewers in another time zone need to understand without a call.
- Skip it: one-line fixes, dependency bumps, changes the description already explains in two sentences.
- Never instead of text. Keep the written summary and test steps in the PR; the video is for context. Not every reviewer can watch with sound.
A 2-minute script
| Time | What to say and show |
|---|---|
| 0:00–0:15 | What this PR does and why, in one sentence. Mention the issue it closes. |
| 0:15–0:45 | Show the result running: the new behaviour, or before and after side by side. |
| 0:45–1:30 | Walk the diff in the order you would review it: the core change first, then the supporting files. Skip generated files. |
| 1:30–1:50 | Risks and edge cases, what you tested, and what you didn't. |
| 1:50–2:00 | Exactly what you want feedback on ("is the retry logic in the right place?"). |
Before you hit record
- One window. Put the GitHub diff and the running app in tabs of one Chrome window, or side by side on one screen.
- Make code readable. Zoom the page to 125–150% (Ctrl/Cmd + +) so the diff is legible in a small player.
- Hide secrets. Close
.envfiles, terminals with tokens, password managers and chat. Turn on Do Not Disturb. - Public repository? GitHub's docs say files uploaded to public repositories can be accessed without signing in, so treat the video as public.
Record it with Bobbin
- Click the Bobbin icon in Chrome's toolbar and choose Record screen, window or tab.
- Tick Microphone. Tick Webcam bubble if you want your face in the corner.
- Press Start recording and share the window (or entire screen). The bubble appears in window and screen recordings, not in single-tab recordings.
- After the 3-second countdown, follow the script. Pause with Alt+Shift+P if you lose your place; stop with Alt+Shift+S.
- Press Download. You get an MP4 where Chrome supports it (Chrome 126 or newer) and WebM otherwise; Bobbin tells you which format it used.
Free: no account, no watermark, no time limit, up to 1080p at 30 fps, and nothing is uploaded. Every second is saved as you record, so a crash doesn't lose the take. Bobbin doesn't host videos or make share links, and it has no editing, transcripts, comments, viewer analytics, team workspace or mobile app.
Fit GitHub's video limit
| Repository owner's plan | Video limit | About how long at 1080p |
|---|---|---|
| Free GitHub plan | 10 MB | About 2 minutes |
| Paid GitHub plan | 100 MB | About 20 minutes |
The durations are estimates from our own 1080p test files; check the file size before you upload. GitHub recommends H.264 video for the widest browser support. In our tests Bobbin's MP4 files used H.264 video, and WebM is also accepted.
- Too big? Record in two parts (the result, then the code), or cut the walkthrough to the core files.
- Longer demo? Upload it to storage your team already uses and paste the link: see how to share a large screen recording.
- Don't record at 4K for a PR. Pro's higher resolutions make bigger files; 1080p is plenty for a diff.
Make it part of your PR template
Add a "Demo" line to your pull request template so authors know a short video is welcome for UI changes. Reviewers can reply the same way: a 60-second recording of "here's what I'd change" is often clearer than five comments.
Filing the bug that the PR fixes? See how to record a bug report video and how to attach console logs and a HAR file.
Checked on 26 October 2026 from their own pages: GitHub Docs: Attaching files · GitHub Docs: Creating a pull request template. 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.