Founding price: the first 100 buyers get Pro for life at $24 once (then $39).Founding: Pro for life $24 See Pro →
Guides

How to record a VS Code code walkthrough with your webcam

A short recorded walkthrough of the code helps when you're onboarding a teammate, explaining a design decision or handing over a module. VS Code has a few built-in settings that make code readable on video. Here is how to set them up and record the VS Code window from Chrome with your face and voice.

Quick answer

Zoom VS Code in (View > Appearance > Zoom In) so the code is readable at 1080p. Turn on Developer: Toggle Screencast Mode from the Command Palette to show your keystrokes. Close files and terminals that show secrets. Then, in Bobbin, choose Start recording and pick the VS Code window in Chrome's picker, with webcam bubble and mic on.

A developer at a desk with code on a large monitor
Explaining code on video. Photos are illustrative.

1. Make the code readable on video

2. Check for secrets first

With Screencast Mode on, VS Code shows what you type on screen, including anything typed into a terminal. Before you record, close .env files, terminals with tokens in their history and any tab showing customer data. A local recording never leaves your computer until you share it, but the person you send it to sees everything in the frame.

3. Record the VS Code window

  1. Click the Bobbin icon in Chrome's toolbar and choose Start recording.
  2. 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).
  3. 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.
  4. Press Download. You get an MP4 where Chrome supports it (Chrome 126 or newer) and WebM otherwise.

In Chrome's picker, choose the Window option and pick VS Code (or record your whole screen). Tab, window and screen recordings all include the webcam bubble; with Pro, move it to a corner where it doesn't cover code. Free: no account, no watermark, no time limit, up to 1080p at 30 fps.

4. A walkthrough structure that works

  1. The one-sentence purpose of the code you're about to show.
  2. Where it starts: the entry point, route or function a request first hits.
  3. The path through it: follow one real case end to end, with Go to Definition rather than scrolling.
  4. The tricky part: the decision a reviewer or new teammate would otherwise ask about.
  5. What's next: open questions, TODOs or where to start changing it.

Keep each recording to one topic; several five-minute videos are easier to find and re-watch than one long one. Pause with Alt+Shift+U while you open the next file. Walking through a change rather than existing code? See how to record a pull request walkthrough.

5. Share it

Bobbin saves an MP4 (WebM in older Chrome) on your computer. At roughly 4–4.5 MB a minute for normal screen content, a five-minute walkthrough is about 20–25 MB: too big for a free-plan GitHub comment (10 MB) but fine for paid plans (100 MB) or your own storage. See how to attach a recording to a GitHub issue and how to share a large screen recording. Bobbin doesn't host videos or make share links, and it has no editing, transcripts, comments, viewer analytics, team workspace or mobile app.

Try Bobbin freeSee pricingNo account · no watermark · no time limit

Checked on 31 October 2026 from their own pages: VS Code docs: Accessibility (Zoom) · VS Code docs: User interface (Zen mode) · VS Code 1.31 release notes (Screencast Mode). Limits and plans change; check the linked page before you rely on it.

Record your screen and camera. Keep the file.

Free, no account, no watermark, no time limit. Saves an MP4 on your computer.

Bobbin is freeChrome extension for computersAdd to Chrome, it's free