ReelSDK's free video compressor runs ffmpeg in your browser, so the file never leaves your device. The default Balanced 720p setting made our 5.5 MB sample clip 80% smaller; the API does it for $0.02 per compute minute.

Compress a video for free: no upload, no watermark

Pick Smallest, Balanced or Best quality and 1080p, 720p or 480p; it is the same command the ReelSDK API runs from code. You get an MP4 that plays everywhere and starts at once, from files up to 2 GB, with no sign-up.

ToolsUpdated

or drop it here

MP4, MOV, WebM or MKV. It stays on your device.

No video at hand?

Runs on your device with the ffmpeg.wasm core 0.12.10 (FFmpeg 5.1.4), GPL-2.0-or-later: source code, our mirror

At a glance

Size and time by setting

Each row compresses our 5.5 MB, 11-second vertical sample in Chromium on our test PC (AMD Ryzen 9 5900X).

Size and time by setting
SettingResultSmaller byTime
Smallest, 720p0.8 MB86%39 s
Balanced, 720p (default)1.1 MB80%40 s
Best quality, 720p1.9 MB65%44 s
Balanced, 480p0.7 MB88%25 s
Balanced, original 1080p2 MB64%1 min 9 s

Source: our runs of the sample clip, checked November 2026.

What the settings change

The tool re-encodes your video with x264 at a constant quality, set by the CRF number: Smallest uses CRF 32, Balanced 28 and Best quality 23, the x264 default. The ffmpeg H.264 guide puts the sane range at 17 to 28, and says that adding 6 to the CRF roughly halves the file size.

Resolution often saves more than quality does. Balanced at 480p came out smaller than Smallest at 720p in our runs, at about 0.7 MB against 0.8 MB, and still looks sharp on a phone. Resolution sets the short side, so a vertical 1080x1920 clip at 720p becomes 720x1280. Sound is re-encoded to AAC at 128 kbps.

Why it takes a while

Your browser runs the encoder on one CPU core, with no help from the graphics card. On our test PC, Balanced at 720p took about 40 seconds for the 11-second clip, close to 4 seconds of work per second of video, so keep the tab open on long videos.

We use the x264 veryfast preset. On 3 seconds of 1080x1920 video in this tab, ultrafast was nearly 3 times as fast as veryfast but made a file almost 4 times bigger. The guide's rule holds: "A slower preset will provide better compression".

Your video stays on your device

Compression happens in this tab, with FFmpeg 5.1 built for WebAssembly. In our network log, the page fetched the 2 engine files and no request carried any part of your video. The engine is a 10.3 MB download (32.2 MB unpacked) that your browser keeps for 7 days.

For videos your app compresses on its own, the API below runs the Balanced 720p command on ffmpeg 8.1. It finished in about 7 seconds and costs $0.02 per compute minute; see pricing.

From your code

The same job as one API call

Shrink a video in your browser with a size and resolution you pick, free and without uploading it, or with one API call.

terminalTry it
curl "https://api.reelsdk.com/v1/ffmpeg?wait=60" \
  -H "Authorization: Bearer $REELSDK_KEY" \
  --json '{
    "inputs": {
      "clip.mp4": "https://api.reelsdk.com/f/lib/demo/clip.mp4"
    },
    "args": [
      "-i", "clip.mp4", "-vf", "scale=720:-2", "-c:v", "libx264", "-preset",
      "veryfast", "-crf", "28", "-pix_fmt", "yuv420p", "-c:a", "aac", "-b:a",
      "128k", "-movflags", "+faststart", "clip-compressed.mp4"
    ],
    "outputs": ["clip-compressed.mp4"]
  }'
The API compressed the 5.5 MB sample to 1.1 MB at 720x1280 with the Balanced 720p settings, in about 7 seconds.Input: 10.7-second sample clip

FAQ

Questions, answered

Is this video compressor free?

Yes. There is no signup, no watermark and no cap on how many videos you compress, because your own device does the work. Compressing from your own code with the API costs $0.02 per compute minute.

Is my video uploaded?

No. The file is read inside your browser and the smaller MP4 is made there. In our network log, the page fetched the 2 engine files and no request carried any part of the video.

How much smaller will my video get?

It depends on the video. Our 5.5 MB sample shrank by 80% at the default Balanced 720p setting and by 88% at Balanced 480p. Phone videos are filmed at high bitrates and usually shrink a lot, while a video that was compressed before may barely change.

Why is it slower than a desktop app?

A browser tab gets one CPU core and no graphics card encoder. The API is the fast lane: the same Balanced 720p job ran on ffmpeg 8.1 and finished in about 7 seconds, against 40 in the browser on our test PC.

Ready to build?

Ship video from your app today

Your first $0.50 is free, and one key covers every endpoint.

Moonlit lake with a lit cabin under the mountains