On Windows 10 version 1809 and later, and Windows 11, you can assign OBS a graphics preference under Settings > System > Display > Graphics. The right choice depends on how OBS captures the picture: OBS recommends High Performance for Game Capture and Window Capture, and Power Saving for Display Capture.
That Windows preference is not the same as choosing an encoder in OBS. For a dedicated loop PC, identify the capture path first, then leave a stable configuration alone unless a test shows a problem.
Check whether the PC has multiple GPUs
The graphics preference matters most on laptops and systems with more than one GPU, such as a laptop with integrated graphics and a discrete graphics chip. Windows can choose which GPU runs OBS, but there is no general rule that a dedicated streaming computer must always use its most powerful GPU. A desktop with one GPU, or a setup that is already stable, may have no useful change to make.
To check what is installed, open Device Manager from the Windows Start menu and expand Display adapters. You can also open Task Manager > Performance and review the GPU entries while OBS is running. Names and numbering vary by system, so use the adapter names rather than assuming “GPU 0” is the integrated one or the discrete one.
The number of adapters alone does not determine a setting. Ask how the image enters OBS. Is it a local video loaded as a media source, a whole display, an application window, or a game? These are different capture routes. A loop built from a media source should not automatically be treated as Game Capture just because it plays continuously.
If your setup uses an OBS playlist or media source, the choice of source and its behaviour over time are separate questions from GPU assignment. The guide to OBS media source versus VLC for playlist rotation can help clarify that distinction. First establish what OBS is actually displaying; then use the Windows preference guidance only where it covers that capture type.
Find OBS in Windows Graphics settings
OBS’s GPU Selection Guide documents a path for supported Windows versions: add the OBS executable, C:\Program Files\obs-studio\bin\64bit\obs64.exe, under Settings > System > Display > Graphics. The wording can vary slightly between Windows releases, but look for the per-app graphics preference in Display settings. OBS’s GPU Selection Guide gives the current instructions and capture-type recommendations.
In Graphics settings, choose the option to add a desktop app, browse to the executable, and select it. If OBS was installed somewhere other than the standard location, browse to the actual obs64.exe file instead. Do not add a shortcut file or a launcher if Windows is asking for the application executable.
If you are unsure where OBS is installed, right-click the OBS shortcut and open its properties. The target field can show the executable location. Check that the path ends with obs64.exe; on a 64-bit Windows installation this is the application file used in the documented guide. If your OBS installation has been moved or updated, verify the path rather than assuming the example applies unchanged.
After adding OBS, open its entry and select Options. Windows normally presents choices such as Let Windows decide, Power Saving, and High Performance. The labels describe a Windows graphics preference for running the application. They do not select a video codec or promise that the stream will perform better.
Set the preference for the capture type
OBS’s documented guidance distinguishes between two capture categories. For Game Capture and Window Capture, OBS recommends High Performance. For Display Capture, OBS recommends Power Saving. On a multi-GPU machine, the names typically correspond to different adapters, but check which adapter Windows associates with each option before saving.
| OBS capture type | OBS’s Windows preference guidance | What to consider |
|---|---|---|
| Game Capture | High Performance | Use the GPU preference OBS recommends for this capture route on a multi-GPU PC. |
| Window Capture | High Performance | The documented guidance groups this with Game Capture. |
| Display Capture | Power Saving | The documented guidance differs from the two capture types above. |
| Media source or capture-card input | No automatic match in the cited table | Identify the actual source path and keep a working preference unless testing points to a problem. |
The distinction is easy to miss because “High Performance” sounds like a universal best setting. It is not. OBS’s table is about capture compatibility on multi-GPU systems, not a blanket instruction to force every OBS workload onto a discrete adapter. For a media source or capture-card arrangement, the cited table does not give a dedicated recommendation. Treat any choice there as a testable configuration, not as an official rule for every loop PC.
A local devotional video played through an OBS media source, for example, is not necessarily Display Capture, Window Capture, or Game Capture. If you use Display Capture to show the playback application, you are capturing the display; if you add the file directly as a source, you are using a different route. Be precise about the source instead of applying a setting from a superficially similar setup.
For more source-specific loop troubleshooting, see the guide to fixing OBS playlist audio delay. A GPU preference will not correct an audio sync issue, a missing media file, or a playlist that stops advancing. Matching the fix to the observed fault saves time.
Close OBS before changing the preference
Close OBS before you change its Windows graphics preference. OBS’s GPU guide explicitly includes this step. Save any scene or profile changes first, then exit the application rather than leaving it minimised in the system tray. If OBS remains running, the current process may continue using the GPU it started with, so you would not be testing the newly selected preference cleanly.
After closing OBS, change the Graphics setting, save it, and start OBS again. Confirm that the intended profile and scene collection have loaded. If you use a dedicated PC that restarts or logs in automatically, make the change during a planned maintenance window and check that the streaming application still starts as expected afterwards.
Do not change several unrelated settings at once. If you alter the GPU preference, encoder, output resolution, and bitrate in the same session, a later improvement or failure will be hard to attribute. Record the existing settings or take screenshots, change one item, and observe the result before making another adjustment.
Distinguish GPU preference from encoder selection
Windows Graphics settings decide which GPU runs OBS. OBS’s Output settings decide how the video is encoded for transmission. The two decisions can interact because hardware encoders live on supported hardware, but they are not the same switch. Choosing High Performance in Windows does not itself choose NVENC, and selecting a hardware encoder in OBS does not set Windows’s application preference.
In OBS, open Settings > Output and find the streaming encoder control. The exact options depend on the installed hardware, operating system, OBS version, and output configuration. You might see x264, which uses the CPU, or a hardware option such as NVENC or an encoder exposed by another supported GPU. Do not assume a particular codec or encoder appears on every machine.
OBS explains that hardware encoding uses a specialised component in a GPU and can take encoding work off the CPU. That is a reason to consider a supported hardware encoder, not a guarantee that every hardware encoder, preset, or combination will be best in every configuration. The OBS hardware encoding documentation describes the distinction. If you change encoders, test the resulting stream rather than assuming that the label “hardware” settles the question.
For an always-on loop, the meaningful outcome is stable capture and encoding over a representative run. If OBS statistics report rendering or encoding overload, check actual resource use and competing GPU work before buying hardware. OBS’s encoding performance troubleshooting guide offers steps such as reducing competing workloads; running OBS as administrator is one troubleshooting option for GPU overload on Windows, not a guaranteed fix.
Choose an encoder available on the hardware
Select only an encoder that OBS offers for the installed system. Hardware support varies, so do not prescribe an encoder from a different computer or assume that the newest codec is available. If you are using a hardware encoder, verify that the selected output format and destination accept it, and check OBS’s current controls for that encoder. Keep the Windows GPU preference and the OBS encoder choice as separate entries in your notes.
YouTube’s live encoder guidance lists RTMP/RTMPS ingestion and supports H.264, H.265/HEVC, and AV1, with recommended settings that vary by codec, resolution, and frame rate. It recommends a two-second keyframe interval and says not to exceed four seconds. Consult YouTube’s live encoder settings and bitrate guidance for the current requirements and values for your intended output.
For comparison, YouTube lists the following recommended bitrates for selected 60 fps outputs. These are YouTube’s published recommendations, not a guarantee that a particular connection will sustain them or that every stream needs the highest listed resolution.
| Output | AV1 or H.265/HEVC | H.264 |
|---|---|---|
| 1080p at 60 fps | 12 Mbps | 17 Mbps |
| 1440p at 60 fps | 24 Mbps | 34 Mbps |
| 2160p (4K) at 60 fps | 35 Mbps | 50 Mbps |
Choose a target your source and upload connection can support, and use YouTube’s current table for the intended codec and frame rate. A lower resolution or frame rate can be a sensible choice when it matches the content and the available connection. A static image with devotional audio, for example, may not need the same output settings as a detailed moving scene, but the right choice still depends on your source and audience.
If bitrate is the concern, first inspect stream health and the connection rather than treating GPU selection as a network fix. The bitrate checks for a Hindi devotional playlist focus on the relationship between YouTube warnings and output settings. A graphics preference cannot increase the upload capacity of a JioFiber or other connection.
Test the YouTube loop after the change
Test the actual loop after changing the preference or encoder. Start with the scene and media source you use in production, connect to YouTube using your normal workflow, and verify that the image and sound arrive as intended. Watch the stream health information and OBS statistics while the test runs. YouTube recommends testing before a stream and checking stream health; do not treat a brief preview as proof that an overnight run will behave identically.
Look for distinct kinds of trouble. A missing or black capture may point to a capture-path or GPU-assignment issue. Rendering lag suggests OBS is struggling to compose frames. Encoding overload suggests the encoding work is not completing in time. Dropped network frames point towards delivery rather than which GPU runs OBS. Those indicators are not interchangeable, so note the specific warning before changing settings.
For a dedicated loop machine, the test should include the normal playback path and enough time to catch transitions between items. Check that the playlist advances, audio remains aligned, and the YouTube stream continues to receive a signal. If the channel is important overnight, make a planned check before leaving the system unattended rather than relying on the fact that OBS opened successfully.
If the change does not improve a measured fault, restore the earlier setting. Do not buy a second GPU solely because a loop runs continuously. The useful evidence is what OBS and YouTube report on your actual workload, along with whether a capture source works reliably. Hardware replacement becomes a consideration only after the bottleneck is identified and simpler changes have been tested.
If managing a local PC through every restart and overnight check is the pain point, StreamNeo can take an uploaded video and keep it running as a YouTube live stream while your computer is off, with monitoring and automatic restart if the broadcast drops. It is YouTube-only; it does not change which GPU OBS selects on a PC.
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
Should I always choose High Performance for OBS?
No. OBS’s Windows guidance recommends High Performance for Game Capture and Window Capture, and Power Saving for Display Capture. The documented distinction is most relevant on laptops and multi-GPU systems; it is not a universal requirement for every OBS setup.
Does High Performance select NVENC?
No. The Windows preference chooses which GPU runs OBS, while the encoder is selected separately in OBS’s Output settings. NVENC is only an option if it is available on your hardware and in your OBS setup.
What should I select for an OBS media source?
The cited OBS GPU preference table does not give a dedicated media-source recommendation. Identify the actual capture route, keep a stable configuration unless you see a problem, and test any change against the real loop.
Do I need to buy a more powerful GPU for a 24/7 loop?
Not solely because the stream runs continuously. Check OBS statistics, YouTube stream health, and the specific capture or encoding fault first; only consider hardware changes when the observed bottleneck points to them.