Mute video

No. The video track packets are copied across untouched and the audio track is simply not added to the output, so the picture comes out bit for bit identical. Nothing is decoded, which is why this runs in Node, on the command line and through MCP, not only in a browser tab.

It removes the track entirely. There is no volume option, so the result has no audio stream at all rather than a silent one. That makes the file smaller by whatever the audio was costing. If you want the sound kept but rebalanced, use Normalize audio volume instead.

You still get a file, and the tool tells you: "had no audio track to begin with", printed alongside the result. It is a note, not an error, so a batch of mixed files does not stop halfway through. The output is still written, so you get a clean MP4 with the video copied across.

Always MP4, named after your input with -muted.mp4 on the end. A WebM or MOV input is remuxed into MP4 with its video codec unchanged. Rotation metadata from the source is carried over so the orientation is preserved. The audio track is left out entirely rather than silenced, so the file is smaller by whatever the sound was costing.

Yes. The tool works per file, so drop as many as you like and each one comes back as its own muted MP4. They are processed one after another, and each result is named from its own source file. Each run is a packet copy, so a batch goes quickly, though every file is still read into memory when its turn comes.

No. The file is read into memory on your device and the new MP4 is written in memory next to it. Nothing is sent to a server. Because both live in memory at once, large videos are limited by your browser tab rather than by any size rule in the tool.