How to Optimize NVIDIA GPU for OBS Studio

For most users, the important changes are selecting an NVIDIA NVENC encoder, using CBR for streaming, setting a two-second keyframe interval, choosing the P5 or P6 preset, enabling Psycho Visual Tuning and limiting the game’s frame rate. Local recordings need a different setup, normally MKV with CQP rate control rather than the fixed bitrate used for livestreaming.

This article explains how to optimize NVIDIA GPU for OBS Studio on Windows 11 and Windows 10. It includes recommended settings for streaming and recording, NVIDIA Control Panel adjustments, laptop GPU selection and fixes for encoder overload, skipped frames, blurry video and poor game performance.

Why NVIDIA NVENC Is Better for OBS

OBS can encode video with the processor or a supported hardware encoder. The x264 option uses the CPU, while NVIDIA NVENC uses dedicated video-encoding hardware on a compatible NVIDIA GPU.

NVENC does not mean OBS stops using the rest of the graphics card. OBS still requires GPU resources to capture sources, scale video, composite scenes, apply filters and render the final frame. NVENC handles the compression stage, but a game that consumes every available GPU resource can still starve OBS of the capacity it needs.

This distinction explains why some users see an Encoding Overloaded warning even though they selected NVENC. The encoder may be available, but the entire OBS rendering pipeline is competing with the game, browser sources, camera effects and overlays.

NVIDIA GPUs can expose one or more of these encoders in OBS:

• NVIDIA NVENC H.264: Offers the widest compatibility with livestreaming platforms, video players and editing applications.
• NVIDIA NVENC HEVC: Produces more efficient video than H.264 and is useful for compatible streaming services, HDR and local recording.
• NVIDIA NVENC AV1: Offers excellent compression efficiency on supported RTX 40-series and newer GPUs, but the destination platform and editing software must accept AV1.

NVIDIA’s current NVENC OBS recommendations identify H.264 and HEVC support on RTX 20, 30, 40 and 50-series cards, while AV1 encoding is available on the RTX 40 and 50 series. Older GeForce cards may also provide NVENC, but their codec support and output quality depend on the GPU generation.

Check That OBS Detects NVIDIA NVENC

Before changing advanced settings, confirm that OBS can see the encoder.

1. Open OBS Studio.
2. Click Settings.
3. Select Output.
4. Change Output Mode to Advanced.
5. Open the Streaming tab.
6. Expand the Video Encoder menu.

Look for an option such as:

• NVIDIA NVENC H.264
• NVIDIA NVENC HEVC
• NVIDIA NVENC AV1

The exact wording can differ between OBS releases. If no NVIDIA option appears, check Device Manager > Display adapters and confirm that Windows detects the GPU without a warning symbol.

Update OBS Studio and the NVIDIA driver before troubleshooting further. A corrupted or incomplete display driver can prevent OBS from accessing NVENC. My article on how to reinstall NVIDIA drivers covers both the standard reinstall and a complete driver cleanup.

Do not download unofficial NVENC plugins or modified graphics drivers to make the option appear. NVENC support is already built into current OBS Studio releases when compatible NVIDIA hardware and drivers are installed.

Best OBS Settings for NVIDIA GPU Streaming

There is no single configuration that is perfect for every streaming service, game and internet connection. The following settings form a strong starting point for a single-PC gaming stream.

Open Settings > Output, set Output Mode to Advanced, and select the Streaming tab.

OBS setting	Recommended starting value
Video Encoder	NVIDIA NVENC H.264, or AV1 when supported by the GPU and platform
Rate Control	CBR
Bitrate	Set according to the platform and tested upload speed
Keyframe Interval	2 seconds
Preset	P6: Slower (Better Quality), or P5 for more GPU headroom
Tuning	High Quality
Multipass Mode	Two Passes at Quarter Resolution
Profile	High for H.264, Main for HEVC or AV1
Look-ahead	On when GPU headroom is available; off during overload
Psycho Visual Tuning	On
GPU	0 on a normal single-GPU computer
Max B-frames	4 with Look-ahead; 2 when Look-ahead is off

Some OBS versions or encoder combinations do not show every option in this table. Use the closest available setting and do not install an older OBS version merely to reproduce a menu from a screenshot.

