PRIVATE BROWSER PROCESSING
Compress a video around the constraint you actually have
Sometimes the problem is quality. More often it is a 25 MB upload limit, an email attachment, or a phone that does not need 4K. Choose target size or resolution and let the browser do the work.
Video compressor
Compression makes more sense when it starts with a real constraint
Target-size mode estimates bitrate from duration and desired file size. It is designed to land near the target, not promise byte-perfect output; browser encoding can finish slightly above or below.
Privacy and limitations
Processing uses FFmpeg WebAssembly locally. The video is not uploaded by this tool. Closing or refreshing the page clears the working file. Speed depends on the browser, device memory, source codec, duration, and resolution, and tools that re-encode are not lossless.
Common questions
Can I just rename the file extension?
Usually not. Renaming does not change the container or codecs inside; this page performs a real conversion.
Is my video uploaded to DJAI?
No. The source file is read and processed in your browser on your device.
Why can the first run take longer?
The browser downloads an FFmpeg WebAssembly core of roughly 31 MB the first time processing is needed; caching can help later runs.