Video & Audio Tools

Turn WebM and MOV into broadly compatible MP4 video, or create MP3 listening copies from MP4, WebM, M4A and WAV — every output checked with ffprobe.

Advertisement

A documented compatibility profile, not an extension rename

These tools cover the six media jobs most often blocked by format support: browser-recorded WebM and camera MOV to H.264/AAC MP4, plus MP3 listening copies from MP4, WebM, M4A and WAV. FFmpeg performs a real decode and re-encode; changing a filename is never treated as conversion.

Every job is inspected before and after conversion. The input extension must agree with its byte signature, ffprobe must find the required stream, and the completed output must reopen with the promised codec, decode from start to finish and stay within a duration difference of 250 ms or 1%. The download page exports the evidence as JSON or CSV, while a six-case synthetic dataset publishes the same checks independently.

Advertisement

Frequently asked questions

Why do these media tools run on the server?

Native FFmpeg is materially faster and more reliable than loading a large WebAssembly video engine into every browser tab. Before you choose a file, each page discloses the HTTPS upload, 100 MB input and 160 MB output caps, 10 minute stream limit, 8 minute request deadline, isolated temporary directory and cleanup behaviour.

Are media conversions lossless?

No. MP4 output is H.264 CRF 23 with AAC audio; MP3 output is 192 kbps stereo. Those are practical compatibility profiles, not archival masters. Keep the source and inspect fine text, fast motion or quiet audio before distribution.

What is not carried into the result?

The first relevant video and audio streams are used. Alternate languages, subtitles, chapters, cover art, attachments and container metadata are removed; encrypted/DRM content is never bypassed.