Choose the Correct NVENC Codec

Use NVIDIA NVENC H.264 when compatibility is the priority. It remains the safest choice for a service that does not clearly advertise HEVC or AV1 ingestion.

Use NVIDIA NVENC AV1 when all three conditions are true:

1. The NVIDIA GPU supports AV1 encoding.
2. The streaming destination accepts AV1.
3. Your OBS connection or streaming mode exposes AV1 for that service.

Use HEVC for a compatible service or workflow, particularly when HDR is required. Do not select a codec only because it is newer. A stream will fail if the destination does not accept it.

Use CBR for Livestreaming

CBR means Constant Bitrate. Streaming services generally expect a predictable bitrate because it makes live delivery and transcoding easier to manage.

Avoid CQP for a normal livestream. CQP changes the amount of data used according to scene complexity, which is excellent for local recordings but can create bandwidth spikes during a broadcast.

Enable Enforce Streaming Service Encoder Settings when OBS displays the option. This allows OBS or the connected service to correct values that do not meet the platform’s requirements.

Set a Safe Streaming Bitrate

The bitrate should satisfy the platform without consuming your entire upload connection. Check the service’s current recommendation before going live, as limits and supported modes can change.

As a practical rule, leave upload bandwidth available for game traffic, voice chat and momentary connection changes. A speed test showing 10 Mbps upload does not mean a stream should use all 10 Mbps.

A useful starting range is:

Stream format	Practical starting bitrate
720p at 30 FPS	2,500 to 4,000 Kbps
720p at 60 FPS	3,500 to 6,000 Kbps
1080p at 30 FPS	4,500 to 6,000 Kbps
1080p at 60 FPS	6,000 to 9,000 Kbps
1440p at 60 FPS	9,000 to 18,000 Kbps
4K at 60 FPS	Platform-dependent, usually requiring far more bandwidth

These are starting ranges, not universal service limits. A platform may accept less, allow more or require a particular codec. High-motion games also need more data than a mostly static talking-head stream. If bitrate is restricted, reducing the output resolution often looks better than forcing a blocky 1080p or 1440p image.

Set the Keyframe Interval to Two Seconds

Enter 2 for the keyframe interval. This is widely required by livestreaming services and gives viewers, players and platform transcoders regular points from which to begin decoding the stream.

Leaving the value at zero lets the encoder decide, but a platform may reject or warn about a stream that does not meet its keyframe requirement.

Choose P5 or P6 Preset

The NVENC preset controls the balance between encoder workload and output quality.

• P6: Slower (Better Quality): A strong choice when the GPU has sufficient headroom.
• P5: Slow (Good Quality): Better for demanding games, lower-end GPUs or systems experiencing rendering and encoding lag.
• P7: Can add workload for a relatively small quality improvement and is rarely the first setting I would choose for a single-PC gaming stream.
• P1 to P4: Useful only when performance or simultaneous encoding demands matter more than maximum quality.

Start with P6. If OBS Stats shows skipped frames caused by encoding lag, switch to P5 before making several unrelated changes.

Use Quarter-Resolution Multipass

Set Multipass Mode to Two Passes (Quarter Resolution). It provides a sensible balance between analysis quality and GPU workload.

Full-resolution two-pass encoding can consume more GPU resources. It may be suitable when plenty of headroom is available, but it should not be enabled simply because it sounds better. A stable quarter-resolution pass produces a better stream than a full-resolution pass that causes missed frames.

Configure Look-ahead and Psycho Visual Tuning

Psycho Visual Tuning improves how the encoder spends the available bitrate, especially during movement. Leave it enabled for a normal gaming stream unless a specific compatibility problem appears.

Look-ahead allows the encoder to vary the number of B-frames based on the content. It can improve compression, but it also uses CUDA resources. Enable it when GPU utilisation remains under control. Turn it off when a demanding game pushes the graphics card close to full utilisation or OBS reports encoding lag.

When Look-ahead is enabled, NVIDIA recommends up to four B-frames. When it is disabled, use two.

Best OBS Recording Settings for NVIDIA GPU

Local recording is different from livestreaming. The recording does not have to maintain a fixed network bitrate, so quality-based rate control is usually the better option.

Open Settings > Output > Recording and use these starting values:

