A local recording in Streamlabs Desktop starts with preparing the scene and checking the recording options under Settings > Output. Choose and verify the destination before capture, then use Record in the editor to start and stop; recording does not itself upload or stream the video.
The order matters. A scene can look right while its microphone is missing, and a successful capture can be hard to find if the destination was not checked first. This walkthrough focuses on local screen or gameplay recording and on confirming where the file was saved.
Prepare the screen, gameplay, and audio sources
Open the scene you intend to record and check what appears in its preview. Add or select the screen or game capture source you need, then make sure the preview shows the intended application or display. If you are recording a game, bring it into the state from which you want the recording to begin; a capture of the wrong window is still a recording, but it will not be useful.
Check the audio mixer while you speak or play a test sound. Streamlabs says a connected microphone should appear in the mixer and can be selected in audio settings. Look for movement on the relevant meter rather than assuming that a device connected to the computer is automatically the source selected for this scene. Likewise, check that desktop or game audio is represented if you want it in the recording.
Keep the scene simple enough to inspect. Hide sources that should not appear, check that overlays are placed as intended, and make sure any text is legible in the preview. A short test recording is a practical way to catch a cropped display, an absent microphone, or an unexpected application window before you capture a longer session.
This is a local recording workflow, not a continuous broadcast setup. If your separate goal is a channel that keeps playing after a computer loses power, that is a different operational problem, covered in our guide to keeping a 24/7 Indian music YouTube stream running after power loss. The recording controls described here create a file on your computer.
Open recording options in Settings > Output
In Streamlabs Desktop, open Settings, then choose Output. Review the recording controls there rather than assuming the settings used for a live stream are automatically the right ones for a local file. Menu names and available options can vary with the application version, so if your screen differs, consult Streamlabs' current recording tutorial.
The recording area is where you can inspect the destination and the choices that affect the captured file, including format, encoder, quality and audio tracks where available. You do not need to change every setting. Start by identifying what is selected now, what you need the recording to do, and whether your computer can handle the requested picture and sound while running the game or application.
If you only need a straightforward video with the audio mixed together, the single-track path involves fewer choices. If you expect to edit commentary separately from game sound, track configuration needs attention before recording: selecting tracks for sources and selecting recording tracks are related but distinct steps. We return to that trade-off below.
Avoid relying on a remembered tutorial screenshot if it does not match your current version. Use the controls shown in your installed application and check the current help material when an option is missing or has changed. This is especially useful before a long capture, when discovering a setting mismatch afterwards may mean repeating the session.
Choose or confirm the recording destination
Before pressing Record, find the recording path in Settings > Output and confirm where Streamlabs Desktop will write the file. Choose a folder your user account can write to and that has enough free disk space for the planned capture. A familiar folder is easier to check afterwards than an obscure location, but the important points are access and available space.
This destination check should happen before you capture, not only after you stop. Streamlabs' recording troubleshooting guidance identifies insufficient disk space and a destination that cannot be written to as possible reasons recording may fail. Those are possible causes, not a diagnosis of every missing file. If you have just changed the path, make a brief test and confirm the result appears where you expect.
Consider whether the chosen folder is on a drive that is usually connected and whether you can readily open it from your account. If you save to removable storage, confirm it is connected and accessible before capture. If the drive is nearly full, clear space or select another suitable destination rather than relying on the recording to succeed.
Do not confuse the recording folder with a YouTube location. This step chooses a local destination for the file; it does not publish, upload, or start a broadcast. If you are comparing continuous-broadcast approaches instead, our guide to prerecorded-video live-streaming tools discusses a different task.
Check practical output settings
Choose output settings in light of what you are recording and what your computer can manage. Streamlabs recommends matching the base canvas to the monitor resolution for gameplay and selecting the highest suitable output resolution, but it also advises testing and reducing output resolution if the machine struggles. Higher resolution and frame rate can demand more from the computer, particularly while a game is already using its resources.
For frame rate, Streamlabs describes 60 FPS as a general recommendation for most action-heavy recording and says 30 FPS may be acceptable for relatively static scenes. Treat those as starting guidance, not a promise that either choice will suit your computer or intended file. A fast game may benefit from smoother motion; a mostly static presentation may not need the same frame rate. Test a short sample and inspect both the recording and the computer's performance.
Streamlabs recommends MP4 in most cases. Its tutorial describes x264 as CPU-based and NVENC as GPU-based, recommending NVENC when you have a supported NVIDIA graphics card. It also describes CQP for NVENC-style recording and CRF for x264, with CQ 17 as a suggested starting value in that tutorial. These are Streamlabs' recommendations, not universal optimums; the right selection depends on your available options, machine and editing needs.
| Choice | When it can make sense | What to check |
|---|---|---|
| Higher output resolution | You need more image detail and the computer handles the capture | Test for performance problems while the game or application runs |
| Lower output resolution | The computer struggles with the chosen output size | Confirm the resulting detail is sufficient for your use |
| 60 FPS | Action-heavy gameplay where smoother motion matters | Test whether the computer can maintain the capture comfortably |
| 30 FPS | Relatively static material | Check that motion still looks acceptable for the subject |
| One mixed audio track | You want a simpler file to review or share | Confirm microphone and desktop audio are both present as intended |
| Separate audio tracks | You expect to adjust commentary and desktop/game sound independently | Assign sources to tracks and enable the recording tracks |
For editing, Streamlabs documents up to six audio tracks and says multi-track recording requires MP4 or MKV; its guide notes that the default FLV format does not support multiple audio tracks. If you want independent control of commentary and game audio later, use Streamlabs' multi-track recording guidance to check both the source assignments in Advanced Audio Settings and the recording track count in Output. More tracks add setup choices, so a mixed track may be more practical when you do not need that editing control.
Our MP4 export settings guide for Gujarati videos concerns preparing a video for a different downstream use, not a required Streamlabs recording preset. Keep the distinction clear: a recording's capture settings and a later export's settings are separate decisions.
Start recording in Streamlabs Desktop
Once the scene, audio, destination and output choices are checked, click Record in the lower-right area of the Streamlabs Desktop editor. The control starts local capture. It does not start a YouTube live broadcast and does not automatically upload the resulting video.
For an important session, make a short test first. Speak into the microphone, make the intended screen or game visible, and play desktop audio if that is part of the plan. Stop after a brief capture and open it to check that the picture, sound and destination are right. This simple test can reveal a wrong source or a write problem before you spend time on the full recording.
During capture, keep an eye on the application and the computer. If the game becomes unresponsive or Streamlabs indicates a problem, note what happened rather than assuming a particular setting is at fault. Streamlabs advises testing chosen settings and lowering output resolution or adjusting settings if the computer struggles; a test is more useful than adopting a setting just because it worked in someone else's setup.
The Streamlabs getting-started help page is a useful reference if your editor layout or controls differ from the description here. As with other software guidance, match instructions to the version you are actually using.
Stop recording and confirm it saved
When you have captured what you need, click Record again to stop. Streamlabs says a confirmation appears when the recording has been saved. Use that confirmation as the immediate check that the stop action completed, and follow its available information or open-file option to inspect the result.
Do not treat the stop click alone as proof that the file is usable. If the confirmation does not appear, or the file is not where you expected, check the destination you reviewed before recording and look for an error message. The free space and write permission checks remain relevant. Avoid immediately repeating a lengthy capture until you know whether the first file exists and whether the problem was a path, storage or application issue.
If there is an error, read the exact wording and check which version of Streamlabs Desktop you are running before trying a fix. Streamlabs' troubleshooting page includes suggestions such as checking storage and write access, updating graphics drivers, or running the app as administrator. These are support suggestions rather than guaranteed solutions, and not every suggestion applies to every error. Prefer the steps that match the message you actually see.
Find or open the recorded file
The simplest route is often the save confirmation that appears after stopping. Streamlabs says the confirmation can provide more information or help open the recording in another Streamlabs application. If you dismissed it, return to Settings > Output and check the recording path; then open that folder using your usual file browser and look for the file created at the time of your capture.
If the folder is empty, verify that you are checking the same destination that was selected when recording began. Check for available disk space and confirm that the folder is writable. Search your computer only after checking the configured path, since a broad search can take time and may find older recordings with similar names.
Open the file and review its beginning, a section with expected audio, and its ending. Confirm that the picture is present, the microphone or desktop sound you wanted is audible, and the recording stops where expected. If you planned separate audio tracks, check that the editing application can access the tracks; simply seeing a video file does not establish that the track layout is right.
If you want a video file as source material for a later YouTube loop, first confirm that the local recording is complete and suitable for that separate workflow. Our article on running a 24/7 rerun channel for Hindi gaming walkthroughs covers the ongoing channel question; this guide only covers capturing and locating a local file.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
How do I record my screen or gameplay in Streamlabs Desktop?
Prepare the screen or game capture and audio sources in the editor, then check Settings > Output, especially the destination. Click Record in the lower-right editor area to begin and click it again to stop. Review the save confirmation and open the file to check the result.
Where does Streamlabs Desktop save recordings?
The destination is shown in the recording options under Settings > Output. Check it before capture, then use the confirmation after stopping or open that folder in your file browser. If the file is missing, confirm the selected path, available disk space and write access.
Can I record microphone and desktop audio separately?
Yes, Streamlabs documents assigning audio sources to distinct tracks in Advanced Audio Settings and selecting recording tracks in Output. Its documentation says multi-track recording supports MP4 or MKV and up to six audio tracks. Configure both parts before capture and make a test file if separate editing control matters.
What should I do if no recording file appears?
Check the exact destination and whether the drive has free space and the folder is writable; Streamlabs lists storage and write access among possible causes. If an error appeared, use its wording to guide the next step and consult Streamlabs' current troubleshooting material. Support suggestions are not guaranteed fixes, so verify the file and the capture with a short test after any change.