Separate Recording and Streaming Settings in OBS

Why Separate Recording and Streaming Settings

Streaming and local recording serve different purposes. The stream must meet the platform's requirements, fit within your internet connection's capabilities, and not create unnecessary load during gameplay. A local file can be saved at higher quality because it isn't limited by the stream's outgoing bitrate.

If you leave a single setting for both processes, OBS will use the same encoding logic. When you choose parameters suited for streaming, the recording may look worse than it should: dynamic scenes will show blocks, blurred details, and motion artifacts. If you optimize only for recording, the stream may start dropping frames, and the load on your computer and connection will become too high.

In OBS you can separately set the encoder, quality control mode, bitrate, save path, container, and audio tracks. In some configurations, separate recording scaling is also available. Scenes, sources, game capture, and overall image processing remain shared for both outputs.

Separate parameters don't mean completely independent rendering. OBS still processes the image for both the stream and the file simultaneously. That's why after changing settings you need to test in the exact scene where you usually stream: with the game, camera, alerts, browser sources, and microphone.

How to Open Advanced Output Parameters

Open the "Settings" menu in OBS, go to the "Output" section, and in the "Output Mode" line select "Advanced." Individual item names may differ slightly depending on the OBS version and selected language.

In simple mode, the program offers a limited set of presets. They're suitable for getting started but don't let you control the stream and local recording separately. After enabling advanced mode, separate blocks or tabs for "Streaming" and "Recording" appear.

First configure streaming, then move on to recording. Don't confuse the "Output" section with the "Video" section. The video settings define the base canvas resolution, output resolution, and frame rate. These parameters can affect both results, even if the encoders and bitrates are separated.

After each significant change, save the settings and test only one scenario. If you change the resolution, encoder, and recording quality all at once, it will be hard to tell what exactly caused the increased load or degraded image.

Stream Settings for Twitch in OBS

For streaming on Twitch, a practical starting combination for 1080p60 is the NVIDIA NVENC hardware encoder, CBR mode, a bitrate of 6000–8000 kbps, and a keyframe interval of 2 seconds. For the codec, H.264 is usually chosen since it's widely supported by platforms and viewer devices.

The 6000–8000 kbps range doesn't mean you should always set the maximum value right away. Start with 6000 kbps if you want to lower the demands on your connection. Use 8000 kbps only after checking Twitch's current limits, your account's capabilities, and the stability of your upload speed. The platform's stream ingestion rules can change.

For the encoding profile, High is usually chosen if the selected encoder supports it. It's best to leave the other NVENC parameters within the values recommended by OBS or Twitch at first. A preset that's too demanding can take resources away from the game, especially when recording simultaneously.

Constant bitrate (CBR) is needed for a stable stream. It makes data transmission better match the platform's requirements than a mode designed purely for quality. Don't try to compensate for a weak connection with maximum encoder quality: with an unstable connection, viewers will still see buffering or drops.

1080p60 requires not only sufficient upload speed but also headroom for connection fluctuations. If your connection is running at its limit, first test the stream at the chosen bitrate. If frames are dropping, it's safer to reduce the bitrate, resolution, or frame rate than to leave an unstable stream.

What to Specify in the Streaming Section

In "Settings" → "Output" → "Streaming," select NVENC if your graphics card supports this encoder and OBS works with it without errors. In the bitrate control field, set CBR, and in the "Bitrate" field enter the chosen value in kbps. For the keyframe interval, set 2 seconds if this matches Twitch's current requirements.

Check that software x264 hasn't been selected by accident. It encodes via the CPU and can be useful in certain systems, but with a demanding game and simultaneous recording it can significantly increase CPU load. Hardware NVENC usually lets you offload the main encoding work to the graphics card.

The "Use stream encoder settings" option in the recording section links the local file to the stream parameters. If your goal is to get separate recording quality, this option should not be enabled. Otherwise, the recording will use the stream's logic, including its bitrate limit.

How to Set Up Local Recording Separately

Go to "Settings" → "Output" → "Recording." In the recording type field, select "Standard," specify a separate folder, and make sure there's enough free space on the selected drive. It's best to set the path not just for convenience but also considering load: the system drive and the game drive may not be the best place for long files.

In the encoder field, select NVIDIA NVENC H.264 if the recording is intended for editing, uploading to various platforms, or viewing on devices with unknown codec support. NVENC is a hardware encoding method, while H.264 is the video codec itself. They shouldn't be considered interchangeable terms.

In the recording section, don't select "Same as stream." This option copies the stream parameters and doesn't allow separate quality control. The encoder may be the same, but the quality mode, container, and additional settings must be configured independently.

For local recording with simultaneous streaming, you can use NVENC for both the stream and the file. The capability depends on the graphics card, driver version, resolution, frame rate, and game load. After enabling both outputs, be sure to check OBS statistics and the game's smoothness.

CQP 18–22 for Recording via NVENC

