Discord Compressor

Works out the exact video bitrate that fits a clip under a size cap, then runs a two pass H.264 encode in your browser to hit it. It reads the length of the video, holds back a margin for container overhead, pays for an AAC audio track at 96, 64, or 48 kbps depending on how tight the budget is, and hands the rest to the picture. The presets cover the common Discord caps, and a custom field takes any size up to 2000 MB for other upload limits. When a cap genuinely cannot hold the clip, it says so with the numbers instead of producing something unwatchable.

Drop a video in and the tool reads its length, then shows the plan before anything is encoded: target size, video and audio bitrate, and the estimated result. Pick a cap, optionally cap the height or the frame rate to buy more bits per pixel, then press Compress. Pass one analyses the clip and pass two encodes it, and the finished file is checked against the cap and reported as either the headroom it left or an honest overshoot. Very large sources are limited by how much memory the browser tab can hold, so an hour of 4K may not load even when the math says it would fit.

The popular discord-size sites upload your video to their servers, re-encode it with one fixed setting, and hand back whatever comes out, which is why the result is often far under the cap and softer than it needed to be. This one computes the bitrate for your exact clip length and cap, shows you the plan before it runs, and does the encode with ffmpeg inside this tab: your files and inputs never leave your device. No queue, no watermark, no account.

Why does it encode twice?

A hard size target needs accurate rate control. On a single pass the encoder is guessing how much of its budget the rest of the clip will need, so a still opening and a busy ending can leave the file well under or over the target. The first pass encodes nothing but statistics about where the motion and detail actually are, and the second pass spends the budget against that map, which is what makes the finished size land close to the number that was planned.

What do I do when it says the cap cannot hold the clip?

That message appears when the budget leaves under 100 kbps for video, which is the point where H.264 stops resolving anything. Three things buy real bits back: cap the resolution (480p over 1080p is roughly a quarter of the pixels), cap the frame rate at 30, or shorten the clip, since the budget is divided by its length. If none of those are acceptable, a larger cap is the only honest option.

Is my video uploaded anywhere?

No. The encoder is a WebAssembly build of ffmpeg that runs inside this tab: your files and inputs never leave your device. The engine itself is a one time download of about 31 MB that your browser keeps, so later visits start it from the cache.