Screen recordings compress well
Most of a screen recording doesn’t move: the window frame, the sidebar, the text you aren’t editing. Video codecs only spend data on what changes, so a two-minute UI demo can stay readable at 1080p inside 10 MB, where a two-minute sports clip could not.
If text in your recording looks blurry after compressing, keep the resolution at 1080p and shorten the clip rather than lowering the resolution. Small text is the first thing to suffer at 480p.
Formats GitHub accepts
GitHub plays MP4, MOV and WebM attachments. ClipFit outputs H.264 MP4, which plays in the GitHub web player in every browser and in the mobile app.
On paid GitHub plans the limit is higher. Set a custom target size to match your plan if you need more detail.
A tidy workflow for bug reports
Record only the steps that reproduce the problem, compress the clip here, then drag the MP4 into the issue. Keeping recordings under 30 seconds makes them easier for reviewers to watch, and they’ll look noticeably sharper.
Private by design
ClipFit processes your video inside your browser using FFmpeg compiled to WebAssembly. The file is never uploaded, so there’s no waiting for transfers and no copy left on a server. Once you close the tab, nothing remains.
Questions
Is my screen recording uploaded anywhere?
Not by ClipFit. The video is processed in your browser and stays on your computer until you upload it to GitHub yourself. That matters when recordings show private code or customer data.
Can I also make a GIF?
ClipFit outputs MP4, not GIF. An MP4 is usually 5–10 times smaller than a GIF of the same clip and looks better, and GitHub plays it inline.
My recording is from macOS and ends in .mov. Is that OK?
Yes. MOV files from the macOS screenshot tool or QuickTime are converted to MP4 as part of compression.
Will the video play inside the pull request?
Yes. Once uploaded, GitHub shows MP4 attachments with an inline player in issues, pull requests and comments, so reviewers don’t need to download anything.