Why this matters
There are countless situations where you need a video without its audio: removing background noise from a screen recording, stripping a music track before adding a new one, creating a silent loop for a website background, or sanitizing footage for a presentation where audio would be disruptive. In most cases, people reach for desktop software like ffmpeg or a web service that requires uploading the file to a remote server.
This tool takes a different approach. It plays the video in your browser, draws each frame onto a hidden canvas, and re-records the result with a silent audio track using the MediaRecorder API. The entire process happens locally — no upload, no server, no waiting for a cloud job to finish. The trade-off is speed: because re-encoding happens in real time, a two-minute video takes about two minutes to process.
1. Click the drop zone — pick a video with an audio track.
How the muting process works
| Step | What happens |
|---|---|
| 1. Load | Video file is read into a `<video>` element |
| 2. Play | Video plays at 1x speed on a hidden canvas |
| 3. Capture | `captureStream()` grabs the canvas video track |
| 4. Silence | A zero-gain oscillator produces an empty audio track |
| 5. Record | `MediaRecorder` encodes the combined stream to WebM |
| 6. Download | The muted file is offered for download |
How to use it
Drop a video file onto the upload zone — formats under 200 MB are recommended for best performance.
Click the mute button to start the process.
The tool plays the video silently while capturing each frame and re-encoding with a blank audio track.
Download the resulting WebM file once processing completes.
Testing your result
Open the downloaded WebM in any media player and verify two things: the video plays normally with no visual artifacts, and the audio track is completely silent (not just quiet). Check the file duration matches the original — if the video was truncated, the browser may have encountered a codec issue during capture. For critical work, compare a few frames from the original and muted versions side by side to confirm pixel-level fidelity.
Common mistakes
Expecting instant results — real-time re-encoding means processing time equals video duration, so a 10-minute clip takes 10 minutes.
Assuming the output will be MP4 — the MediaRecorder API in Chrome and Firefox produces WebM regardless of input format.
Using iOS Safari, which has limited MediaRecorder support and may not support `captureStream` at all.
Attempting to mute very long videos (over 10 minutes) which are better handled by native tools like ffmpeg.
Edge cases and options
The silent audio track is not a simple track deletion but an active zero-gain oscillator connected to a `MediaStreamDestination`. This ensures the output file has a valid audio stream structure, which prevents playback issues in some players that malfunction with audio-less video files. For videos longer than a few minutes, consider using ffmpeg with the `-an` flag instead — it processes in seconds rather than real time and can output MP4 directly.
Real-world use cases
Content creators stripping accidental audio from screen recordings before adding a professional voiceover.
Social media managers creating muted video loops for website headers or ad creatives.
Educators removing distracting background noise from lecture recordings before redistribution.
Frequently asked questions
Q: Why does the output become WebM?
A: The MediaRecorder API in Chrome and Firefox encodes to WebM (VP9 or VP8) regardless of input format. If you need MP4 output, convert the WebM afterward with a native tool.
Q: How is the audio actually muted?
A: A zero-gain oscillator is connected to a MediaStreamDestination, producing an empty audio track. There is no possibility of the original audio leaking into the output.
Q: Why does processing take as long as the video?
A: Re-encoding happens in real time — the video plays at 1x speed while each frame is captured and re-recorded. Native tools like ffmpeg can do this in seconds by reading and writing directly.
Q: Does this work on iOS Safari?
A: MediaRecorder support on iOS Safari is limited and captureStream may be unavailable. For reliable results, use Chrome, Edge, or Firefox on desktop or Android.
Q: What if my video is very long?
A: For anything over a few minutes, prefer ffmpeg with the -an flag — it processes almost instantly and can output MP4 directly. This browser tool is best suited for short clips.
Q: Is there a file size limit?
A: There is no hard limit, but files under 200 MB are recommended for smooth performance. Very large files may cause memory pressure in the browser.
Start using it now
Try the Mute Video tool. See also Extract Audio, Change Video Speed, and Video to GIF.
