All tools Guides

How fast vocal and stem separation runs in a browser

With WebGPU and a mid-range graphics card, Vocal Remover separated a 4-minute song in 31 s and Stem Splitter in 42 s. Without WebGPU the same song took 12 min 29 s on one processor thread. The tables below show how we measured and what it means for your device.

Test setup

Computer
Intel Core i5-8500 (6 cores), 32 GB of memory, NVIDIA GeForce RTX 3050 (4 GB), Windows 11 Pro
Browsers
Chrome 157 and Edge 157 with WebGPU; Chromium 159 without a graphics processor (processor path)
Test song
A 4-minute song made in code (a synthesized voice, drums, bass and synths at 100 BPM), so every part is known exactly and no copyrighted music is used
Models
HTDemucs fine-tuned for vocals (Vocal Remover) and HTDemucs with 4 sources (Stem Splitter), 90.4 MB each, converted to ONNX and run with ONNX Runtime Web
Measured
November 17, 2026

Results for a 4-minute song

ToolEngineSeparation timeNote
Vocal RemoverGraphics processor (WebGPU)31 s34 s including loading the model
Stem SplitterGraphics processor (WebGPU)42 sSame time in Chrome and Edge
Vocal RemoverProcessor, one thread12 min 29 sThe page estimated 12 min 36 s before starting
Stem SplitterGraphics processor (WebGPU)2 min 1 sA 12-minute song

Why the graphics processor matters

The model does the same arithmetic on every 7.8-second piece of the song, and a 4-minute song is 42 overlapping pieces. A graphics processor runs thousands of those operations at once: 0.74 s per piece in our test (the first piece takes 1.8 s while the browser prepares it). Without WebGPU the processor runs the model on a single thread, 17.2 s per piece, about 23 times slower.

Using several processor threads in a browser needs special security headers (cross-origin isolation), which also block embedded content from other sites. This site doesn’t turn them on, so the processor path uses one thread.

Estimated time for other song lengths

Time per piece × number of pieces, from the measurements above. A different device gives different times; the speed test measures yours.

Song lengthPiecesVocal Remover, WebGPUStem Splitter, WebGPUEither tool, processor
3 min3123 s31 s9 min
4 min4231 s42 s12 min
6 min6246 s1 min18 min
8 min831 min1 min 25 s24 min
10 min1031 min 15 s1 min 45 sover the limit
15 min1541 min 55 s2 min 35 sover the limit

Memory

The model needs about 2.1 GB of working memory while it separates a piece. With WebGPU that memory sits in the browser’s graphics process and stays the same for short and long songs; without WebGPU it sits inside the tab. The rest grows with the song: about 110 MB per minute for four stems.

CaseTabGraphics processTotal
Vocal Remover, 4 min, WebGPU1.43 GB3.83 GB5.4 GB
Stem Splitter, 4 min, WebGPU1.6 GB3.9 GB5.55 GB
Stem Splitter, 12 min, WebGPU2.6 GB3.89 GB6.5 GB
Either tool, 30 s, processor2.65–2.84 GB—2.8–3 GB

Limits we set from these numbers

The tools check the song length and the reported memory before the model downloads, so a song that is too long is refused up front instead of crashing the tab.

DeviceWith WebGPUProcessor only
Laptop or desktop15 min · 6 min with 4 GB of memory or less8 min
Phone or tablet6 min · 4 min with 4 GB of memory or less4 min

A device that reports less than 4 GB of memory is told before anything downloads: the model alone needs about 2.1 GB while it runs.

Quality on the test song

SDR (signal-to-distortion ratio) compares each separated part with the true part, in decibels; higher is better. A song made in code is easier than a real recording, so read these numbers as proof that the browser version matches the original model on the same test, not as a promise for your song.

PartSDR
Vocal Remover: vocals12.4 dB
Vocal Remover: instrumental20.7 dB
Stem Splitter: vocals8.0 dB
Stem Splitter: drums18.5 dB
Stem Splitter: bass17.9 dB
Stem Splitter: other5.8 dB

Not measured yet

Safari, Firefox, laptops with only integrated graphics, and phones. We will add them here once we have measured them on real devices.

Measure your own device

The speed test separates a short sound made in your browser and shows the time per piece and an estimate for a 4-minute song. Results stay on your device.

Run the speed test