The short answer
Choose local when your upload can handle the sum, you want to control each platform separately and you'd rather keep keys and reports on your PC. Choose a cloud relay when your connection can only sustain one good output or when taking the distribution load off your machine is worth the external dependency.
There's no winner without looking at your connection. The same streamer might go local at home and use a relay at an event with tight upload.
What changes in the path
In local mode, OBS delivers one signal to the app, and the app opens one connection per platform. The upload math grows with every output.
With a relay, OBS or an app sends one signal to the cloud. The relay opens the other outputs, so your PC's upload stays close to a single stream.
Side-by-side comparison
| Factor | Local | Cloud relay |
|---|---|---|
| Upload at home | Sum of the local bitrates | One main output |
| Re-encoding load | May use your PC's CPU or GPU | May happen on the service, depending on the plan |
| Keys | Stay on your computer | Must be handed to the service |
| Per-destination control | Depends on the local app; in Corneta it's separate | Depends on the dashboard and plan |
| What can fail in between | Your PC and local connection | The service, the account and the route to the relay also join the path |
| Recurring cost | Corneta's core is free | Varies by service and plan |
When local fits better
- your stable upload sits above the sum, with headroom;
- your PC can handle copying or re-encoding the outputs you chose;
- you want to pause, test and reconnect one destination at a time;
- you don't want to hand your stream keys to a relay;
- Windows and OBS are already part of your setup.
When the cloud saves you a headache
- your upload only sustains one good-quality output;
- your machine is already at its limit with the game and OBS;
- you need to stream from a temporary or unpredictable network;
- the relay's plan delivers the destinations and settings you need;
- you're fine with storing your keys on that service.
The middle ground
Not every adaptation means re-encoding everything. In Corneta, Smart copies the compatible destinations and re-encodes only the ones that need to change. That reduces the load on your machine, but each output still uses upload.
Do the math with your own bitrates in the multistream upload guide.