Video Compressor screenshot

Video Compressor

Shrink a video with H.264 at CRF 28 and at most 1280 pixels wide, and see the byte counts before and after.

Privacy First
0 Runs
Updated 2026-11-07
Runs on the tool server
No account needed
The upload is not stored
The output is probed

What the compressor changes

It re-encodes with H.264 at CRF 28 and the veryfast preset, scaling the long edge to at most 1280 pixels and the audio to AAC at 96 kbit/s. CRF, rather than a fixed bitrate, means the encoder spends bits where the picture needs them, so a still scene gets cheap and a busy one gets the detail it needs.

The summary reports the input and output byte counts and the percentage saved, plus the durations and frame sizes. When the re-encode comes out larger — which happens with a clip that was already efficiently encoded — the page says so instead of calling it a saving.

How to use it

Choose a video and press Run. Compare the two byte counts in the summary; if the result is not smaller, the original is the better file and the page tells you that in the same sentence.

Limits

20 MB in, 2 minutes of duration, 24 MB out, 180 seconds of processing. A longer or larger clip is refused with the measured value.

Honest about the trade-off

This is a lossy re-encode at a fixed quality target, so detail in high-motion footage is the first thing to go. It is a good default for a file that must fit a size limit; it is not a way to keep a master copy.

Upload a video and the server re-encodes it with H.264 at CRF 28, scaled to at most 1280 pixels on the long edge, with AAC audio at 96 kbit/s, then reports the byte counts before and after and the percentage saved.

The upload is validated by reading the container, not by trusting the file name: ffprobe must decode it and find a stream before any encoder starts. A text file named video.mp4 therefore fails at the same point a real video would pass.

Compression is a re-encode, so it is not lossless. A video that is already small can come out larger, and the summary says so in words rather than reporting a negative saving as a success.

The limits and the pipeline

The input may be up to 20 MB and two minutes of container duration; both are checked before encoding. The output is capped at 24 MB, checked from the file on disk before it is read, and one encode has 180 seconds.

The picture is scaled so the long edge is at most 1280 pixels, then encoded at CRF 28 with the veryfast preset and yuv420p. Audio is re-encoded to AAC at 96 kbit/s, and the MP4 is written with its index first so it can start playing before it is fully downloaded.

  • Input: 20 MB, 2 minutes
  • Output: H.264 CRF 28, at most 1280 px wide
  • Audio: AAC 96 kbit/s

What the saving figure means

The percentage compares the uploaded bytes with the produced bytes. It is a file-size measurement, not a quality score; two clips of the same length and size can look very different at the same CRF because the encoder spends bits where the picture is busy.

The produced file is probed again and must carry a video stream, so a zero exit code alone is not accepted as success. The temporary directory is removed whether the run succeeded, was refused or timed out.

How to use the upload

Choose a clip of at most 20 MB and two minutes in the Upload step and press Run; ffprobe validates the container before any encoder starts. The server scales the long edge to 1280 pixels, re-encodes at CRF 28 with AAC audio, and returns the MP4.

Read the summary's byte counts before and after with the percentage saved: that figure is the file-size result, not a quality grade. A refusal names the measured limit that was hit, so check size and duration first when a run does not start.

What to Expect

Best for

  • Shrinking a short clip for an email or a chat
  • Reducing a screen recording to a shareable size
  • A predictable H.264 file that plays widely

Not ideal for

  • A clip longer than two minutes or larger than 20 MB
  • Keeping the original quality at a smaller size
  • A video whose codec cannot be decoded by ffprobe

What this tool keeps

  • The full duration, with no trimming
  • The aspect ratio, scaled to the 1280-pixel long edge
  • An audio track when the input had one

What may need cleanup

  • Visible compression on a busy or dark scene
  • A file that is larger than the input because it was already efficient
  • The audio bitrate, which is fixed at 96 kbit/s

Common errors

  • Uploading a 30 MB clip and reading the size refusal as a codec problem
  • Expecting a lossless result from a re-encode
  • Assuming every upload shrinks, even one already compressed

Example use cases

  • Sending a short clip in a message
  • Shrinking a phone recording for a form
  • Producing a widely playable MP4

Sample input

A 12 MB, 40-second phone clip uploaded for compression.

Sample output

An H.264 MP4 at most 1280 pixels wide with AAC audio, and a summary giving both byte counts and the percentage saved.

Who this is for

  • Anyone sending a short video
  • Support staff preparing an attachment
  • Content creators making a smaller preview

Frequently asked questions

How does the video compressor reduce size?

It re-encodes with H.264 at CRF 28, scales to at most 1280 pixels on the long edge, and uses AAC audio at 96 kbit/s.

What are the limits?

A clip longer than two minutes or larger than 20 MB is refused.

Why is the output sometimes larger?

An already efficient source can grow when it is re-encoded, which the reported byte counts show.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.