OBS setting	Recommended recording value
Type	Standard
Recording Format	MKV
Video Encoder	NVENC AV1, HEVC or H.264 based on compatibility
Rate Control	CQP
CQ Level	18 to 23 for balanced quality and file size
Keyframe Interval	2 seconds or 0 when no editor requires a fixed interval
Preset	P5 or P6
Tuning	High Quality
Multipass Mode	Two Passes at Quarter Resolution
Psycho Visual Tuning	On
GPU	0

Record in MKV Instead of MP4

MKV is the safer recording container because an interrupted session is less likely to make the entire file unusable. Power loss, an application crash or an accidental shutdown can damage an unfinished MP4 recording.

If an editor requires MP4, use File > Remux Recordings in OBS after recording. Remuxing changes the container without re-encoding the video, so it is normally fast and does not reduce image quality.

Choose CQP and a Suitable CQ Level

CQP aims for a selected quality level and allows bitrate to change with the complexity of the scene. Lower CQ numbers produce higher quality and larger files.

• CQ 15 to 17: Very high quality with large files.
• CQ 18 to 20: Strong quality for gameplay recording and editing.
• CQ 21 to 23: Smaller files with acceptable quality for many users.
• Above 23: More compression and a greater risk of visible artifacts.

Start at CQ 20, record a demanding two-minute section and inspect both image quality and file size. Move to 18 if fine details look soft, or to 22 if the files are unnecessarily large.

Pick AV1, HEVC or H.264 for Recording

AV1 offers excellent compression on compatible RTX GPUs, but it may not work smoothly in older editing software or hardware. HEVC is efficient and widely useful for high-resolution recording, although licensing and software support can vary. H.264 produces larger files at similar quality but remains the easiest format to edit, upload and play.

If a recording imports as audio-only, shows a black preview or plays slowly in an editor, switch from AV1 to HEVC or H.264 before assuming the GPU is faulty.

Configure OBS Video Resolution and Frame Rate

Encoder settings cannot compensate for an unrealistic resolution and frame-rate combination.

Open Settings > Video and check:

• Base (Canvas) Resolution: Usually the monitor or game resolution used to arrange sources.
• Output (Scaled) Resolution: The actual resolution sent to viewers or written to the recording.
• Downscale Filter: Lanczos provides a sharp result, while Bicubic can reduce load on a struggling system.
• Common FPS Values: Use 60 for smooth gameplay when the computer and connection can maintain it; use 30 when stability or bandwidth is more important.

Do not set the canvas to 4K just because the GPU can run a game at 4K. If the final stream is 1080p, oversized browser sources, video files and camera inputs can add unnecessary processing.

For fast shooters and racing games, 720p60 can look cleaner than 1080p60 at the same restricted bitrate. The lower resolution assigns more bits to each pixel and reduces compression artifacts during rapid movement.

Optimize NVIDIA Control Panel for OBS

Many online tutorials recommend changing every NVIDIA Control Panel option. Most 3D settings do not improve NVENC quality. Aggressive global changes can increase power consumption or alter the behaviour of every game without helping OBS.

Create an OBS-specific profile instead:

1. Right-click the desktop and open NVIDIA Control Panel.
2. Select Manage 3D settings.
3. Open the Program Settings tab.
4. Click Add and select OBS Studio.
5. If it does not appear, browse to the OBS executable, normally obs64.exe.

Use these conservative values:

NVIDIA Control Panel setting	Suggested value for OBS
CUDA GPUs	All
OpenGL rendering GPU	Your NVIDIA GPU
Power management mode	Normal first; Prefer maximum performance only if clocking problems occur
Low Latency Mode	Off
Max Frame Rate	Off for OBS itself
Vertical Sync	Use the 3D application setting
Texture filtering options	Leave at default

Prefer maximum performance can stop an application-specific clock-down problem, but it also increases power use, heat and fan activity. It is not necessary on every system. Apply it to the OBS profile only if monitoring shows the GPU dropping to an unsuitable power state during recording or streaming.

If NVIDIA Control Panel is missing or refuses to open, use my NVIDIA Control Panel installation steps before changing the profile.

Make Windows Use the NVIDIA GPU for OBS

This step is particularly important on laptops containing both integrated graphics and a discrete NVIDIA GPU.

