Single-PC Streaming Setup

Who this setup is for

This setup is for gaming or desktop content where the application and OBS run on the same computer. This blueprint starts with the signal path and the host connections, because a list of popular gear cannot show whether the parts can exchange the required video, audio, control and power signals.

A second HDMI capture path is usually unnecessary for a game rendered on the same host. Map the exact computer, ports, sources and equipment already owned in the setup builder. Resolve every required port, cable and software mode before buying around it.

Choose the smallest complete path. A control surface, second light, premium camera or external mixer can improve operation, but none repairs a missing host port, unsupported mode or audio return that feeds back into itself. Add optional parts only after this base route records cleanly.

Signal path

The game or application is captured inside OBS, while camera USB and microphone USB or interface USB connect directly to the same computer. OBS owns the program mix, recording tracks and stream output; the monitor or gaming display stays connected to the graphics system.

Write each hop as source output → cable → receiving input → software source → destination. Put the connector name and required protocol beside the cable. A USB-C plug describes a shape; it does not prove USB 3 speed, video support, charging power or device compatibility.

When the route uses capture, keep capture and passthrough as two rows. Capture is what the streaming computer receives; passthrough is what the display receives from HDMI output. A device can pass a high mode while capturing another, so never copy the larger passthrough number into recording settings.

Eight component decisions

Resolve these eight decisions in order. Each either removes a signal-path blocker or defines a destination that later routing depends on.

• Render headroom: Check CPU/GPU load with the game, encoder, camera and normal background apps running together.
• Game capture: Prefer OBS software capture for the same host; use display capture only when the application path requires it.
• Camera: Choose resolution and frame rate for the scene size rather than the camera headline maximum.
• Voice path: Pick direct USB for simplicity or XLR plus interface for the routing and input path you specifically need.
• Monitoring: Monitor at the microphone/interface where possible and avoid monitoring the OBS program back into desktop audio.
• Track plan: Decide which sources must be combined live and which should remain separate in a local recording.
• Control: Map only live-critical actions such as mute, scene, record and marker; folders can hold setup actions.
• Upload/output: Set platform output from sustained upload and leave headroom for the rest of the household.

Compatibility checks before purchase

Run the pre-stream checklist after drawing the physical plan. Match the exact model, host operating system, port mode and destination.

Match each model suffix and generation to its manual. If a required cable, mode, included part or operating system is not listed for that exact device, keep that requirement unresolved and choose another route when it is essential.

• Host load: A setup that is stable on a blank scene must still pass under the real game and encoding workload.
• USB topology: High-bandwidth camera and audio devices should be tested on known direct ports, especially when hubs are involved.
• Audio ownership: Every source needs one capture path and each monitor return needs one destination.
• Software versions: Confirm current OBS, device driver and routing-app support for the operating system.
• Recording storage: Measure free space and sustained write behavior for the chosen recording format.
• Output profile: Verify the current destination guidance; Twitch’s exact profile remains unknown until rechecked.

Connect and configure in this order

Mount and power the equipment before connecting data cables. Leave slack at camera and microphone sockets, keep power bricks from hanging on ports, and label both ends of any cable that disappears behind the desk.

Connect one signal family at a time: display, capture or camera, microphone and monitoring, then control. Confirm the operating system sees each device before opening OBS, and select exact device names instead of an unspecified default.

Build one scene and one monitoring route first. Record representative content and alerts locally, then add secondary scenes, effects and automation only after the file contains the intended picture and every required audio source exactly once.

• Draw the physical route and label every source, input, output and host port.
• Connect display passthrough, where used, and prove the display mode before configuring capture.
• Connect the video source to a direct suitable host port and select its supported capture mode.
• Connect the microphone or interface, then plug headphones into the output that owns monitoring.
• Add OBS sources one at a time; disable duplicate global devices or duplicate source audio.
• Set OBS canvas, scaled output, frame rate and encoder to the selected destination profile.
• Make a local recording, inspect it outside OBS, then run a private destination test.

Realistic ways to apply the blueprint

For a single-PC game stream, OBS Game Capture can take the game directly while a USB webcam and microphone enter as separate sources. That keeps HDMI and capture hardware out of a path that does not need them.

For a software tutorial, Window Capture plus a small camera scene and USB voice path may be sufficient. Separate microphone and application audio tracks in the recording when later editing matters.

If neither pattern matches, use the cable and port guide to identify the physical links, then return to this blueprint. The related pages OBS audio routing, stream and VOD track guide cover the decisions that commonly change this route.

Four failure states to diagnose

Change one variable at a time. Start at the first missing hop in the diagram instead of replacing the most expensive component; a local recording separates a source or routing fault from a destination or network fault.

• Encoder overload: Lower the rendering or output workload, cap the game where appropriate, and retest the full scene.
• Duplicate game audio: Disable one of the global/source capture paths and keep the intentional instance.
• Camera disconnects under load: Move it to a direct suitable port and test USB bandwidth with all devices active.
• Clean local file, unstable destination: Inspect upload headroom and destination diagnostics without changing the proven local sources.

What to keep, verify and buy last

Start with equipment already owned. Keep an item when its exact ports and modes cover the route. Mark it conditional when one required fact is unresolved, and blocked when a hard mismatch prevents the signal from reaching its destination.

Buy connection-critical parts before convenience parts. In this blueprint the first purchase should resolve the earliest blocked render headroom or game capture decision. A second light, larger control surface or higher camera mode belongs later unless one of the eight decisions identifies it as the actual blocker.

Match every product label, suffix and generation to the linked record and manual. Family names can hide different cables, software, mounts, host requirements, input counts and capture matrices; count an unlisted included part as a separate purchase.

Enter current costs when assembling the setup. Compare the complete path, including microphone, monitoring, cables, power and mounts, with the cost of keeping a working route. Buy an upgrade only when it solves a named signal, workflow or reliability problem.

Five tests before going live

Run a representative test after the computer has reached its normal load and every intended USB device is connected. A brief preview does not exercise heat, power management, sustained USB traffic or a full audio return.

Keep the first destination test private or unlisted where available. Inspect the received feed on another device with its volume low enough to avoid sending room audio back into the microphone.

Save the working OBS profile and scene collection, exact device names, physical port map, output mode and any per-source delay or routing assignment. When a later change fails, restore one known working element at a time.

Call the result ready only when every required path passes together. A conditional route works only with a named accepted mode, port or workaround; a blocked route is missing a required source or destination and is not ready for a live session.

Check the distinct OBS Stats counters if the received feed stutters or the rehearsal reports dropped frames.

• Record several minutes of motion and speech; inspect picture continuity, lip sync and dropped-frame counters.
• Listen on the creator headphones and in the recorded file; confirm each source is present once and muting works.
• Exercise the real display resolution, refresh rate and HDR choice while capture remains stable.
• Trigger scene changes, alerts, guest audio and any control actions used during the session.
• Run the destination test with upload headroom and confirm the received feed on a separate device.

Equipment for these connections

Start with the needed role. Check the complete profile before adding a product to your setup.