If you want to record a gameplay walkthrough for YouTube, first decide whether the game runs on a Windows PC or a console. That choice determines whether you can capture it directly in OBS or need a separate route to bring console footage into a computer.
A capture card is one way to record console gameplay, not a requirement for every setup. Whatever route you choose, make a short test recording, check the game and commentary audio, then review and prepare the file before you record a full session.
Choose a capture path for your device
For a game running on a Windows PC, start by trying OBS Game Capture. OBS describes it as a direct capture method for DirectX or OpenGL games, and recommends trying it first for game capture. It avoids the extra connection step involved in bringing a console’s HDMI output into your computer.
That does not mean Game Capture behaves identically for every game or operating system. If it does not show the game, check OBS’s guidance for that source and consider the display or window capture choices documented for your platform. The source you choose depends on the operating system and how the game is displayed; do not assume one Windows workflow transfers unchanged to a Mac or Linux computer.
For console gameplay, decide whether you want to send the console’s video to the computer or use remote-play software on the computer. A compatible capture device can bring the console signal into OBS as a Video Capture Source. Where the console and game support remote play, you may instead capture the remote-play window, with the result depending on the network connection.
A capture device can be useful when you want to record the console’s direct video output on a computer, but it adds a compatibility check and another connection to troubleshoot. Before buying a USB HDMI game capture card, confirm that the exact device supports your console, computer operating system, resolution and frame rate, and intended audio route. OBS documents the general capture-device route; that is not a validation of any particular model.
Nintendo Switch owners should check the console model before planning a hardware connection. A docked Switch can be used with a compatible capture device, whereas Switch Lite cannot be docked and does not use that dock-and-capture route. If remote play or another supported method is available for your console, check its requirements rather than treating a capture card as universal.
| Capture path | What you need | Main trade-off |
|---|---|---|
| Windows PC game with OBS Game Capture | OBS and the computer running the game | Direct route, but a particular game or setup may need a different capture source |
| Console through a capture device | Compatible console, device and computer connections | Brings console video into OBS, but compatibility and audio routing need checking |
| Console remote-play window | A supported remote-play app and a suitable network | Avoids a capture device, but picture and sound depend on the remote-play connection |
If you are still deciding what belongs in a broader recording setup, the equipment and software setup guide gives context on how capture equipment fits alongside software and other gear. Treat it as a planning aid, not a replacement for checking the requirements of your actual game and device.
Capture PC gameplay with OBS
Install OBS Studio from the OBS Project, open it and run the Auto-Configuration Wizard. It can help select an initial setup based on how you intend to use OBS and the computer available. The result is a starting point, not a guarantee that a demanding game and recording will run smoothly together.
Create a scene for the walkthrough and add the game as a source. On Windows, try Game Capture for a compatible DirectX or OpenGL game and check that the preview shows the correct window. If it does not, consult the OBS Game Capture FAQ for troubleshooting; depending on your platform and the game, a documented window or display capture source may be more suitable. Avoid capturing your desktop when you only need the game, especially if private notifications or other windows could appear in the footage.
Before a full recording, set the destination folder and check the available storage. OBS’s recording choices balance picture quality, computer performance and file size. Hardware encoders may be available on some computers, but there is no single quality preset that fits all hardware. Start with the wizard’s suggestion or an available preset, test it with your game running, and adjust if you see stutter or the file is unexpectedly large.
Keep the scene simple until the core picture and audio work. If you want a webcam, overlays or a second information panel, add them after confirming the gameplay source. Every extra element can make the scene more complex to check, and overlays can obscure useful game details if they are placed without reviewing the preview.
OBS’s Quick Start Guide covers creating a scene and adding sources. The interface may change over time, so use the source names and instructions shown in the current OBS version. If a game behaves differently from the guide, troubleshoot that specific combination rather than assuming the recording itself is broken.
Connect console gameplay to a computer
For a capture-device setup, connect the console’s video output to the device’s input, then connect the device to the computer according to its instructions. If you also want to play on a television or monitor while recording, check whether the device supports a suitable passthrough connection. Passthrough is a convenience to verify before purchase, not a requirement for capturing video.
In OBS, add a Video Capture Source and select the connected device. Check the preview before starting the game session: confirm that the picture is present, fills the intended frame, and updates as the game changes. Device names and available controls can differ, so consult the manufacturer’s documentation for its specific connection and configuration. Do not infer support for a certain resolution or frame rate from the fact that OBS recognises the device.
Audio deserves a separate check. Some setups route console audio with the video; others may need a different connection or device setting. Listen to a short recording to establish what is actually included. A picture in the OBS preview alone does not confirm that game sound reaches the recording.
Where your console and game support remote play to a computer, you can capture the remote-play app with a suitable OBS window source. This can avoid adding a capture device, but the connection can affect responsiveness and picture quality. If the remote-play feed drops or stutters, check the network and the app before changing recording settings. A guide to SDI signals explains a different video-connection standard; it is relevant when planning professional video connections, but it does not establish compatibility for a consumer console capture setup.
Set up game and microphone audio
Open the OBS Audio Mixer while the game is running and speaking into your microphone. The game or desktop audio meter should respond to game sound, and the microphone meter should move when you speak. If a meter stays still, select the intended input in OBS’s audio settings and test again. Do not rely on hearing sound through your headphones: monitoring sound and recording it are separate things.
For commentary, make sure your voice is understandable over the game. You can lower the game’s own volume or adjust its level in the recording mix, then listen back to a clip. A headset microphone can be enough to start; a separate microphone is optional if your current equipment gives clear speech. Adding equipment will not fix a muted or wrongly selected input.
Watch for duplicate audio. If the same game sound is captured through both a desktop source and a capture-device source, it may sound louder or echo. Check the mixer and make one route responsible for the game audio where practical. If you hear a delay between the picture and your voice, identify whether the issue is present in the source, monitoring or recorded file before adjusting sync settings.
For a walkthrough without narration, decide whether game audio alone is enough to guide the viewer. If you explain a puzzle, route or decision, keep commentary focused and audible. The webcam background guide is useful if you plan to add a face camera, but a webcam is not needed to record gameplay and should not distract from the game.
Make a short test recording
Record a brief sample with the actual game open. Move through a scene, perform an action that uses game sound, and speak as you would during the walkthrough. OBS recommends testing before a full recording; a short clip can reveal a missing source or wrong audio input while it is still easy to fix.
Open the resulting file, not just the OBS preview. Check that it is saved in the folder you intended, plays from beginning to end, and contains the expected picture and sound. Confirm that commentary is audible, game audio is present, and the two are in sync. Look for black frames, an unwanted desktop view, stutter, clipped speech or repeated audio.
If the clip stutters, reduce the recording demands and test again. You might lower the output resolution or choose a less demanding quality option, depending on your computer and the game. Change one relevant setting at a time so you can tell whether it helped. If the capture source itself is blank, troubleshoot that source or connection before lowering quality; those are different problems.
A test also shows whether the file size and recording destination are workable for the planned session. Long recordings take more storage than short samples, and editing can require additional working space. Leave enough room for the recording and any exported version, and make a fresh test after changing the capture path, audio devices or output settings.
Review and prepare the upload
Before recording a complete walkthrough, decide how the video will help someone follow the game. Organise it around an episode, objective, mission or question being solved. Use clear explanations when a decision or transition would otherwise be difficult to understand. This is editorial guidance rather than a formal YouTube format requirement.
Edit out avoidable waits or failed attempts if they do not help the viewer, but preserve context where it matters. If you cut ahead, make the change clear through narration, a caption or a chapter boundary. Add chapter markers when they help viewers return to a boss, puzzle or location. Avoid promising that an edit, title or upload setting will increase recommendations; prepare the video for the person who intends to watch it.
Gameplay footage should have a clear original contribution where appropriate, such as commentary, explanation, or substantive editing that adds educational or entertainment value. YouTube’s reused-content policy describes how it evaluates reused material at channel level. That policy is distinct from copyright: adding commentary does not by itself establish that you have rights to use every game, soundtrack or other included material. Check the relevant permissions and current official guidance for your situation.
For export, YouTube’s encoding recommendations list MP4, H.264 video and AAC-LC or Opus audio, and recommend matching the frame rate used for recording. The guidance also gives recommended upload bitrates by resolution and frame rate. For example, it lists 8 Mbps for 1080p SDR at standard frame rates and 12 Mbps at high frame rates. These are upload recommendations, not OBS recording bitrate settings; do not copy an upload figure into OBS without understanding what that setting controls. Confirm YouTube’s current table before exporting because its guidance can change.
Upload the finished file through YouTube Studio, add a specific title and description, select the audience setting, and review the available checks. Uploading transfers the file; it does not make the video public by itself. Choose private or unlisted if you want to inspect the uploaded version before publication, then select the visibility you intend. A final playback check can catch issues that were not obvious in the local export.
A saved recording can also be useful as source material for a separate channel format, but gameplay capture is not the same as making a continuous live channel. If you later need to keep a prepared video running as a live broadcast while your computer is off, StreamNeo addresses that separate hand-off by taking an uploaded video and running it as a YouTube live stream, rather than asking you to leave the recording computer on.
If you want to add live video connections or longer-running channel work to your setup later, the guide to keeping a 24/7 radio stream alive through OBS updates covers a different operational problem from recording a walkthrough. Keep the two workflows distinct: record and review the gameplay file here, then plan any live broadcast separately.
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
How do I record gameplay for YouTube?
Choose a capture route based on whether the game runs on a Windows PC or a console. Set up the matching source in OBS, check game and microphone audio, make and review a test recording, then export and upload the finished video through YouTube Studio.
Do I need a capture card to record console gameplay?
Not always. A compatible capture device is one way to bring console video into a computer, while supported remote-play software may let you capture a window instead. Check the console, game, operating system and connection requirements before choosing a route.
How do I record game audio and my microphone in OBS?
Check the Audio Mixer while game sound is playing and while you speak, and confirm that both meters respond. If either one does not, select the intended input, record a short sample and listen back to verify levels, clarity and sync.
Can I use the same OBS capture source on every computer and game?
No. OBS documents different source choices by platform and capture method, and Game Capture is not a universal solution for every game or operating system. Use the guidance for your setup, check the preview and test the resulting file before recording a full walkthrough.