Why this is the fastest video compressor on the web
Browser-side compressors (ffmpeg.wasm) run x264 single-threaded with a ~2 GB cap, often 5–10× slower than native ffmpeg, and they crash on big phone clips. We rebuilt the pipeline: presigned upload to the nearest Backblaze B2 POP, native server-side ffmpeg x264 encode tuned for the preset target, output delivered through Bunny CDN. A 1-minute 1080p clip typically clears in 10–20 seconds.
Picking a preset by destination
If you're emailing the clip, start with Smaller — Gmail's 25 MB attachment ceiling is the most common hard wall. For a Discord free channel, same answer (25 MB cap). Slack tolerates up to 1 GB on free workspaces, so Balanced is plenty and keeps the quality reasonable. For X (Twitter), the format ceiling is 512 MB and 140 seconds — Balanced lands almost any short clip comfortably under both. For Notion, Loom-style hosting, or anywhere you have headroom, Best quality just produces a more efficient re-encode of the original.
Why H.264 instead of H.265 or AV1
H.265 is roughly 30% smaller at the same quality. AV1 is better still. Neither is universally supported. PowerPoint refuses H.265 on most Windows machines, older phones choke on AV1, and half the social platforms transcode unfamiliar codecs back to H.264 on upload anyway. We ship H.264 because every player has supported it since 2008 — the compressed output will play wherever the source did.
Skip compression by recording smarter
If your goal is "send a video to a coworker without it being huge," record with Clipy from the start. The recording is uploaded to a hosted, autoplay-friendly link as you record — your coworker opens the URL, no file changes hands, no compression needed.
Sister tools
Already have an MP4 and need a different aspect ratio or dimensions? Resize video. Need to clip out the silence first? Trim video and crop video handle that step with the same server-side ffmpeg. Going to GIF instead? MP4 to GIF converter uses a two-pass palette pipeline.