Skip to content

Mute video and remove audio track losslessly

Delete background noise or private audio tracks from MP4, MOV, and WebM clips with zero video quality loss.

Your files are open only in this tab. Nothing is uploaded.

Videos to mute

Remove audio tracks from MP4, MOV, M4V, and WebM clips losslessly without re-encoding video frames.

Drop one or more videos here

MP4, MOV, M4V, or WebM muted locally inside this tab.

How to use Mute video

  1. Add one or more video files. Drop MP4, MOV, M4V, or WebM clips onto Drop one or more videos here, or click Load sample MP4 video to test a built-in clip containing AAC audio and GPS atoms.
  2. Wait for local container remuxing. The Web Worker detects every audio track, copies raw compressed video frames bit-for-bit, and builds a silent fast-start output without touching pixels.
  3. Inspect audio counts and preview playback. Verify the removed audio track badge and byte savings counter on each row, or click Preview to check muted playback inline.
  4. Download single muted video files or a batch ZIP. Click Download muted video on individual rows, or click Download all muted videos (.zip) whenever two or more muted clips are ready.

Your camera, microphone and recordings stay on this device. Nothing is uploaded or streamed anywhere.

Stripping audio from MP4, MOV, and WebM without re-encoding

Removing background chatter, wind noise, or confidential microphone audio should never soften video frames. Modern browsers can strip audio without re-encoding by rewriting container box tables and copying raw compressed video packets directly into a clean silent track inside local memory.

Remuxing H.264, HEVC, VP8, VP9, and AV1 bitstreams

Under the Library of Congress MPEG-4 File Format standard, ISO 14496-14 separates compressed bitstream bytes in mdat from track metadata in moov. When you load an MP4 or MOV file, muteVideoContainer demuxes avc1, avc3, hvc1, hev1, vp09, and av01 video chunks without decoding pixels.

WebM clips follow the same lossless principle by copying V_VP8, V_VP9, and V_AV1 frames alongside CodecPrivate decoder headers through webm-muxer. Before discarding audio permanently from sensitive smartphone recordings, review embedded camera metadata tags with Video Metadata Viewer on your source file.

Preserving video rotation and fast-start moov ordering

Portrait phone clips store a transformation matrix inside tkhd specifying 0, 90, 180, or 270 degrees of clockwise rotation. During clean remuxing, toMuxerRotation copies that orientation straight into the new container header so vertical footage never flips sideways.

Clean MP4 exports also enable fastStart, placing moov ahead of mdat so browsers and mobile players start playback immediately without buffering the end of the file. Every silent output retains original coded width, height, color metadata, and monotonically ordered microsecond timestamps.

Does muting a video strip GPS metadata or reduce sharpness?

Stripping sound leaves pixel sharpness completely untouched because compressed video frames transfer bit-for-bit without decoding or re-quantizing. When clean container remuxing runs, the fresh MP4 muxer omits optional user-data boxes such as QuickTime GPS coordinates and encoder tags, cutting both audio bytes and location metadata together.

Copying compressed video chunks bit-for-bit

In the W3C WebCodecs encoded chunk architecture, encoded video packets remain independent from pixel-level frame decoding once codec configuration bytes are read. Feeding raw mdat video payloads into addVideoChunkRaw prevents re-compressing keyframes and runs far faster than full transcoding.

Because zero video encoding runs, 0 bytes of pixel payload are modified, keeping fine UI text in screen captures crisp down to individual subpixels. If you want to keep spoken commentary separately before silencing the video, extract the original AAC audio stream first.

Clearing udta location tags during clean remuxing

Click Load sample MP4 video to inspect sample-with-gps.mp4, a built-in clip containing H.264 video, 48,000 Hz stereo AAC audio, a ©xyz GPS atom, and an encoder string. Clean container remuxing drops the soun audio track along with udta boxes automatically.

If an unusual MP4 or MOV track layout triggers surgical fallback rebuilding (rebuildIsoContainer) instead of clean remuxing, audio trak boxes and mvex entries still drop cleanly while user-data boxes remain until stripped separately. Each row updates immediately with exact bytes removed.

Container formats, fallback remuxing, and size savings

Container layout dictates whether a clip runs clean muxer rebuilding or surgical moov track removal inside the MDN Web Workers API documentation pipeline. Reviewing each path clarifies codec coverage, metadata handling, and expected byte reductions across supported formats.

