Convert MP4 to ZIP

Barely smaller, and that is expected. An MP4 already holds its contents in compressed form, so general-purpose compression has almost nothing left to find and the archive lands within a few per cent of the total it was given. Pack it anyway for the reasons that have nothing to do with size: one file to send instead of forty, one download, one checksum, and the folder layout preserved on the way out. Almost every MP4 in the wild is H.264 video with AAC audio; the container also legally holds HEVC, AV1 and VP9.

Almost certainly, once it is unpacked. An MP4 is one of the handful of formats a plain browser plays with nothing installed, so the recipient does not need a media player, a codec pack or any particular operating system — unpack, double-click, done. That is worth knowing before you convert the contents to something more exotic for the sake of size: the archive is for moving the files, and moving them is easier when what is inside them is ordinary. MP4 is the safest possible delivery target — every phone, browser, console, editor and Smart TV built in the last decade plays it without extra software. MP4 only supports one widely-honoured subtitle format (mov_text), and multi-track audio is unreliable outside desktop players.

It is the way that survives a bad connection. Sending a few hundred recordings individually fails somewhere in the middle and leaves you working out which ones arrived; packing them into one archive gives a single transfer with a single thing to retry. Names and folder layout come across intact, which matters more than it sounds — a phone names files by date, and that ordering is the only index most people have. Nothing is re-encoded on the way, so what lands is what was recorded.

Not reliably, no. A handful of desktop players will reach inside an archive and play a track from it, but phones, browsers, smart TVs and every streaming device expect a plain file, so the practical answer is to unpack first. That is the trade an archive asks for: it is a container for moving and storing media, not for playing it, and the MP4 that comes out is bit-identical to the one that went in.

Size is the constraint, and it is worth planning around rather than discovering. Video runs to hundreds of megabytes an hour, so a set of MP4 files reaches the per-file upload limit long before the same number of documents would, and the archive that comes back is essentially the sum of its parts because the payload is already compressed. Pack in batches rather than all at once, and check where it is going before you send it: plenty of mail systems refuse anything past twenty-five megabytes whatever is inside it. MP4 is ISO/IEC 14496-14, standardised in 2001 and derived from the same QuickTime box layout MOV uses.

Free conversions have a size limit per file, set by the type of file, and the page tells you when a file is over it. A paid plan removes that limit, so much larger files can be converted.

Several files in one job need a paid plan. Free use is one file per conversion, one conversion an hour. On a paid plan you can add several files to one job, then download each result on its own or all of them in one ZIP.

Yes — the UI is responsive and the conversion pipeline runs server-side, so mobile devices upload-then-download just like desktops. iOS and Android browser file pickers (camera roll, Files app) work end-to-end.

Chrome, Firefox, Safari (15+), Edge, and Opera. The converter uses standard `<input type="file">` upload — no WebAssembly or PWA dependencies — so even older browsers work.