Streamlabs Desktop is a live production and recording studio that combines camera feeds, microphones, games, windows, images, browser widgets, and alerts into an output. A scene is one arranged layout, and a source is one item inside that layout. Streamlabs sends the composed result to a streaming service, saves it locally, or does both. It does not decide which window is private or which microphone should be heard; those choices come from the selected sources, audio routes, and output settings.
Scenes hold sources
A creator can keep separate scenes for a starting screen, gameplay, a camera discussion, and an ending card. Switching scenes changes the visible source arrangement without rebuilding the whole project. One source can also appear in more than one scene, so changing its properties can affect several layouts.
Window Capture follows a chosen application, Display Capture sees an entire monitor, and Game Capture targets supported games. Display Capture can expose notifications, password managers, email, or another window dragged onto that screen. Window names can also change after an application update. A private local test recording should inspect every scene before the first broadcast.
Two visible outputs
Selective Recording lets a source appear in the stream, the local recording, or both. A live alert box can remain visible to viewers while the clean recording keeps only gameplay. A private production note can take the opposite route and stay out of the broadcast.
New sources default to both outputs. Adding a camera or alert after the initial setup can therefore put it into the recording until its destination changes. Streamlabs has separate projector previews for the live and recording results. Checking only the normal editor preview can miss a source that the second output excludes.
Audio needs routes
The mixer controls microphones, desktop sound, capture devices, and browser-source audio. Advanced output settings can assign sources to different recording tracks. A compatible container can preserve those tracks for later editing rather than baking every sound into one mix.
Audio separation becomes more involved when one sound should reach the stream but not the recording. Streamlabs documents a route that uses a virtual mixer, separate monitoring device, and several tracks. Monitoring a source through the same desktop path that the capture already records can create echo or feed the alert back into the clean track. A short recording with spoken track names makes a routing mistake easy to find before a long session.
Encoding has limits
Streaming turns the composed frames into a continuous encoded feed. Resolution, frame rate, bitrate, and encoder choice determine the work placed on the processor, graphics hardware, and upload connection. A local recording can use different quality settings, but simultaneous streaming and recording still share system resources.
Higher settings do not guarantee a clearer broadcast. An upload connection that cannot sustain the bitrate causes dropped frames, while an overloaded encoder causes skipped work before the data reaches the network. Games can also consume the graphics capacity that hardware encoding needs. Testing the target game is more useful than testing an empty scene.
Several destinations
Streamlabs can connect to supported streaming platforms and custom RTMP destinations. Multistreaming sends one production to several services, subject to account access and the active Streamlabs plan. Each service still applies its own authentication, category, title, bitrate, and content rules.
A shared title does not render identically everywhere, and one platform may ignore a field another requires. Losing authorization on one account can leave the other destinations active, so a successful Go Live action does not prove that every service received the feed. Opening each destination’s dashboard confirms the actual state.
Record before live
The Record control runs the production without sending it to an audience. That pass should cover scene switches, the loudest microphone moment, alerts, game capture, and the final output file. Streamlabs settings can be correct while the selected file path lacks space or the chosen recording format cannot keep the requested audio tracks. A completed test file verifies both composition and storage.
