Built for GitHub PRs, Issues, Linear & Jira · Safe for Private Code

Compress Screen Recordings for GitHub (Under 10 MB)

Turn bloated 80 MB macOS QuickTime .mov or OBS recordings into crisp, inline-playable H.264 .mp4 clips strictly under GitHub's 10 MB limit—without uploading proprietary UI or source code to external servers.

✓ Calibrated ≤ 9.5 MB for GitHub Free's 10 MB gate

✓ Converts .mov / .webm / .mkv → H.264 .mp4

✓ Zero cloud upload—SOC2 / NDA friendly

🚀

GitHub Free / Open Source PRs

Strict 10 MB Limit · Inline MP4

Targets 9.5 MB (with a 4% MP4 container safety margin) and mutes unnecessary mic hiss if desired so UI text stays razor-sharp.

Target ceiling:

Apply 10MB PR preset & open compressor →

Drop QuickTime .mov or screen recording here

Outputs universal H.264 .mp4 ready to drag into GitHub

🛠️

GitHub Pro / Linear / README GIF

25–100 MB Caps · Or README GIF

Uploading to GitHub Pro/Enterprise (100 MB cap), Linear/Jira tickets, or exporting a silent loop for a repository README.md?

Preset:

Open developer video preset →

Click to choose recording or drag & drop

Trim dead seconds at start/end right inside the workspace

Developer Platform Video Attachment Limits

Dragging a raw Retina screen recording into a PR comment almost always triggers "Yowza, that's a big file." Here are the exact byte ceilings across engineering tools:

Platform	Video / GIF Limit	Accepted Formats	Recommended NeatCompress Setting
GitHub Free (Issues / PRs / Discussions)	10 MB strict	`.mp4`, `.mov`, `.gif`	Target ≤ 9.5 MB · H.264 MP4 · 30 fps
GitHub Pro / Team / Enterprise Cloud	100 MB video (10 MB GIF/images)	`.mp4`, `.mov`, `.gif`	Target ≤ 24 MB or ≤ 95 MB · H.264 MP4
GitHub `README.md` Repo Docs	≤ 5–10 MB recommended	`.gif` or Issue-hosted `.mp4` URL	Video to GIF (2–6s loop) or ≤ 9.5 MB MP4
Linear / Jira Cloud Tickets	Typically 20 MB – 50 MB	`.mp4`, `.webm`, `.mov`	Target ≤ 24 MB · Mute mic if silent UI demo
Bug Bounty Reports (HackerOne / Immunefi)	25 MB – 50 MB per PoC	`.mp4`	100% local compression keeps zero-day PoCs off third-party clouds

3 tips to keep code & terminal fonts readable under 10 MB

Drop 60 fps to 30 fps (or 24 fps): UI demos and terminal reproductions rarely need 60 fps, and halving frame rate frees substantial bitrate per frame for crisp text edges.
Mute empty audio tracks: Screen recorders often capture silent or fan-noise stereo audio at 192 kbps. Switching audio to "No Audio" (Mute Video) gives 100% of your 10 MB budget to the video stream.
Trim waiting time first: Use the built-in scrubber to cut 5 seconds of build/reload waiting before encoding—every second trimmed directly boosts visual quality.

Frequently Asked Questions

What is the maximum video upload size for GitHub Pull Requests and Issues?

GitHub Free accounts enforce a strict 10 MB maximum file size for .mp4 and .mov attachments inside Issues, Pull Requests, and Discussions. Users with GitHub Pro, Team, or Enterprise Cloud accounts can attach videos up to 100 MB.

Why are macOS screen recordings (.mov) rejected by GitHub?

macOS Screenshot (Cmd+Shift+5) and QuickTime record Retina-resolution .mov files at very high bitrates—often 40 MB to 120 MB for a 20-second UI walkthrough—and sometimes in HEVC formats that don't play inline across every browser. Converting to standard H.264 .mp4 with a 9.5 MB target keeps UI text readable and embeds inline everywhere.

Is it safe to compress private repository demos or customer bug recordings here?

Yes. Unlike cloud video compressors that upload your screen recording to third-party storage buckets, NeatCompress encodes videos locally inside your browser via WebCodecs and WebAssembly. Source code, staging URLs, tokens on screen, and unreleased product UI never leave your machine.

Should I upload an MP4 or an animated GIF to a GitHub PR?

For walkthroughs longer than 5 seconds or clips with high-DPI code/text, H.264 MP4 delivers dramatically sharper text at a fraction of the byte size—plus pause and scrub controls. For 2–5 second silent micro-interactions in README.md files (where inline <video> tags behave differently), use our local Video-to-GIF exporter.