Input video layout Worker processing path Output format Audio & metadata outcome Filename & preview
MP4 / MOV (H.264, HEVC, VP9, AV1) Clean demuxVideoContainer + mp4-muxer .mp4 (video/mp4) Drops audio tracks and udta tags <name>-muted.mp4 + inline player
WebM (VP8, VP9, AV1) Clean demuxVideoContainer + webm-muxer .webm (video/webm) Copies CodecPrivate, strips audio <name>-muted.webm + inline player
MP4 / MOV (non-monotonic fallback) Surgical rebuildIsoContainer .mp4 (video/mp4) Drops soun tracks, shifts stco/co64 <name>-muted.mp4 + saved bytes
Silent clip (0 audio tracks) Zero-edit pass-through copy .mp4 or .webm Preserves original bytes (0 bytes saved) Labeled 0 audio tracks (already silent)
Multi-video queue (2+ ready clips) Sequential worker loop + createZip .zip archive Unique -muted filenames per video Bundles into muted-videos.zip

Surgical rebuildIsoContainer fallback walks every preserved trak box in ISO containers and rebuilds 32 bits stco, 64 bits co64, and moof tfhd chunk offsets so video frames play cleanly. When capturing fresh clips that still require camera framing locally, try browser-based webcam video recording.

Tip: Click Preview on any processed row to check silent playback visually before saving. Files without sound immediately show 0 audio tracks (already silent) so you skip redundant exports.

Batch muting multiple clips and exporting muted-videos.zip

Social media editors, QA testers, and field inspectors regularly need to silence dozens of short clips at once. Dropping multiple videos onto Videos to mute processes every file sequentially inside browser memory without uploading raw footage.

Queuing clips locally and inspecting bytes saved

Each file added via drag-and-drop or Choose videos enters a live status queue displaying its video codec badge, number of removed audio tracks, and byte delta. Header summaries automatically aggregate total saved bytes and overall percentage reduction across every completed video in the batch.

Individual rows let you click Preview to toggle an inline muted video player, click Download muted video for single downloads, or remove a row cleanly with automatic blob-URL cleanup. Clicking Clear list releases memory across all queued files immediately.

Packaging deduplicated muted files inside a single ZIP

Once at least 2 videos finish processing cleanly, Download all muted videos (.zip) becomes active in the header toolbar. Passing uniqueFilename ensures duplicate source filenames never collide inside the IANA application/zip media type registry compatible muted-videos.zip archive.

Building the archive executes inside everyday.worker.ts via createZip, keeping UI controls responsive during multi-megabyte exports. If your deployment workflow expects .tar.gz tarballs instead of .zip bundles for Linux servers, repack muted ZIP bundles into offline tarballs directly afterward.

Questions

Does muting a video lower pixel quality or change frame rate?

No. Both clean remuxing and surgical moov rebuilding copy compressed H.264, HEVC, VP8, VP9, or AV1 sample bytes straight from the original video payload. Resolution, sharpness, color space, rotation, and frame timestamps remain bit-for-bit identical to your source clip.

Are smartphone GPS location and encoder tags removed from muted MP4s?

Clean container remuxing through mp4-muxer builds fresh ftyp, moov, and mdat boxes without copying udta or meta atoms, so QuickTime GPS coordinates and encoder app strings are omitted automatically. Only surgical fallback mode preserves original non-audio boxes intact.

What happens if a video already has zero audio tracks?

If container inspection detects zero audio streams, the worker skips remuxing, keeps your file untouched, and labels the row with 0 audio tracks (already silent). Saved bytes report as 0 B while still letting you preview or download the video.

How does batch muting package multiple silent clips into one ZIP?

Dropping two or more videos queues each file sequentially inside the local Web Worker and enables Download all muted videos (.zip). Duplicate filenames automatically receive unique numbered suffixes before createZip bundles every -muted output into muted-videos.zip.

How much smaller does a muted video get after removing sound?

Audio bitstreams typically consume 64 kbps to 320 kbps plus audio sample tables. On short voice-heavy screen recordings or low-bitrate security clips, removing the audio track often trims 5% to 25% of total file bytes immediately.

Why does clean MP4 remuxing enable fast-start moov placement?

Placing the moov index box ahead of the mdat media payload lets browsers and mobile players read frame tables immediately over HTTP without seeking to the end of the file. Clean mp4-muxer output sets fast-start placement automatically on every muted MP4.

Updated