Skip to tool

Categories

VideoTrim

Trim, mute or take the sound out of a video

The picture is never re-encoded. The frames you keep are copied across exactly as they were, so a trimmed clip is not a lower-quality copy of your video — it is the same frames in a smaller file. MP4 and MOV, in the tab you are looking at.

Runs in this tab

MP4 and MOV only. WebM and Matroska store their index in a different format entirely and are refused by name rather than failing oddly.

Remove audio track from MP4 or MOV videos instantly without re-encoding. The trim, the mute and the audio extraction copy compressed frames across, so they lose nothing at all. The GIF is the exception and the only one that does: it has to decode and re-encode, and a GIF holds at most 256 colours, so its output is genuinely worse than its input. That is the format rather than the tool.

Related Video Tools

About this video muting tool

Select an MP4 or MOV video file up to 2 GB and click Mute Video. The audio track is omitted from the container header, outputting a clean, silent MP4 video in milliseconds with zero quality loss and no watermark.

Removing background noise, wind rumble, or unwanted commentary from a video before sharing on social media typically requires importing the video into complex video editors or uploading to cloud converters that re-encode every frame. This tool performs instant container surgery: it reads the video track and writes a new container without the audio track atom. The video frames remain completely untouched.

Runs in this tab — no uploadFree, no account, no watermark

Step by step

  1. 1Select video with audioChoose an MP4 or MOV video file. The demuxer verifies video and audio track allocations.
  2. 2Optionally set clip rangeSpecify start and end cut points if you want to trim the silent clip simultaneously, or leave blank to mute the entire video.
  3. 3Remove audio trackClick Mute Video. The engine packages the video stream into a new MP4 container while excluding the audio track.
  4. 4Download muted videoSave the silent video file immediately. Export finishes in milliseconds with 100% original video resolution and bitrate.

Why container surgery muting beats video re-encoding

Standard video editors mute video by decoding both picture and audio, stripping the audio waveform, and running the picture through an encoder again. Re-encoding 1080p or 4K video takes minutes, heats up your computer, and noticeably softens fine image textures. In contrast, our container muting engine simply omits the audio track box (trak) and handler (hdlr) from the movie header (moov). The compressed video frames in the media data box (mdat) are preserved byte-for-byte.

Instant turnaround on social media clips

Whether you are preparing B-roll footage, silent product demos, or background website video headers, muting via container surgery takes under 100 milliseconds even on 4K clips. Because audio data is stripped, the output file size is slightly smaller than the original.

Streaming zero-copy memory safety

Using our streaming ByteSource architecture, the tool processes large videos without buffering gigabytes of video frames into browser memory. Video packet ranges are assembled directly into a download Blob via zero-copy file slices.

Container structure and media data decoupling

In the ISO Base Media File Format, audio and video samples reside inside the media data box (mdat), while track indexing tables reside in the movie box (moov). Muting a video does not require modifying or rewriting media data samples on disk; the engine simply builds a new movie atom that registers only the video track, allowing players to play the video track cleanly while ignoring audio bytes.

Zero upload security guarantee

Every response from this site is served with a Content Security Policy whose connect-src directive is set to none. That is not a promise in marketing copy; it is an instruction to your browser, and the browser is the one enforcing it. While this page is open it cannot open a connection to anywhere — not to this site, not to anyone else — so there is no path by which your document could be uploaded, not by a bug, not by a future change, not by a script that should not be here. e2e/egress-proof.spec.ts asserts the served header and then tries to send data out by every route a page has and requires each attempt to be refused, and it runs on every build.

The second half of the guarantee is that the code has nowhere to send anything from. lib/tools/local-source-policy.test.ts reads every source file under lib/tools, workers, components and app on every test run and fails the build if any of them contains fetch, XMLHttpRequest, WebSocket, EventSource, sendBeacon or a peer connection, or even a remote address written down in a comment. A tool here cannot acquire an upload by accident, because the file that would have to contain one cannot be committed.

Client-side processing limits

Computations run directly on your own device using WebAssembly, Web Workers, and modern browser APIs including Web Crypto and TextDecoder. There are no server queues, no background telemetry, and no temporary cloud files created. Large operations remain responsive by offloading heavy parsing and conversion tasks to dedicated worker threads, ensuring the browser UI never freezes during intensive document and data processing tasks.

Questions people ask

Does muting a video reduce its picture quality?
No. The video stream is copied byte-for-byte without re-encoding, so the picture quality is 100% identical to the source recording with zero degradation.
Can I trim the video while muting it?
Yes. Set start and end cut points to trim and mute the video in a single instant step, saving time and storage space.
Does the output file have a smaller file size?
Yes. Removing the audio track reduces the total file size by the exact size of the stripped audio bitstream, making downloads slightly smaller.
What video file formats are supported?
MP4 and MOV video containers are supported with instant zero-copy in-browser audio removal.
Are my private videos uploaded to any server?
Never. All processing executes 100% locally in your browser under strict connect-src none Content Security Policies with zero telemetry.