Guide · Audio & Video
Mute and Replace Audio Track Safely (Browser)
Updated 2026-10-23 · 4 min read
Bad room tone, wrong language take, or music you finally licensed after the picture was locked - all mean the same FFmpeg operation: keep video stream, change audio stream. ToolComb splits the UX across Video Replace Audio, Remove Audio from Video, and Add Music to Video, all FFmpeg.wasm local with ~100 MB per-file limits and ~25 MB first engine load.
"Safely" here means sync discipline, rights, and privacy - not uploading a confidential board recording to a random mux site. This guide routes which page to open and what the browser will not fix.
Pick the right tool
| Goal | Tool |
|---|---|
| Silent video (b-roll, GIF source) | Remove Audio from Video |
| One new narration or music bed replaces old audio entirely | Video Replace Audio |
| Background music under clip (shortest stream wins) | Add Music to Video |
Replace maps one audio stream to the video length. Add music often ends at the shorter of song vs clip - read tool copy if your song is longer than the video.
Picture edits still belong on Video Trimmer before mux. Captions after audio lock: Burn-in subtitles from SRT.
Safe workflow (sync and levels)
1. Picture lock. Trim video first. Changing duration after mux forces redo.
2. Prepare audio.
- Narration: export WAV or high MP3 from DAW, start at zero or trim silence in Audio Trimmer.
- Music: use length ≥ video or accept cutoff per tool rules; loop in DAW if needed.
- Levels: avoid clipped peaks before mux; browser tools are not mastering suites.
3. Load video + audio on replace/add page. Each file under ~100 MB.
4. Mux and read the log. FFmpeg copies video when possible, encodes AAC audio (~192 kbps typical). Watch for codec copy failures on odd inputs.
5. Download and QC with headphones. Lip sync errors mean prepare audio again - do not publish hoping nobody notices.
6. Optional compress for sharing: Video Compressor after you are happy with sound.
FFmpeg.wasm limits
- Two files × 100 MB still stresses RAM on mobile.
- First load ~25 MB engine - plan time on first mux of the day.
- No multitrack mix like Pro Tools - one replacement or simple bed mix per tool design.
- Exotic video codecs may force re-encode or fail - normalize to H.264/AAC MP4 first.
Failure → desktop ffmpeg -map flags, not a credential-harvesting "unlimited mux" site.
Copyright and sync rights
Replacing audio with chart music is synchronization - a separate right from buying the MP3. Stock libraries grant sync in license text; read it.
Remove audio then add unlicensed track is still infringement.
Work-for-hire narration: you own VO; ensure video rights too if you did not shoot it.
Platform Content ID triggers on upload, regardless of local mux.
Local processing reduces vendor copy risk; it does not replace legal review for ads and broadcast.
Privacy scenarios
HR training, M&A teasers, patient education - reasons to mux locally. Claim: media not required on ToolComb servers for export. Mitigations: trusted device, close tab, downloads folder not synced to personal cloud. Corporate policy may still block browser tools - follow InfoSec.
Common mistakes
- Music shorter than video → abrupt silence tail (fix length in DAW).
- Double audio - forgot to remove old track before adding bed (use remove or replace intentionally).
- Re-mux loop five times - generational loss on re-encoded video paths; mux once from best video master.
- Muted video uploaded to platform that rejects silent ads - add licensed bed or VO.
Related reading
Hub: Best free browser audio and video tools. Captions after sound lock: Burn-in subtitles from SRT limits. Trim/compress picture: How to trim and compress video without uploading.
Remove vs replace: legal and practical nuance
Remove audio when you need silent b-roll, stock footage without its embedded music, or a clean plate for later VO in a DAW. Replace when the picture is final and you have one approved track. Add music when dialogue stays and bed sits underneath - verify levels so VO remains intelligible; browser tools will not auto-duck like a broadcast chain.
Replacing licensed music on a client's old ad without rights to the new song is the same legal failure as cloud mux. Local only changes who holds a copy.
Corporate and ads review loop
Legal often wants mute + new VO on testimonial reels to strip background TV audio. Workflow: Remove Audio → record VO → Video Replace Audio with WAV → Burn-in subtitles if compliance needs on-screen disclaimers. Each step is one download; keep versioned filenames so approvers know which mux passed QC.
Lock picture, prepare licensed audio with sync in mind, mux once in Video Replace Audio or siblings, QC with headphones, compress for delivery if bytes matter.
Frequently asked questions
Does video replace audio upload my files?
No. FFmpeg.wasm muxes video and audio in the browser. Sources are read locally and the export downloads from the tab - not from a ToolComb transcode server.
Which tool: replace, remove, or add music?
Remove Audio from Video for mute/silent MP4. Video Replace Audio when you have one new track for the whole timeline. Add Music to Video when you mix a bed under existing sound (check tool behavior for ducking).
Why ~100 MB per file?
Both video and replacement audio hit separate validator checks. Browser RAM holds demux buffers. Trim or compress oversized sources before mux.
First export slow?
FFmpeg.wasm downloads ~25 MB engine files on first use, then caches. Neither file contains your media.
How do I fix sync drift?
Replace assumes aligned zero points. If narration starts late, trim audio in Audio Trimmer or shift in a DAW, then mux. Browser tools rarely offer frame-accurate slip after the fact.
Can I add any song from Spotify?
No. You need a track you may synchronize to video - license, royalty-free, or original. Local mux does not grant sync rights.
Related guides
More reading that links back to the same tools and workflows.
Best Free Browser Audio and Video Tools (FFmpeg.wasm)
Trim, join, compress, GIF, MP3, subtitles, and waveform exports without uploading media. How ToolComb's FFmpeg.wasm tools map to real chores - and where ~100 MB and first-load limits apply.
6 min read
Burn-In Subtitles from SRT: Limits and Workflow
Hardcode captions in the browser with FFmpeg.wasm when sidecar SRT fails on social or review links. Timing, font, ~100 MB caps, and accessibility tradeoffs.
4 min read
How to Trim and Compress Video Without Uploading
Cut screen recordings and shrink MP4 for Slack, LMS, and email caps using FFmpeg.wasm locally. CRF vs bitrate, ~100 MB limits, and resize when needed.
4 min read
How to Trim Audio in the Browser (No Upload)
Cut podcast cold opens, song intros, and interview segments with FFmpeg.wasm. First-load size, ~100 MB limits, and when to join or strip silence next.
4 min read