For recording via NVENC, use CQP quality control mode and start with a value in the 18–22 range. A lower number means higher quality and usually a larger file size. A value of 18 works as a starting point for a high-quality source, while 22 lets you reduce the size if the recording takes up too much space.

The specific result depends on the game and the image. In a calm scene, the file may come out small, but with fast camera movement, particles, grass, foliage, and small text, the data stream will grow. That's why you can't rely on the CQP number alone: check the file itself and make sure the drive has enough space.

A practical starting setup looks like this: NVENC H.264, CQP 18–22, MKV container, recording to a separate fast drive. If after testing you see blocks on motion or lose small details, lower the CQP value. If the quality is already sufficient but the files are too large, raise it toward 22.

For software x264, CRF is usually used instead of CQP. It's a similar quality scale, but its value can't be directly compared to CQP. If x264 is selected, use CRF and follow its own logic. Don't carry the number 18 or 22 between different encoders without checking the result.

CBR also works for local recording but isn't always efficient. It fixes the bitrate even in a simple scene and may not provide enough data for complex frames if a limited value is set. Leave CBR for streaming, and use a quality-oriented mode for the file.

How to Choose a Codec for the Local File

Don't confuse container, codec, and encoder. MKV and MP4 are containers that hold video and audio. H.264, HEVC, and AV1 are video codecs. NVENC is a hardware encoding method on NVIDIA graphics cards. In OBS settings these concepts appear side by side, so it's important to check each item separately.

H.264 is usually chosen for maximum compatibility with video editors, players, and upload services. HEVC can produce a smaller file at comparable quality, but support depends on the operating system, video editor, and hardware. AV1 can also compress images efficiently, but decoding and editing requirements may be higher.

If the recording is for quick editing, clip publishing, and sharing with another person, start with H.264. If the file is for your own archive and the programs you use work reliably with HEVC or AV1, you can test one of these options on a short segment.

Check more than just playback. Open the test file in the video editor you'll be using, scrub through the timeline, and try exporting a short segment. Some combinations of codec, container, and audio tracks play fine in a player but cause problems during editing.

MKV and Automatic Remux to MP4

For long recordings, it's safer to select MKV in the "Recording Format" field. If OBS or the computer crashes, the container usually preserves the portion of the file already written. This doesn't recover data that hadn't yet been written to disk, but it reduces the risk of losing all the material due to an unfinished MP4.

To get MP4 automatically after a normal stop, open "Settings" → "Advanced." Find the section related to recording and enable "Automatically remux to mp4." In the "Output" section, leave the recording format as MKV.

After normally clicking "Stop Recording," OBS will first finalize the MKV and then perform the remux to MP4. There's no re-encoding here: video and audio are transferred to a different container, so quality doesn't change. The finished MP4 will appear in the recording folder once the operation completes.

Auto-remux can't create an MP4 after a sudden OBS crash because that requires properly closing the source file. On a crash, the saved MKV remains usable. After restarting OBS, open "File" → "Remux Recordings," select the MKV, and specify a location for the MP4.

Don't rename the extension manually. Renaming MKV to MP4 doesn't change the container structure and can cause an error when opening. After automatic or manual remuxing, check the MP4, and only then delete the source MKV.

Different Resolution and General Video Parameters

The base canvas resolution is set in the "Video" section. It defines the working area of scenes and affects the image OBS receives from sources. The output resolution sets the size of the result after scaling.

In the recording section, a "Rescale Output" option may be available. If it's shown for the selected configuration, enable it and specify the local file's resolution separately from the stream's resolution. For example, you can send the stream at 1920×1080 while saving the recording at a different resolution if the task justifies it.

Separate scaling requires additional image processing. Enabling it increases the load on the graphics card and OBS rendering. It's not worth raising the recording resolution above the source: upscaling won't add detail but will increase computation and file size.

The frame rate is most often set in the general video settings and applies to the entire workflow. Setting 60 frames per second for the stream and a different value for recording separately with standard tools isn't possible in all scenarios. If such a scheme is necessary, first check the capabilities of the current OBS version and the selected encoder.

Separate Audio Tracks for Streaming and Recording

You can make the local file easier to edit by not mixing all sources into one track. In "Advanced Audio Properties," assign the microphone, game, music, and alerts to different tracks. For the stream, keep a separate track with the finished overall mix that the viewer hears.

Most platforms use a single audio track for the broadcast. The local recording, meanwhile, can contain multiple tracks: for example, the overall mix, microphone only, and game audio only. This helps you remove music, fix the balance, or replace a separate source during editing.

Check the tracks in the recording settings and in the video editor itself. Make a short file, mute the tracks one by one, and make sure the microphone isn't duplicated, the game audio isn't missing, and the overall mix contains everything needed for viewing.

Separate tracks won't automatically fix incorrect volume. Before streaming, listen to a test segment in headphones and check that the game isn't drowning out speech. This is especially important after changing the output device or connecting a new microphone.

