Vocal Remover
Separate voice and music. Create instrumental and vocal stems using an on-device separation model.
What does vocal remover do?
A vocal remover estimates the vocal source and the remaining accompaniment from a mixed recording. SoundTools runs a four-source Demucs model locally, exposes the vocal prediction, and combines drums, bass, and other into the instrumental output.
A real local processor, not a decorative upload box
Demucs WebGPU runs after you choose a source and explicitly start the operation. The audio samples remain in browser memory; SoundTools does not send the selected media to an application endpoint.
Confirm that your browser supports WebGPU, then start the one-time model download and local chunked separation. Results remain available for preview and download only in the current tab. Closing or refreshing the page releases those temporary objects.
How to use vocal remover
- 01
Choose the local source
Open a compatible file in the dedicated workbench at the top of this page. The browser validates and decodes it without an upload step.
- 02
Set the useful controls
Confirm that your browser supports WebGPU, then start the one-time model download and local chunked separation.
- 03
Process, check, and export
Run the local processor, inspect the status and preview, then save Vocals WAV · Instrumental WAV when the result is ready.
What this tool actually does
Clear limits are part of a useful tool. These values describe the processor currently running in this page.
The work is executed in the page through browser workers, WebAssembly, Web Audio, or WebGPU as stated.
Runtime and model assets may be downloaded, but the selected file is not attached to those requests.
The dedicated workbench exposes only formats it can actually produce in the current browser.
Useful reasons to open vocal remover
- Practice tracks
Create an instrumental reference for rehearsal or arrangement study.
- Vocal study
Listen more closely to the estimated vocal performance.
- Remix preparation
Generate two local starting stems for an authorized creative edit.
Questions about this tool
Answers based on the current browser processor—not promises about a future version.
01Is my audio uploaded for processing?
No. Audio samples stay in browser memory. The page may download a codec or model asset, but it does not send the selected file with that request.
02Why can the first run take longer?
This tool uses Demucs WebGPU. A browser may need to download and initialize that runtime before the first operation; later runs can reuse cached assets.
03Can I preview the result before saving?
Yes. Audio-producing tools expose local result players, while analysis and transcription tools show their detected data before download.
04What happens when the browser is unsupported?
The workbench reports the missing capability instead of uploading the media or pretending that processing is still running.