Video & audio engine (FFmpeg in your browser)
Everything is processed on your own device — files are never uploaded. The engine is a ~25 MB one-time download that your browser caches for future visits.
Why does this tool need an "engine" — and why is it safer?
A 30-second explanation of what's actually happening.
Why the engine?
Browsers can play video, but they can't re-encode it — converting MP4 to WEBM or compressing a clip needs a real codec toolkit. That toolkit is FFmpeg, the same open-source engine inside VLC, YouTube's pipeline and most editing software. We ship it as a ~25 MB WebAssembly file your browser downloads once, caches, and then runs like any other page script. It's a bigger first click than a normal tool — but after that, everything works instantly and even offline.
Why local processing is safer
Typical online converters upload your file to their server, convert it there, and let you download the result — meaning your private videos, voice notes and screen recordings sit on someone else's machine, subject to their retention policy, staff access and breach risk. Here the file never leaves your device: it's read into your browser's memory, processed by the engine on your own CPU, and handed back as a download. Close the tab and everything is gone. There's nothing for us to store, leak, sell or get subpoenaed for — we literally never receive it. It's also why there are no file-size fees, upload queues or "premium speed" tiers: your hardware does the work.
You can verify this yourself: open your browser's DevTools → Network tab while converting. After the one-time engine download, you'll see zero requests during processing.
The rest of the suite
Images and PDFs have dedicated tools — all client-side too.
Convert video and audio in your browser — no uploads
This media converter runs FFmpeg — the same engine behind most professional video software — compiled to WebAssembly, entirely inside your browser. Convert MP4, MOV, AVI, MKV and WEBM video or MP3, WAV, AAC, FLAC, OGG, OPUS and M4A audio; compress with quality control; trim clips; rotate; mute; boost volume; extract audio from video; export frames; or turn any clip into a GIF. Because processing is local, private footage and voice notes never touch a server.
How it works
Click "Load the engine" once — a ~25 MB WebAssembly build of FFmpeg downloads and is cached by your browser. After that, files are read into your device's memory, processed, and handed back as downloads. Nothing is stored anywhere; closing the tab wipes everything automatically.
Frequently asked questions
Why is there a file-size limit?
The whole file must fit in browser memory. Up to ~900 MB works on most laptops; phones handle less. For bigger files, desktop software is the right tool.
Why is conversion slower than desktop apps?
WebAssembly runs FFmpeg at roughly half native speed and single-threaded for compatibility. A 100 MB video typically converts in a few minutes.
Is anything uploaded or stored?
No. The only network request is the one-time engine download from a public CDN. Your files stay in your browser's memory and are cleared when you leave.