1. Open Settings.
2. Go to System > Display > Graphics.
3. Add or select OBS Studio.
4. Click Options.
5. Choose High performance, which should display the NVIDIA GPU.
6. Save the change and restart OBS.

Game Capture generally works most reliably when OBS and the game run on the same GPU. Forcing OBS onto the NVIDIA GPU while the game runs on integrated graphics, or doing the reverse, can introduce capture and frame-copy problems.

On a desktop with one active NVIDIA graphics card, Windows normally selects it automatically. Forcing the preference is unnecessary unless Task Manager shows OBS using a different adapter.

Run OBS Studio as Administrator

Running OBS as administrator can help Windows reserve sufficient GPU capacity when a game would otherwise take priority.

1. Close OBS Studio.
2. Right-click its shortcut.
3. Select Run as administrator.
4. Approve the User Account Control prompt.

The official OBS encoding performance troubleshooting page recommends this as a quick fix for GPU overload on Windows. It does not make a weak GPU faster, but it can improve scheduling when OBS struggles to render while a game is under heavy load.

If the change helps, open the shortcut’s Properties > Compatibility tab and enable Run this program as an administrator. Remember that applications running with different permission levels may interact differently. A capture source or plugin can sometimes require matching permissions.

Leave GPU Headroom for OBS

The most effective NVIDIA GPU optimisation is often reducing the game’s demand rather than increasing OBS quality settings.

OBS requires time on the GPU to build every frame. When a game uses 99 or 100 percent of the graphics card, NVENC’s dedicated encoder does not eliminate competition for rendering, texture copying and compositing resources.

Try these changes in order:

1. Cap the game frame rate at the monitor’s refresh rate.
2. If utilisation remains too high, use a lower cap that the GPU can hold consistently.
3. Reduce ray tracing, shadows, volumetric effects or resolution scaling.
4. Use DLSS or another supported upscaler at a sensible quality mode.
5. Change from exclusive full screen to borderless only if capture behaviour improves.
6. Close GPU-heavy background applications.
7. Reduce OBS output from 60 FPS to 30 FPS if the system still cannot keep up.

For example, a game fluctuating between 160 and 210 FPS can consume almost every available resource even on a 144 Hz display. A 144 FPS or 120 FPS cap may have little effect on perceived smoothness while giving OBS enough room to render reliably.

Disable Duplicate Recording and Overlays

Running OBS recording alongside NVIDIA Instant Replay, Xbox background capture and another clipping tool creates unnecessary competition for encoding resources, storage bandwidth and hotkeys.

If OBS is your only recorder:

• Turn off NVIDIA Instant Replay.
• Disable automatic highlights you do not use.
• Turn off Windows background game recording.
• Close third-party clipping applications.
• Disable browser and chat overlays temporarily while testing.

You do not have to remove the NVIDIA App or graphics driver. My article explaining how to turn off NVIDIA Overlay shows how to disable its recording interface without affecting normal graphics performance.

The overlay is not always harmful. Disable it when diagnosing stuttering, encoder-session limits or shortcut conflicts, then enable it again if OBS performance does not change.

Keep OBS Scenes Efficient

A simple scene uses fewer resources than one filled with animated browser sources, filters and oversized media files.

To reduce scene load:

• Use Game Capture instead of Display Capture for compatible games.
• Avoid capturing the same game with multiple source types.
• Set camera resolution to what the layout actually displays.
• Replace static browser overlays with image sources where possible.
• Remove unused filters rather than merely hiding them.
• Resize video assets before importing them instead of scaling huge files inside OBS.
• Split extremely large scene collections into focused collections.
• Close preview docks and browser panels that are not needed during a broadcast.

Hidden sources can still use resources depending on how they are configured. Use Unload image when not showing, Close file when inactive or similar source options when available and appropriate.

Adjust Windows Gaming and Graphics Settings

Keep Windows Game Mode enabled on a current Windows 11 or updated Windows 10 system unless testing shows a repeatable problem. Recent OBS and NVIDIA guidance is designed around modern Windows scheduling behaviour.

Hardware-accelerated GPU scheduling, often shortened to HAGS, can help Windows balance game, OBS and other GPU workloads on supported systems. To check it:

