Video Mute & Audio Stripper
Video Mute & Audio Stripper: Draws video frames to a canvas stream omitting all audio tracks, and re-encodes silent WebM via MediaRecorder.
About this video mute & audio stripper
Draws video frames to a canvas stream omitting all audio tracks, and re-encodes silent WebM via MediaRecorder.
How this tool works
Implements client-side Video Mute & Audio Stripper operations. Re-renders decoded video frames to a canvas stream while omitting captured audio tracks, recording a silent WebM at up to 1280x720 via MediaRecorder API.
- Video Element Ingestion: Loads local video into a hidden HTML5 video object to extract metadata and decode frames.
- Synchronized Frame Seeking: Seeks across calculated timestamp intervals using asynchronous seeked event promises.
- Canvas Rendering & Scaling: Renders frames to a Canvas 2D context scaled to requested dimensions, which may result in stretching if non-proportional.
- MediaStream & GIF Encoding: Records the running canvas stream to WebM via MediaRecorder or quantizes frames to up to 256 colors for GIF compilation.
Worked example
Scenario: A video creator removes the audio track from a video clip before sharing.
Sample input:
Processing: Draws every decoded frame to a 30fps canvas while omitting captured audio tracks; width and height are independently capped at 1280 and 720 and even-rounded, then MediaRecorder selects supported VP9/Opus, VP8/Opus, or generic WebM.
Illustrative output:
Limits and verification
A file must be decodable by the current browser; codec and container support varies by browser and platform. MediaRecorder outputs WebM, and GIF compilation does not enforce strict file-size limits or maximum durations.
Examples demonstrate an expected workflow; they do not prove every input or every branch of an external specification. Check important results with an independent source before using them for money, security, compliance, safety, or irreversible file changes.
Browser processing boundary
Tool input is processed by code running in the browser and is not intentionally sent to a CZOA processing API. The page can still request ordinary site assets, analytics, or advertising when those services are enabled. Browser extensions and managed-device software remain outside this tool's control.
Relevant references
These references govern or help explain the format, protocol, or calculation used here. Listing a reference does not claim certification or complete implementation of every optional feature.
- W3C MediaStream Recording API (MediaRecorder)
- W3C HTML Living Standard (HTMLMediaElement & Canvas 2D)
Content owner: CZOA Tools · Last reviewed: 2026-09-15 · Review methodology
How to use it
- Enter, paste, or select your input data into the Video Mute & Audio Stripper workspace controls.
- Review available parameter fields, units, formats, or options configured for your task.
- Click the action button or observe immediate live calculations rendered in your browser runtime.
- Inspect the resulting output and any diagnostic messages, then copy or download the result if needed.
Frequently asked questions
How does Video Mute & Audio Stripper transform the selected file?+
A browser-decodable video is redrawn frame by frame to a canvas stream while every captured audio track is omitted, then recorded as a new silent WebM. This is re-encoding rather than lossless audio-track removal.
Which inputs and controls does Video Mute & Audio Stripper provide?+
The only tool input is one video; there are no controls for choosing tracks, clip ranges, codecs, bitrates, subtitles, metadata, or output dimensions.
What limits apply to Video Mute & Audio Stripper output?+
Width and height are independently capped at 1280 and 720 before even rounding, so an unusually shaped source can be stretched. Recording is 30 fps with VP9/Opus, VP8/Opus, or generic WebM fallback; source container, timing, captions, metadata, file size, duration, and successful encoding are not guaranteed.
What does the browser-isolation evidence establish for Video Mute & Audio Stripper?+
Recorded browser requests contained no submitted video payload. This establishes the observed tool-value path in the tested browser only; normal page resources remain outside that statement.