OBS Studio logo
OBS
Open Broadcaster Software®️
Discord icon Discord
Twitter
OBS Studio screenshot Mastodon
GitHub

OBS Studio for Windows

Last updated: September 1, 2026

Windows is the platform where OBS Studio has the widest hardware support: three separate capture paths, encoders from all three GPU vendors and direct access to desktop audio without extra drivers. This page covers what that means in practice.

Capture modes on Windows

Windows offers three ways to get video into OBS, and picking the right one solves most quality and performance complaints before they start.

  • Display Capture mirrors an entire monitor. Simplest option, good for tutorials and software demos.
  • Window Capture follows one program even when it is behind other windows. Use it when you do not want notifications or a second monitor on screen.
  • Game Capture hooks a full-screen Direct3D or Vulkan game and is the most efficient of the three for gameplay.

If a capture shows a black rectangle, it is usually a GPU-selection or permission problem rather than a broken install; the black screen fix walks through it.

Hardware encoding

Software encoding with x264 uses the CPU and gives the best quality per bitrate, but it competes with games and other applications. On Windows you can move that work to the GPU instead:

  • NVIDIA cards expose NVENC, including the newer HEVC and AV1 paths on recent generations.
  • AMD cards expose AMF.
  • Intel processors with integrated graphics expose Quick Sync.

For screen recording, hardware encoding at a generous bitrate is usually the right trade. Recommended starting values are collected on the OBS settings page.

Audio on Windows

OBS reads desktop audio directly through WASAPI, so you can record system sound without a virtual cable. Two device slots are configured by default: Desktop Audio and Mic/Auxiliary Audio. Add extra application-specific captures when you need to keep game sound and voice chat on separate tracks.

If the meters stay flat, start with the no-audio checklist.

Keeping performance stable

Encoding overload and dropped frames on Windows almost always come from one of four places: an output resolution higher than the hardware can encode in real time, a CPU-bound x264 preset, a full disk, or a network upload that cannot sustain the chosen bitrate.

Detailed remedies live in high CPU usage and dropped frames.

Related guides