1. Open Settings > System > Display > Graphics.
2. Select Change default graphics settings or Default graphics settings.
3. Enable Hardware-accelerated GPU scheduling.
4. Restart Windows.

HAGS is not a guaranteed improvement on every combination of driver, GPU and capture software. If stuttering begins only after enabling it, turn it off, restart and compare another recording under the same conditions.

Also disable Windows background recording if OBS performs all captures:

1. Open Settings > Gaming > Captures.
2. Turn off Record what happened or the equivalent background-recording option.

Leave Xbox Game Bar installed if you use its other features. The important change is preventing two applications from continuously recording the same gameplay.

Use Game Ready or Studio Driver for OBS

Both NVIDIA Game Ready and Studio drivers support NVENC and OBS Studio. Choose the branch that matches the rest of the computer’s workload.

• Game Ready Driver: Suitable for users who stream newly released games and want day-one game optimisations.
• Studio Driver: Suitable for users who prioritise tested stability in supported creative applications and do not need every game update immediately.

Switching to Studio Driver does not automatically improve stream quality. The NVENC settings, GPU generation, available headroom and scene design have a much larger effect. Use the newest stable driver that works well with your games and OBS setup.

If problems begin immediately after a driver update, consider returning to the previous working release rather than changing ten OBS settings. The steps in how to roll back an NVIDIA driver explain how to restore an earlier version safely.

Recommended Settings by NVIDIA GPU Level

The exact GPU model, game and connection matter more than a broad product group. These profiles provide realistic starting points rather than fixed rules.

NVIDIA GPU level	Streaming starting point	Recording starting point
Older GTX with NVENC	720p60 or 1080p30, H.264, P5	1080p30/60 H.264, CQP 20 to 23
GTX 16 series	1080p60 H.264, P5 or P6	1080p60 H.264/HEVC, CQP 18 to 22
RTX 20 or 30 series	1080p60 H.264, or compatible HEVC, P6	1080p60 or 1440p60 HEVC/H.264, CQP 18 to 21
RTX 40 or 50 series	1080p60 or 1440p60, AV1 where supported	AV1 or HEVC at the required resolution, CQP 18 to 21

A high-end GPU does not justify selecting 4K60 if the platform bitrate, upload connection or viewers cannot support it. Resolution is only one part of stream quality.

How to Read OBS Stats

Open View > Stats while running a test stream or recording. The type of dropped frame tells you where to troubleshoot.

Dropped Frames Due to Network

This points to the connection between OBS and the streaming server, not the NVIDIA GPU.

Try a lower bitrate, wired Ethernet, another ingest server and a check for other upload activity. Changing NVENC presets will not repair an unstable internet connection.

Frames Missed Due to Rendering Lag

OBS could not render the scene in time. The GPU is usually overloaded by the game, scene composition or another application.

Cap game FPS, reduce game graphics, simplify OBS scenes, run OBS as administrator and confirm that the game and OBS use the correct GPU.

Skipped Frames Due to Encoding Lag

The encoder could not finish frames quickly enough.

Change P6 to P5, disable Look-ahead, keep quarter-resolution multipass, reduce the output resolution or frame rate, and stop duplicate recording tools.

High CPU Usage

Confirm that OBS is using NVIDIA NVENC rather than x264. Browser sources, filters, plugins and applications can still consume CPU even when NVENC is active.

Fix OBS Encoder Overloaded on NVIDIA GPU

Apply these fixes one at a time and make a short test recording after each change:

1. Run OBS as administrator.
2. Cap the game’s frame rate.
3. Turn off NVIDIA Instant Replay and other capture tools.
4. Change the NVENC preset from P6 to P5.
5. Disable Look-ahead.
6. Use Two Passes at Quarter Resolution instead of Full Resolution.
7. Reduce the output from 1440p to 1080p or from 1080p to 720p.
8. Change 60 FPS to 30 FPS.
9. Simplify browser sources and filters.
10. Update or reinstall the NVIDIA driver.

Do not immediately increase process priority to Realtime in Task Manager. Realtime priority can starve essential Windows processes and make the computer less stable. Running OBS as administrator is the safer first scheduling adjustment.

Fix Blurry or Pixelated OBS Streams

