Before—
After—
Saved—
Video—
Muting a video should cost nothing. The sound is a separate track inside the file, so taking it out means writing the picture through untouched and leaving the audio behind — no decoding, no re-encoding, not a single frame changed. Plenty of tools re-encode anyway, which makes a free operation slow and slightly damages the picture in the process. There is also a second question nobody asks: whether you want the audio track *gone* or *silent*. They produce different files, and some upload pipelines accept only one of them.
Step by step
01Open the clip
MP4, MOV, WebM, or MKV. The tool reports what the audio track actually is — codec, channels, sample rate — before it removes it.
02Choose removed or silent
Removing drops the track and makes the file smaller by exactly what the sound was costing. Keeping a silent one leaves a track of the same length carrying nothing.
03Check that the picture was copied
The ledger says whether the video was written through untouched or re-encoded. On any file the browser can read, it should be untouched.
04Take the file
The size row shows what the audio was worth in this particular file — usually a fifth to a twentieth of it, depending on how heavily the picture is compressed.
A worked mute
The sample clip this tool opens with: ten seconds of 640×360 video with a mono Opus track, 135 KB, generated in the browser. Both options, on the same file.
Given
The two kinds of mute
remove the track 102 KB −24% nothing left to recover
keep it, silent 106 KB −21% a 4 KB track of nothing
video frames re-encoded, either way: 0The audio was 24% of this file, which is high because the sample's picture is small and lightly compressed; on a 1080p recording the sound is nearer a twentieth and removing it barely moves the size. The number worth taking away is the last one: zero frames re-encoded. Muting is a container operation — the video packets are copied across byte for byte — so a muted clip is bit-identical in picture to the original. Any tool that takes minutes to mute a video, or hands back something visibly softer, is re-encoding for no reason. And the four-kilobyte silent track is not a rounding error but a purpose: an editing timeline or an upload pipeline that expects an audio track will handle it correctly, where the removed version can be refused outright.
Before you mute
Sound and picture are separate tracks
A video file is a container holding independent streams. Removing one is a matter of writing a new container around the other — which is why muting can be instant and lossless, and why it should never make the picture worse.
Removed and silent are not the same file
Removing the track leaves nothing to recover and makes the file smaller. Keeping a silent track leaves a stream of the same length carrying no sound, and costs a few kilobytes. Which you want depends entirely on what happens to the file next.
Some pipelines require an audio track
Certain editing timelines, ad platforms, and broadcast checks assume a video has audio and behave badly — or reject the upload — when it does not. A silent track satisfies them; a removed one does not. This is the single most common reason a muted upload fails without a useful error.
Muting is not how you make a video smaller
On the sample here the sound is 24% of the file because the picture is tiny; on real footage it is usually between 2% and 10%. If the goal is a smaller file, trimming the parts nobody watches or re-encoding the video is where the bytes actually are.
Take the audio out before you throw it away
Extracting the audio is also a copy, so it costs nothing and takes seconds. If there is any chance the sound will be wanted later — a stray comment aside, a lecture recorded on the same file — pulling it out first is free insurance.
The reason for muting is usually the reason not to upload
People mute a clip because something audible in it should not be shared: a name, a phone call in the background, a conversation off camera. Sending the file with that audio still in it to a web service to have it removed is precisely backwards.
The judgement call
Where the file is going decides it.
Sending the clip to someone
Remove the track
Smaller, simpler, and nothing is left in the file that could be recovered.
Uploading to a platform that rejected it once already
Keep it silent
A missing audio track is a common cause of an upload failing with an unhelpful error. A silent track removes that variable.
Dropping it into an editing timeline
Keep it silent
Some editors mis-sync or refuse to place a clip with no audio stream. The silent track costs a few kilobytes and avoids the argument.
Removing something audible you do not want shared
Remove the track
There is then nothing in the file to recover, which a silenced track would still leave ambiguous to anyone reasoning about the original.
You might want the audio back later
Extract it first
Extracting is a copy, so it costs nothing and takes seconds. Removing it afterwards is permanent in that copy.
Trying to make the file smaller
Wrong tool
Audio is usually a small fraction of a video. Trimming or re-encoding the picture is where the bytes are.
Reference
FAQ
Use a tool that rewrites the container rather than re-encoding the video. Sound and picture are separate tracks inside a video file, so the audio can be dropped while the video packets are copied across byte for byte — the muted clip is then bit-identical in picture to the original. The Tinapps mute video tool works this way and reports whether the picture was copied or re-encoded.
Removing drops the audio track entirely, making the file smaller with nothing left to recover. Silencing keeps a track of the same length that carries no sound, costing a few kilobytes. It matters because some editing timelines and upload pipelines assume a video has an audio track and misbehave or reject it outright when there is none — the Tinapps mute video tool offers both for that reason.
Usually not much. Audio is a small fraction of a video file — commonly 2% to 10% of a 1080p recording, though 24% on the small sample in the Tinapps mute video tool. If the goal is a smaller file, trimming the parts nobody watches or re-encoding the picture is where the bytes actually are.
Yes. The Tinapps mute video tool reads and rewrites the container with your browser's own codecs, so the file never leaves the device. That is the right way round for this job in particular: the reason for muting is usually something audible that should not be shared in the first place.
A few seconds, because no frames are decoded or encoded — the time is bounded by how fast the file can be read and written rather than by its running time. A tool that takes minutes to mute a clip is re-encoding the picture unnecessarily.
Not from the muted copy — the track is not in it. The original file still has it, so extracting the audio before muting is worth doing whenever there is any chance the sound will be wanted; extraction is also a copy, so it costs nothing and takes seconds.
Most likely because it has no audio track at all. Several platforms and editing tools assume every video has one and fail with an unhelpful error when it is missing. Keeping a silent track instead of removing it removes that variable, which is why the Tinapps mute video tool offers the choice.
Not in the Tinapps mute video tool, because nothing is uploaded and there is no bandwidth or storage to meter. The practical limit is how much memory the browser tab can allocate while rewriting the container.
The clip is read and rewritten entirely in your browser. Nothing is uploaded, and the muted copy exists only as the file you download.
Keep going
Extract audio
Take the sound out before you throw it away — also a copy.
Trim video
Where the bytes actually are, if the goal was a smaller file.
Video and audio tools
The rest of the category, all on the browser's own codecs.
Metadata viewer
The same idea for pictures: see what a file reveals before sharing it.