OBS recording settings are found under Settings → Output. For a dependable starting point, choose a folder with enough free space, record to MKV, select a quality level your computer can sustain, and make a short test before recording for a long session.
MKV reduces the risk that an interrupted recording makes the entire file unusable; it does not protect you from a full drive, a failing device, or every possible fault. If your editor needs MP4, OBS can remux an MKV recording afterwards. The right quality and encoder depend on your hardware, the footage, and what you plan to do with the file.
Find the recording controls in OBS
Open Settings → Output. OBS offers Simple and Advanced output modes. Simple is a sensible place to begin if you need a straightforward recording without separate encoder controls or multiple audio tracks. Advanced exposes additional recording settings, including encoder choices, recording tracks and rescaling options.
In Simple mode, look for the recording path and recording quality controls. The available labels and choices may vary with OBS version and hardware. OBS’s recording preset guide describes “High Quality” as targeting high quality with a medium file size, while “Indistinguishable” increases quality and file size and may put more strain on older or weaker hardware. “Lossless” makes very large files and uses the CPU encoder. These labels describe trade-offs, not a promise about the result on your computer.
“Same as stream” reuses the streaming encoder settings, so it can be convenient when you want a recording of the broadcast without configuring another encoder. OBS notes that recording cannot be paused with this choice. If you want recording settings independent of streaming, choose a separate recording quality or configure Advanced output instead. Recording independently can consume additional system resources, so verify performance rather than assuming your stream settings will have spare capacity.
For a live channel, decide what the recording is for before adjusting controls. A local archive of a devotional loop may not need the same quality or editing flexibility as a source file you intend to cut into short clips. A study channel may want to keep the original lecture and its spoken audio intact. Write down the intended use, then select settings that meet it without making the session unstable.
Set a recording path and check available storage
In the recording controls, set Recording Path to the folder where you want OBS to save the file. OBS saves recordings there, so do not rely on remembering a temporary or unfamiliar default location. Choose a folder you can find quickly after the session, and confirm that the intended drive is connected and mounted before you start.
Check free space on that drive, not just the amount you think the recording ought to use. File size varies with quality, encoder, resolution, frame rate, movement in the picture and the length of the session. A static image with music and a fast-moving game are different workloads; do not estimate a long recording from a tiny test file without allowing for that variation.
OBS’s Lossless preset guide gives a specific warning sign for storage planning: it estimates around 7 GB per minute for that preset. This is OBS’s estimate for Lossless, not a general size prediction for normal recordings. A short session at that setting can use substantial space, and a long one can quickly exceed the capacity you expected. If storage is limited, avoid Lossless unless you have a concrete reason and have confirmed the available capacity.
If you have more than one suitable drive, a separate recording drive can make files easier to manage and keep them off the system drive. It is not a requirement, and it does not remove the need to monitor free space. A removable drive can be disconnected or fill up; a second partition on the same physical drive does not necessarily protect against drive failure. The useful question is whether the chosen destination has enough capacity for the session and whether you can locate and back up the result.
A simple way to plan is to make a short recording at the intended settings, note its file size and duration, then use that as a rough guide for the same content and settings. Keep a margin for longer sessions and variation. This estimate is only a planning aid: it cannot guarantee the size of a future file, and it does not change the storage limit of the drive. For a channel that reuses one source file rather than capturing every broadcast locally, the distinction is worth understanding; the explanation of uploading once versus streaming forever describes that different workflow.
Choose a recording format: MKV or MP4
A recording format, or container, holds video and audio streams together. OBS recommends MKV for most recording cases because an interrupted recording is less likely to lose the entire file. As the OBS Project puts it in its Standard Recording Output Guide, “MKV is recommended in case of unforeseen issues arising, since MKV will not corrupt the whole file if there is no graceful stoppage of recording.” That is a resilience advantage, not a guarantee that every interrupted file will be complete or playable.
Regular MP4 and MOV files are widely supported by editing software and online services, but they require finalisation when recording ends. OBS warns against recording directly to regular MP4 or MOV because a recording that stops unexpectedly can leave the file unrecoverable. Choosing an ordinary MP4 for convenience therefore trades some protection against an unclean stop for a familiar file type. For most people, MKV first and remuxing when needed is the more cautious workflow.
| Format | Practical advantage | Trade-off |
|---|---|---|
| MKV | OBS recommends it for most cases; an interrupted recording need not corrupt the whole file. | Some editors have limited support, so you may need to remux it. |
| Regular MP4 or MOV | Broad compatibility with editors and internet-video workflows. | Requires finalisation; an interrupted write can leave it unusable. |
| Fragmented or hybrid MP4/MOV | Can combine improved resilience with broader compatibility in supported workflows. | Compatibility depends on the editor and codec; remuxing may still be needed. |
Fragmented or hybrid formats can be useful when you know the editing software supports the specific format and codec combination. Do not choose one simply because “MP4” appears in the name: confirm compatibility with the application that will open the file. If you are unsure, MKV plus OBS’s remux tool gives you a clear source file and a separate MP4 copy when required.
Select an encoder and quality your computer can handle
In Simple mode, choose a recording quality that fits the purpose and hardware. “High Quality” is a reasonable starting point for many tests, but no preset is universally best. “Indistinguishable” can produce larger files and may affect weaker hardware; “Lossless” is exceptionally storage-intensive. If OBS drops frames, the machine struggles, or the file grows too quickly, reduce the quality demand or test a different encoder rather than assuming a more demanding label is automatically an improvement.
Advanced output is useful when you need recording controls separate from the stream, a particular encoder, rescaling, or multiple recording tracks. OBS’s Advanced Recording Settings guide gives baseline examples for named encoders: NVENC CQP 16–23, x264 CRF 16–23, AMD CQP 16–23 and Quick Sync ICQ 16–23. These are starting ranges from OBS’s guide, not required settings. Within these quality-number controls, lower values mean higher quality and larger files. Hardware support and the controls available to you depend on your system and OBS version.
The same guide lists additional baseline examples, such as keyframe interval 2 and encoder-specific presets or profiles. Those controls are not all available for every encoder or machine, and it is not necessary to change them just to make a first recording. Begin with a working default or a Simple mode choice; move to Advanced only when you can name the need you are solving. If you change several controls together, a failed test will not tell you which change caused the problem.
For local recording, OBS’s formats guide recommends using the best-quality available hardware encoder for its described use case and gives an order of AV1, HEVC, then H.264. Codec support varies: the guide notes weaker editing support for AV1, while H.264 has broad compatibility. Treat that as guidance to weigh against your editor and workflow, not an instruction to choose the newest codec regardless of what can open it.
Compare the options across four practical questions: does the picture look good enough for later use, how large is the file, can your computer encode it smoothly, and can your editing or playback software handle the codec? A useful setting is one that balances all four. For example, if you need to trim clips in an older editor, a broadly supported codec may save time even if another option could produce a smaller file. If a static loop is all you need to archive, paying for a file size or detail level you will never use may not be worthwhile.
If you are also deciding whether the source file needs to remain on your own computer during a continuous YouTube broadcast, distinguish that from OBS’s local recording job. The guide to uploading new videos to a YouTube stream running on a VPS covers an alternate operating setup; it does not remove the need to choose recording settings based on your own computer and post-production needs.
Configure audio tracks if needed
Separate audio tracks help when you intend to edit sources independently. For example, you might want the microphone on one track and desktop audio or music on another so that you can adjust them later. OBS lets you assign sources to tracks in Advanced Audio Properties, then enable the recording tracks under Settings → Output when using Advanced output.
Plan the tracks before recording. Decide which sources belong together, assign them deliberately, and make sure the tracks you want are enabled for recording. Track assignment alone is not enough if the recording output is not configured to include those tracks. A short test can reveal a silent track or a source placed where you did not expect it.
There is an important playback caveat: standard video players generally play one audio track at a time. If you record dialogue on one track and music on another, a normal player may not play both as a complete mix. OBS advises assigning all sources to track 1 as well when you want a complete mix that plays without editing. You can keep separate tracks for later work and include a combined track for simple review, provided you check the result in your own player.
If you do not plan to edit the sources separately, avoid adding complexity. A single complete mix is easier to review and less likely to surprise someone who opens the file. The goal is not to maximise the number of tracks; it is to preserve the audio arrangement you will actually need.
Make a short test recording and verify playback
Before a long session, record a short test using the intended scene, encoder, container and audio setup. Include the sources that will be present during the real recording: a camera or loop, any music, a microphone, and any desktop audio. A test made with a silent scene will not tell you whether the live scene captures sound correctly.
Stop the test normally, then confirm that a file appeared in the selected recording folder. Open it in a player or editor you expect to use. Check that the picture is present, playback lasts as expected, audio is audible, and the mix or tracks behave as intended. If you plan to edit, test the file in that editor rather than relying only on a media player that may support different codecs or tracks.
Watch OBS’s status information while the test runs. If the computer becomes unresponsive, frames are missed, or playback stutters, the chosen recording settings may be too demanding for that machine alongside the other work it is doing. Try a less demanding quality choice or a different available encoder, then test again. Do not make several changes at once unless there is a reason; controlled changes make it easier to see what helped.
Check the file size as well. Compare its duration and size with the available space and the length of the session you intend to record. A brief test cannot prove that storage will last through a much longer session, but it gives a more grounded estimate than guessing. Recheck free space before starting a long capture, particularly if recordings accumulate in the same folder.
This check is also where you catch workflow errors: the wrong scene, a muted source, an unexpected track, or a path pointing somewhere you cannot access. If the recording is part of a 24/7 channel workflow, make sure you are not assuming that capturing locally is the same as keeping a stream live. A 24/7 UPSC study stream setup guide addresses the channel’s continuous operation, while this article deals with the local recording file.
Remux a recording when an MP4 copy is needed
If you recorded to MKV and an editor or upload workflow needs MP4, use OBS’s built-in remux function rather than recording the original directly to regular MP4. In OBS, open File → Remux Recordings, choose the MKV recording, and select the destination for the MP4 copy. OBS can also be configured to remux recordings automatically in Advanced settings, if that fits your workflow.
Remuxing changes the container without being the same as re-encoding the video. It is a convenient way to make a compatible copy while retaining the original MKV. Keep the original until you have opened the MP4 in the editor or service that needs it. If the editor still rejects the file, check its supported codecs and formats; changing the container cannot make an unsupported codec compatible.
A remux is not a repair tool for every damaged file, and it cannot restore video or audio that was never recorded. The benefit is practical: record in the format OBS recommends for resilience, then create a more familiar copy if a specific application calls for it. For a workflow that needs MP4 every time, test automatic remuxing and confirm where the resulting copy is saved before relying on it for a long session.
If you want to remove the local-computer burden from a file-based YouTube broadcast, StreamNeo addresses the specific pain of keeping your computer on to run a continuous stream: you upload a video and provide your YouTube stream key, then the broadcast runs while your computer is off. It is YouTube-only, and that is a different need from recording a local OBS session for editing or archiving.
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 stream in OBS?
Set the destination under Settings → Output, choose a recording quality and format, then click Start Recording. Record a short test first and check that the file saves to the expected folder and plays with the picture and audio you need.
Should I use MKV or MP4 for OBS recordings?
OBS recommends MKV for most cases because an interrupted recording is less likely to corrupt the whole file. If you need MP4 for editing or another workflow, use File → Remux Recordings and check the result before deleting the MKV.
How do I record separate audio tracks in OBS?
Assign sources to tracks in Advanced Audio Properties, then enable the relevant recording tracks under Settings → Output in Advanced mode. Because a standard player may play only one track, include all sources on track 1 too if you need a complete mix for ordinary playback.
How much storage does OBS recording use?
It depends on the encoder, quality, content and duration; there is no single size that applies to every recording. OBS estimates around 7 GB per minute for its Lossless preset, so use that only as a warning about that specific setting, not as a general estimate. Make a short test and check free space before a long session.