A blurry stream does not always mean the NVIDIA GPU is poorly optimised. It commonly results from insufficient bitrate for the selected resolution and the amount of motion on screen.

Try the following:

• Reduce output resolution while keeping the same allowed bitrate.
• Use AV1 or HEVC only when the platform supports it.
• Enable Psycho Visual Tuning.
• Use P6 if the GPU has enough headroom.
• Select Lanczos when downscaling and performance is stable.
• Avoid enlarging a low-resolution source beyond its native size.
• Check that the stream is not being viewed at a lower player quality setting.
• Improve lighting for cameras, as sensor noise is difficult to compress.

For a fast game at a restricted bitrate, 936p or 720p may preserve movement better than 1080p. Test the actual game rather than judging quality from a static desktop image.

Fix OBS Recording Stutter While the Game Is Smooth

When gameplay looks smooth but the recording stutters, open OBS Stats. Rendering lag indicates that the game is monopolising the GPU. Encoding lag points more directly to the encoder settings or simultaneous encode sessions.

Limit the game frame rate and disable background recorders first. Then change P6 to P5 and turn off Look-ahead. Confirm that the recording drive is not full, unusually slow or busy with another large transfer.

Pressing Windows + Ctrl + Shift + B resets the Windows graphics driver, but it should be used for a temporary display or driver glitch, not as a routine OBS optimisation. My Windows graphics reset article explains what the shortcut does and when it is appropriate.

Frequently Asked Questions

What is the best NVIDIA encoder for OBS Studio?

NVIDIA NVENC H.264 is the safest choice for broad streaming compatibility. AV1 can deliver better quality at a comparable bitrate on supported RTX 40-series or newer GPUs when the streaming platform accepts it. For local recording, AV1 or HEVC can reduce file size, while H.264 remains easiest to edit and play.

Should OBS use NVENC or x264?

Use NVENC for a single-PC gaming stream when a compatible NVIDIA GPU is available. It shifts video compression away from the CPU and normally leaves more processor resources for the game and other applications. x264 may still suit a dedicated streaming computer or a particular quality workflow.

Should I use P5 or P6 in OBS?

Start with P6 for high-quality streaming when the GPU has enough headroom. Use P5 if OBS reports encoding lag, the game is demanding or you run several simultaneous encodes. Stability matters more than the small quality difference between presets.

Should Look-ahead be enabled in OBS?

Enable Look-ahead when GPU utilisation is controlled and the stream remains stable. Disable it when OBS skips frames, a game drives the GPU near full utilisation or you need to reduce CUDA workload.

Does NVIDIA Control Panel improve OBS stream quality?

It has a limited role. Selecting the correct GPU and resolving a power-state problem can help, but most NVIDIA Control Panel 3D settings do not change NVENC quality. OBS encoder, resolution, bitrate and scene settings have a greater effect.

Should I run OBS as administrator?

Yes, especially for gaming streams that experience rendering or encoding lag. Running as administrator can help Windows reserve GPU capacity for OBS. It does not replace reasonable game, encoder and resolution settings.

Why does OBS still lag with an RTX GPU?

The game may be using nearly all GPU resources, OBS scenes may be too complex, the output may be too demanding or another recorder may be active. NVENC has dedicated encoding hardware, but OBS still needs the GPU to capture, composite and render frames.

What CQ level should I use for NVIDIA recording?

Start at CQ 20. Use CQ 18 for higher quality and larger files, or CQ 22 for smaller files. Record a short high-motion test and inspect the result before committing to a long session.

Is AV1 always better than H.264 in OBS?

AV1 is more compression-efficient, but it is not always the correct choice. The NVIDIA GPU, streaming platform, playback device and editing application must support it. H.264 remains the most compatible option.

Once the settings are stable, save them as a separate OBS profile and create a matching scene collection. This makes it easier to experiment without losing a known working configuration. Run a private or unlisted test stream for at least ten minutes, watch OBS Stats and inspect a high-motion section before relying on the setup for an important broadcast.

You might like to see:

• Switching From NVIDIA to AMD GPU: Steps to Follow
• NVIDIA Filters Not Working? How to Fix It
• How to Install NVIDIA Control Panel on Windows 11 or 10
• NVIDIA Overlay Shortcut: Hotkeys and How to Change Them