Troubleshooting Song Separator.

Start here: three quick checks

1. Refresh Song Separator, choose Standard (4-stem), and try a short 10–20 second WAV or MP3.
2. Use a current browser. On desktop, Chrome or Edge with graphics acceleration enabled is the best starting point.
3. Close other GPU-intensive apps and tabs to free up memory, and avoid using multiple Song Separator tabs simultaneously.

Standard's model download is about 181 MB; Studio's is about 336 MB. Actual memory use during AI processing is substantially higher than those download sizes.

“WebGPU is unavailable” or “No compatible GPU adapter”

WebGPU is required for both AI models. A browser can be up to date and still lack a compatible GPU or operating-system support.

• Safari on Mac: Safari WebGPU requires macOS Tahoe 26 or newer. Safari 26 installed on macOS Sequoia 15 may still report WebGPU unavailable. If you cannot upgrade macOS, use Google Chrome or Edge on your Mac.
• Chrome or Edge on desktop: Update the browser, enable hardware/graphics acceleration in settings, restart the browser, and verify that the device's graphics hardware supports WebGPU.
• Safari on iPhone or iPad: Safari 26 introduced WebGPU on iOS/iPadOS 26, but WebGPU availability does not guarantee the large separation models will work. Chrome on iPhone may share similar platform limitations.

WebGPU worked earlier, but now fails immediately? Chrome and Edge may temporarily stop exposing GPU adapters after repeated GPU-process crashes. Fully exit the browser (including background processes), then reopen it. On Windows, open chrome://gpu (or edge://gpu), inspect the WebGPU line and Problems Detected, and confirm graphics acceleration is enabled in chrome://settings/system (or the Edge equivalent). If WebGPU remains disabled, update the graphics driver and restart Windows. Don't force blocked GPU features on if the browser reports repeated crashes.

WebKit's WebGPU demos can help check basic browser WebGPU support, but passing a demo does not guarantee successful model inference.

Windows: “GPU device is lost” during separation

This error means the browser lost access to the GPU while the AI model was running. ONNX Runtime may report OrtRun, mapAsync, or Failed to download data from buffer. That final message refers to reading results from GPU memory, not downloading the AI model from the internet.

It can happen because of GPU memory pressure, a graphics driver or GPU-process reset, or browser/runtime compatibility. Your reported system RAM does not tell you how much dedicated GPU memory is available.

1. Restart Chrome or Edge completely and retry the song. Once a WebGPU device is lost, the current AI session may not be reusable.
2. Open chrome://gpu (or edge://gpu) and look for WebGPU: Hardware accelerated. If the browser is using software rendering or the wrong GPU, check graphics settings.
3. Update your GPU drivers directly from your graphics card or laptop manufacturer. Close GPU-heavy games, editing apps, and other tabs.
4. If you have integrated and dedicated graphics, check Windows Settings → System → Display → Graphics and consider assigning your browser to the high-performance GPU. Restart the browser afterward.
5. Try Standard (4-stem) first. Studio's six-stem model is more GPU-intensive. If a 10–20 second clip fails too, the model or GPU may be incompatible regardless of song length.

If the issue persists, use Copy error details and share your GPU model, approximate available video memory, whether this happens on the first segment, and your browser version. Avoid repeatedly retrying the same failed GPU session without restarting the browser.

iPhone or iPad goes blank, freezes, or refreshes

If Safari goes blank and the page reloads just after the model downloads or starts, the web-content process may have been terminated under memory or GPU pressure. This is a likely explanation, not a confirmed diagnosis. A process restart can happen before Song Separator has a chance to display an error.

1. Choose Standard (4-stem) instead of Studio (6-stem).
2. Start with a 10–20 second audio clip rather than a full song.
3. Close other tabs and demanding apps, then retry in a normal browser tab.
4. If it reloads even with a short clip, try a desktop Mac or PC with Chrome or Edge. Some mobile devices may lack sufficient usable memory for model initialization.

Successfully downloading the model does not mean the GPU can initialize or run it. We don't have a server-side processing fallback.

Model download is stuck, fails, or repeats

The model is downloaded directly to your browser from Hugging Face. Check your internet connection, free storage, and whether a content blocker, VPN, firewall, or network restriction could block its download.

Try reloading the page and retrying. As a last resort, clearing the site's cached data may fix a corrupt model download. Warning: Clearing website data removes cached models and other local preferences, so the large model may need to download again. Studio requires private browser file storage (OPFS), which might not work in some private browsing environments.

“Could not load audio” or an unsupported file

Start with an MP3 or WAV file; other formats only work if your browser can decode them. Songs must be six minutes or shorter. Very short, corrupted, protected, or unsupported files may fail.

Try another recording or create an MP3/WAV copy with an audio editor on your device. Audio stays on your device during Song Separator's decoding process.

Separation is slow, stalls, or fails after starting

The GPU may run out of memory or the browser may be incompatible with an operation required by the model. Performance varies by device, song length, and selected model.

1. Use a short file and select Standard, which uses less memory than Studio.
2. Leave the tab open and avoid heavy GPU workloads while separating.
3. Restart your browser and retry. If an error appears, click Copy error details in the app and see Getting support.

If separation completes but instruments bleed between stems, that's an AI quality limitation rather than necessarily a technical error.

A WAV or ZIP won't download

WAV exports and the ZIP archive are created locally. Download Current Mix combines the currently audible stems into a single WAV; like ZIP packaging, mixdown can require extra browser memory for long recordings. The ZIP contains separated stems but excludes the Original comparison track.

1. Try downloading one WAV stem rather than a full ZIP.
2. Make sure the browser permits downloads and your device has free storage.
3. If ZIP creation still fails, try a shorter clip or a desktop browser.

Still need help?

If the app shows an error, use Copy error details and email hello@grfnstudios.com. Mention your browser, device, selected model, and when the issue occurred. If Safari simply reloaded, say so—there may be no diagnostic report.

Review diagnostic text before sharing it. You do not need to email your music or separated stems.