Is The Video Uploaded?

No. The media file stays in the current browser session. The processing code downloads on first use, but the source video is not sent to that provider.

Will Target Size Be Exact?

No. This local one-pass workflow calculates a bitrate target, but source complexity and encoder behavior can finish above or below it. The final result reports the real size.

Why Can A Codec Fail?

The browser loads a bounded FFmpeg WebAssembly build. Its available decoders and encoders can differ from a desktop FFmpeg installation, and large files can exceed browser memory.

Video Compressor

Compress video locally with quality or approximate-size targets, MP4 or WebM output, resolution and audio controls, and an export receipt.

Local processing: your media stays on this device.First export downloads about 31 MB of FFmpeg WebAssembly

01 · Source

Source Video

Open a browser-readable video, then balance size, resolution and quality.

Drop a video hereor choose a local file · maximum 250 MB / 30 minutes

02 · Settings

Output Controls

Settings are validated before the runtime starts.

Size Control

Quality (CRF 24)Lower values retain more detail and create larger files.Output ContainerMaximum HeightFrame RateAudio Bitrate

Remove Container Metadata

03 · Output

Output Workspace

The completed file and processing receipt will appear here.

Open a source, confirm the settings, then run Compress Video.

Codec note: exports run in FFmpeg WebAssembly after a first-use download of about 31 MB. The 250 MB / 30 minutes picker ceiling is not a success guarantee: the complete source and output occupy browser memory, available decoders vary, and large 4K or unusual-codec media may still fail. Processing uses a duration-aware 5–45 minute job timeout. Fast trimming follows source keyframes and is not frame-perfect; re-encoded timing can still vary slightly on variable-frame-rate media.

Loading Tool…

What Is the Video Compressor?

The Video Compressor is a private local delivery transcode workspace. It can encode MP4/H.264/AAC or WebM/VP9/Opus, keep or reduce the source resolution and frame rate, adjust audio bitrate, remove container metadata, use constant-quality encoding or approximate a requested file size, and export a JSON processing receipt.

How It Works

Open a video that the browser can inspect, choose constant quality or a target-size approximation, set the output container, dimensions, frame rate and audio bitrate, then review the planned output before processing. The first export downloads about 31 MB of FFmpeg WebAssembly; the source itself remains on the device.

When to Use It

Use it to prepare smaller review copies, web uploads, email attachments and delivery proxies. Target size is an estimate rather than a guarantee, and browser memory plus the available FFmpeg WebAssembly encoders limit very large or unusual sources.

Frequently Asked Questions

Is The Video Uploaded?: No. The media file stays in the current browser session. The processing code downloads on first use, but the source video is not sent to that provider.
Will Target Size Be Exact?: No. This local one-pass workflow calculates a bitrate target, but source complexity and encoder behavior can finish above or below it. The final result reports the real size.
Why Can A Codec Fail?: The browser loads a bounded FFmpeg WebAssembly build. Its available decoders and encoders can differ from a desktop FFmpeg installation, and large files can exceed browser memory.

Found an issue? Send Feedback. See our data sources and update policy for tools that depend on changing information.