How to Check Disk Load: HDD vs SSD

The write speed to a specific disk can be just as important for a streamer as choosing CQP. During recording, OBS constantly writes data while the game reads textures and other files in parallel. On an HDD, sequential writing may proceed fine, but head movement between game files, the system, and the recording can cause delays and stuttering.

An SSD is usually better suited for local recording, especially if the game also runs on it or other applications are active. An NVMe SSD isn't always necessary: what matters more is real, stable writing on your drive, free space, and the absence of competing tasks. You can't judge an old HDD by its rated speed from the specs alone.

Test the drive on your own computer. Launch the same game and OBS scene you'll use for streaming, start recording for 10–15 minutes, and during that time open Windows Task Manager or Resource Monitor. Watch disk activity, write speed, free space, and whether delays appear in the game.

After the test, check the size of the resulting file and calculate the average speed: divide the file size in megabytes by the recording duration in seconds. Compare this result with the actual write speed shown by monitoring. With CQP, the speed won't be constant, so test a complex scene, not just the game menu.

Don't rely solely on synthetic test results. A drive may show high speed in a short check but slow down when the cache fills or during long recordings. A real OBS test accounts for the game, scenes, encoder, and file system all at once.

If the HDD frequently hits 100 percent activity, the recording starts stuttering, and the game lags, move the recording to an SSD or a separate drive. Also, don't save the file to a network folder, an external drive with an unstable connection, or a nearly full partition without testing first.

How to Identify the Cause of Drops and Stutters

Open the OBS "Stats" window during testing. Dropped frames due to network indicate a connection issue with the platform. Drops due to encoding indicate a lack of encoder resources. Rendering stutters mean OBS or the game can't prepare the frame for output in time.

A disk problem may manifest differently: recording stops, the file comes out corrupted, delays appear during saving, or the game starts accessing the drive with long pauses. That's why OBS statistics alone aren't enough—also monitor disk usage in the operating system.

If rendering is lagging, try limiting the game's frame rate, reducing unnecessary scaling, and closing unnecessary sources. For encoding problems, check the NVENC preset, resolution, frame rate, and simultaneous operation of both outputs. If network losses are increasing, first reduce the stream bitrate or fix the cause of the unstable connection.

A stable broadcast remains the priority during streaming. If your computer can't handle NVENC for both streaming and recording at CQP 18, first raise the CQP value to 20–22, simplify the recording, or move it to another drive. It's better to get a slightly more compressed local file than to lose frames in the stream.

Checking Before a Full Broadcast

After setting up, don't immediately start a multi-hour stream. Make a short recording at maximum load for your computer: open the game, turn on the webcam, alerts, browser sources, and microphone. Then separately test the stream with the same resolution, frame rate, bitrate, and encoder.

Review the beginning, middle, and end of the file. Pay attention to fast camera turns, small text, dark areas, particles, and scenes with lots of motion. That's where quality issues, overly aggressive compression, or scaling problems are most often visible.

Check the audio on all the tracks you need, import the file into a video editor, and try scrubbing. After a normal stop, make sure auto-remux created the MP4. To test a crash scenario separately, it's enough to verify that the MKV recording appears in the folder before OBS finishes closing.

If you're satisfied with the result, save the OBS profile for that specific task. You can use separate profiles for different games, but before an important stream you should still check the scene, free space, and drive condition. A graphics card driver update, OBS update, or codec change can alter the load.

Common Mistakes with Separate Settings

One common mistake is selecting "Same as stream" for recording and then expecting CQP quality. In this case, the local file gets the stream's parameters. Another mistake is setting CQP 18 without checking the size and leaving the recording on a drive that's already busy with the game or system.

You shouldn't immediately choose HEVC or AV1 just because of the smaller file size. First check codec support in your video editor and on the device where the recording will be played. Also, don't manually rename MKV to MP4 or assume that enabling auto-remux protects against any crash.

Another problem is checking only the first few minutes. The drive may start slowing down later, free space may run out, and a demanding scene may only appear in the middle of the game. Test the full working scenario and look not only at the image but also at OBS statistics, audio, and drive load.

Quick Step-by-Step Guide

1. Open "Settings" → "Output" and enable advanced mode.
2. For Twitch 1080p60, set NVENC H.264, CBR, 6000–8000 kbps, and a keyframe interval of 2 seconds, after checking the parameters against the platform's current requirements.
3. In the recording section, disable "Same as stream," select NVENC H.264, and CQP 18–22 mode.
4. Specify a separate folder on a tested drive, preferably an SSD, and select MKV.
5. In the "Advanced" section, enable automatic remux to MP4 so that after a normal stop you get a compatible file without re-encoding.
6. Assign the audio tracks and check the microphone, game, and overall mix.
7. Make a test recording and stream, check OBS statistics, HDD or SSD load, file size, and the quality of complex scenes.