What GitHub's Built-In Screen Recorder Does
The GitHub screen recorder is a native recording tool integrated into GitHub desktop and the web app that lets you capture your screen while you work in repositories. It is designed for creating short, focused recordings of code reviews, walkthroughs, demos, and bug reports. GitHub records your screen, cursor movements, and system audio you choose, while hiding unrelated open windows and sensitive information by default. This evergreen explainer covers what it records, where recordings live, how long they are kept, privacy and security implications, supported platforms, and step-by-step instructions to record and share efficiently.
How to Start a Recording on GitHub
Depending on whether you use the desktop client or the web interface, the steps differ slightly. Both approaches aim to make recording a repository context fast and repeatable. Follow these steps for a clean, focused recording.
Using GitHub Desktop
GitHub Desktop includes a built-in recorder that ties recordings to a specific repository. Use this when you want to keep work scoped to a single repo.
- Open the desired repository in GitHub Desktop.
- Click the ellipsis (three dots) in the top-right of the repository window.
- Select Start Recording from the menu.
- Give the recording a short title that describes the task.
- Perform the actions you want to capture.
- Click the stop button in the top bar to end the session.
- Optionally add a description and Save the recording.
Using the GitHub Web App
On the web, you can launch the recorder from your workspace when the feature is available to your account.
- Open a repository or file view where you want to record.
- Click the ... menu in the header or a contextual panel.
- Choose Start Recording.
- Confirm microphone and screen sources if prompted.
- Record your workflow.
- Click Stop and then Save or Discard.
What Gets Recorded and What Does Not
GitHub uses contextual capture rules to focus recordings on the task at hand. By default, the tool records the active browser tab or the desktop window you choose, while excluding unrelated open windows and sensitive system indicators. Exact behavior can change with platform updates, so treat the following as a reliable baseline.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Screen area captured by default | Active tab or selected window you choose | Product behavior |
| System audio included | Optional; you can include or exclude during capture | Capture settings |
| Other open windows recorded | No; excluded by default to protect privacy | Design behavior |
| Keystrokes showing sensitive input | Masked or hidden where possible | Privacy safeguards|
| Recording storage location | Local device and/or cloud per configured settings | User configuration |
Storage, Retention, and File Formats
Where recordings live and how long they are retained depends on whether you use the desktop client settings or the web app defaults. By default, desktop recordings are stored locally in the repository's .github/recordings folder, while web recordings may be saved to your account or a temporary cache. Retention policies vary by organization and admin settings. Common formats include MP4 for video and accompanying metadata files for timestamps and descriptions.
Privacy, Security, and Compliance Considerations
Because recordings can contain code, paths, and sensitive information, GitHub emphasizes masking and user control. You should avoid recording authentication tokens, internal URLs, or customer data unless explicitly permitted by your organization. Admins can enforce retention rules, and teams should agree on sharing practices. If you are unsure whether a recording is safe to share, remove or redact portions before publishing. These practices align with standard secure coding and data handling guidance.
Supported Platforms and Requirements
Availability depends on your GitHub Desktop version and web account features. Desktop recording functionality is generally available on recent releases of Windows and macOS. The web recorder may roll out gradually and require a enabled feature flag or higher plan tier. Check your client's release notes or settings panel to confirm support and update if needed.
Best Practices for Clear, Shareable Recordings
- Close unrelated tabs and apps before you start to keep the recording focused.
- Use a descriptive title and brief description to explain the context.
- Record short segments that address a single topic or issue.
- Review the recording and trim unnecessary steps before sharing.
- Sanitize or mask sensitive information, tokens, and private URLs.
- Prefer short, target-specific recordings over long, unfiltered sessions.
When to Use Recording vs Other Sharing Tools
Choose the GitHub screen recorder when you need to show exact UI interactions, step-by-step workflows, or bug behaviors that are hard to describe in text. For simple questions, a brief excerpt or well-written issue may suffice. For complex debugging sessions or stakeholder reviews, a concise recording with clear narration often reduces back-and-forth and speeds resolution. Match the tool to the task and the audience.