Short answer
These video tools run entirely inside the web browser using a WebAssembly build of FFmpeg. Because the processing is local, files are never uploaded to a server, there is no file size limit imposed by the service, no account is required, and no watermark is added to the output.
Make a video file smaller without a visible drop in quality.
Extract the soundtrack from a video as a plain MP3 file.
Turn a few seconds of video into a shareable animated GIF.
Keep only the section of a video you actually need.
Change a video's resolution or reshape it for a specific platform.
Remove the sound from a video without re-encoding the picture.
Fix a video that was recorded sideways or upside down.
Convert iPhone and QuickTime MOV files into universally playable MP4.
Convert web-native WebM files into MP4 that editors and phones accept.
Modernise legacy AVI files into smaller, widely supported MP4.
Convert MKV to MP4 — usually instantly, and without quality loss.
Convert video to WebM for smaller, faster-loading web pages.
Most free online video tools work by uploading your file to a server, processing it there, and giving you a download link. That model forces file size caps, queues at busy times, watermarks on free tiers, and the uncomfortable fact that a copy of your video now sits on someone else's disk.
These tools take the other approach. A WebAssembly build of FFmpeg is loaded into the page and runs on your own hardware, so your file never leaves the device. The trade-off is honest: encoding is slower than a native desktop application, and very large files are limited by your available memory.
Yes. There is no paid tier, no watermark, no daily limit and no account. The processing runs on your device, so there are no server costs to recover per file.
No. Every tool processes the file inside your browser. You can verify this by opening your browser's network panel, or by disconnecting from the internet after the page has loaded — the tools keep working.
There is no limit imposed by the service. The constraint is your device memory. Files up to roughly 500 MB are comfortable on a typical laptop; phones handle much less.
The encoder runs as WebAssembly on a single thread inside a browser sandbox, which is several times slower than native multi-threaded software. Nothing needs to be installed in exchange.
Once the page and the encoder have loaded, yes. The engine is cached by your browser and requires no further network access to process files.
