Compress a Video to 100MB
The last stop before 'just send a link' — 100MB, hit exactly in your browser.
Runs entirely in your browser. Your videos never leave this device.
100MB is GitHub's hard per-file limit and the default attachment cap in Confluence, and plenty of CMS and portal upload forms stop at the same round number. (Signal messaging sat at 100MB for years too, before moving to 200MB in 2026.) Pick the 100MB target and the encoder computes the exact bitrate from your video's duration — processed locally in your browser, never uploaded.
How do I compress a video to under 100MB?
Drop the video into the compressor, choose the 100MB target, and download the finished MP4 — nothing is uploaded, because the encoder runs inside your browser. It calculates the exact bitrate from the video's duration to land just under 100MB, and automatically re-encodes at a lower rate if the first pass overshoots.
The facts that matter
| Who caps at 100MB today | GitHub (hard per-file limit), Confluence Cloud attachments (default), many CMS and portal upload forms |
|---|---|
| 2–3 minutes at 100MB | ≈4.4–6.7 Mbps — good 1080p |
| 5 minutes at 100MB | ≈2.7 Mbps — good 720p, passable 1080p |
| 10 minutes at 100MB | ≈1.3 Mbps — clean 480p, decent 720p |
| 20–30 minutes at 100MB | ≈440–670 kbps — soft 480p; fine for screen recordings, rough for camera footage |
| Output | MP4 (H.264 + AAC), aspect ratio and frame rate preserved |
Get a better result
- Trim before you compress — cutting three minutes off a 20-minute video buys the rest a visibly better picture.
- Screen recordings compress far better than camera footage; the same bitrate goes much further on static frames.
- Committing to GitHub? Anything you can keep well under 100MB also keeps clones fast — smaller is kinder to the repo.
- Large source file? Close heavy tabs first; the encoder works entirely in your browser's memory.
- Use the batch queue for multi-part recordings — each part is encoded to its own target, one after another.
Frequently asked questions
What quality does 100MB give me?
For most everyday videos, plenty. Up to five minutes you get 2.7 Mbps or better — good 720p, and passable 1080p. Ten minutes still gets about 1.3 Mbps, which holds up well at 720p for calm footage. Only past twenty minutes does the budget get thin, dropping toward 500 kbps.
Can I fit a 30-minute recording under 100MB?
Yes, at around 440 kbps — and whether that's acceptable depends on the content. A screen recording or slide presentation stays legible because static frames compress efficiently; fast-moving camera footage at that rate looks rough. If it's camera footage, trim it or split it into parts.
Why not just upload the original somewhere and share a link?
Sometimes that is the right call — but when the destination itself enforces the cap (a GitHub repo, a Confluence page, a portal form), the file simply has to be under 100MB. This tool exists for exactly that case, and it gets you there without pushing the original through anyone's server first.
How long does compressing take?
Longer than a desktop app, honestly — encoding runs at browser speed. Short clips finish quickly, but a half-hour recording can take a good while depending on your machine. You can queue several files and let them process one at a time.
My original is over 1GB — any issues?
It can work, but files past roughly 1GB can strain browser memory since the entire job runs on your device. Free up memory by closing other tabs, or split the video into parts and compress them separately.
What happens if the output lands over 100MB?
The tool verifies the finished file's real size and, if it overshot the target, automatically retries at a lower bitrate. You get a file that's genuinely under the cap, not approximately under it.
Does the tool watermark or re-crop my video?
No watermark, ever, and no cropping — the aspect ratio is always preserved and the source frame rate is kept. The output is a standard MP4 (H.264 + AAC) that plays anywhere.