Local vs cloud stem separation: keeping client music on your computer

To separate a track into stems, the audio has to be processed somewhere. Some services do it on their own servers, which means your file is uploaded. Other tools run on your own computer, so the file never leaves it. For personal projects either can be fine. For client work, it can matter.

Why it matters for client and unreleased music

Client contracts and NDAs often limit who may receive a copy of the material.
Unreleased or embargoed music is sensitive until it is public.
Uploading a file to a third-party service can count as sharing it, even if the service deletes it later.

This is not legal advice. Read your agreement, and ask the client if it is unclear.

What cloud processing means in practice

A cloud service receives your audio file on its servers, processes it there, and sends the stems back. Policies on how long files are kept and how they are used differ from service to service, so read the privacy policy of any service before you send it client music.

What local processing means

A local tool does the work on your own machine, so the audio is never sent anywhere. The trade-offs are practical ones:

You need a computer capable of running it, and how fast it runs depends on that computer.
The software has to download its audio models before it can work.
Quality is the same kind of estimate as anywhere else. Where it runs does not change how clean the stems are.

How StemForge handles it

StemForge runs a local companion service on your Mac, and the panel inside Premiere Pro or DaVinci Resolve Studio talks to it on your own machine. Separation, BPM and key detection, and rendering all run there. Your audio is never uploaded. StemForge goes online only to check your license and to download its audio models. It runs on Apple Silicon Macs only. See how it works and the FAQ.

A short checklist before you separate client music

Read the agreement for anything about sharing material with third parties.
Find out whether the tool uploads your file. The privacy policy or documentation should say.
Keep a note of which tool processed which files, in case a client asks.
Remember that rights are a separate question. Processing a file locally does not change who owns the music.

Questions

Does StemForge upload my audio?

No. Stem separation, BPM and key detection, and rendering all run locally on your Mac. StemForge goes online only to check your license and to download its audio models.

Is local stem separation better quality than cloud?

Not by itself. Quality depends on the model and the music, such as how clear and distinct the parts are, not on where the processing runs. Stems separated from a finished mix are an estimate either way.

Why would I care where my music is processed?

Client agreements and unreleased music often limit who may receive a copy. Uploading a file to a third-party service can count as sharing it, so check what your agreement says before you do.

What are the downsides of running stem separation locally?

It needs a computer that can handle it, the speed depends on that computer, and the software has to download its models. StemForge runs on Apple Silicon Macs only.

Does local processing change who owns the music?

No. Where a track is processed has no effect on rights. Check the license for any music you use.