AscendLab

Video tools

Video Compressor

New ffmpeg.wasm tool

Private Video Compressor

Compress a video locally with quality, resolution, format, and audio controls. FFmpeg is hosted with the site and loads only after you start processing, so the source file stays on your device.

Free ToolFFmpeg loads only when needed
Video Compressor
Compress a local video in your browser with quality, resolution, format, and audio controls. No upload is required.

Drop video here or click to upload

MP4 and WEBM are the safest first-version inputs.

Max file size: 200MB

No video uploaded

Compression settings
Choose output format, quality, resolution, and audio before processing.

H.264 video with AAC audio for broad compatibility.

Output size: No resize needed

CRF 32
Higher qualitySmaller file

Disable for a smaller silent video.

Engine

ffmpeg.wasm

Output

MP4

Audio

96 kbps

Ready0%
Compressed video
Review the output size, format, and local download.

Output size

No compressed video yet

Format

MP4

Size change

Not ready

Upload a video, choose compression settings, and process it to preview the output here.

The video stays on your device. FFmpeg runs in the browser only after you start processing, and the large WebAssembly engine is served from this site.

Quick answer

A video compressor reduces file size by re-encoding the video with a quality and resolution target.

This first version is best for short MP4 or WEBM clips under 200MB.

Best inputs

Short local clips

Browser-side FFmpeg uses local memory and CPU, so short clips finish faster and are more reliable on mobile.

Clear output goal

Choose whether you want a smaller file, a lower resolution, a silent clip, or a more compatible MP4.

Compression method
The tool writes the selected video into browser memory and runs ffmpeg.wasm with your settings.
Higher CRF values usually create smaller files with more visible compression.
Resolution limits reduce pixel count and often reduce output size significantly.
Audio bitrate and silent output controls can reduce size for clips where sound is not required.
Example, Assumption, and Limitation
Use the result as a practical estimate or transformation, then confirm edge cases for critical work.

Example

Upload a 120MB MP4, choose MP4 output, set CRF 32, limit resolution to 720p, and export a smaller file for web upload.

Assumption

The browser has enough memory to load the source video and ffmpeg.wasm. Smaller files are more reliable on phones.

Limitation

Browser-side video compression is not a replacement for desktop batch encoding, professional mastering, or very large video files.

Common use cases
These pages are built for lightweight browser-side work, examples, and planning.

Upload limits

Reduce a clip before sending it through a form, chat, or content management system.

Mobile sharing

Lower resolution and audio bitrate when a smaller file matters more than full quality.

Silent previews

Remove audio from short previews when the destination does not need sound.

Web publishing

Prepare a smaller MP4 or WebM for pages, docs, and product updates.

Frequently asked questions

Does this video compressor upload my file?

No. The selected video is processed in your browser with ffmpeg.wasm. The current tool does not send the video to a backend.

What file size should I use?

The first browser-side version accepts videos up to 200MB. Smaller files are recommended on mobile devices because compression uses local CPU and memory.

How do I make the video smaller?

Use a higher CRF value, lower the resolution, lower the audio bitrate, or remove audio when a silent result is acceptable.

Why can the output sometimes be larger?

Re-encoding can increase size when the source was already heavily compressed, the selected quality is high, or the new codec is less efficient for that clip.

Suggested workflow

Build a browser-side video optimization workflow

Compress the clip, convert format when needed, then extract the cover image for publishing.