How to Record Gameplay Properly — Software, Capture Cards and the Real Trade-offs
Most people do not need a capture card. Here's when software recording is enough, when it isn't, and the settings that stop recordings looking terrible.
The short answer
Software recording using the GPU's built-in encoder is sufficient for the large majority of PC gameplay recording, costing only a few per cent of frame rate on modern hardware. A capture card is genuinely necessary only when recording from a console or a second machine, or when running a demanding game where even a few per cent of performance loss matters. The most common cause of poor-looking recordings is an inadequate bitrate, not the recording method.
Verified and last updated August 12, 2026.
- Time needed
- 12 min
- Difficulty
- Intermediate
- Read time
- 3 min
The capture card question comes up constantly and the answer for most people is that they do not need one. Modern GPUs record gameplay with a performance cost small enough to ignore.
Where capture cards earn their place is a narrower set of situations than the marketing suggests.
When you actually need a capture card
Recording from a console. Recording from a second PC. Running a game so demanding that a few per cent matters. That is the list. For single-PC recording of a typical game, the hardware encoder in your GPU is doing the same job for free.
Software recording: the settings that matter
The important distinction from streaming: you are not limited by upload bandwidth. Streaming forces a low bitrate because it has to travel over your connection. Recording does not, so use a much higher one. This is the single biggest reason recordings look worse than they should — people copy their streaming settings.
Use CQP or CRF rather than a fixed bitrate. Constant-quality modes spend bits where the scene needs them and save them where it does not, which is exactly right for a file you are going to edit.
The drive is the hidden bottleneck
High-bitrate recording writes continuously and steadily. Two things break it:
Record to a different drive than the game 2 min
Reading game assets and writing a 50 Mbps stream to the same drive causes contention, and the recording drops frames while the game stutters. Separate them.
Keep free space on the recording drive 1 min
SSDs slow substantially when nearly full, and a long session at high bitrate produces very large files. Check you have room for the whole session before starting, not halfway through.
When a capture card is the right answer
Console recording. There is no software route. A card is the only option, and this is the main legitimate use case.
Two-PC setup. The gaming machine takes zero recording load because the second machine does all the encoding. This is genuinely better if you also stream, and genuinely unnecessary otherwise.
Preserving every frame in a demanding title. If you are recording a game that is already at the edge of playable, moving the encode entirely off the machine helps.
Internal cards avoid USB bandwidth limits and are more reliable for high resolutions and frame rates. External cards are more flexible and easier to move between machines. Neither is meaningfully better in image quality at typical settings.
What works
What doesn't
Key takeaways
Frequently asked questions
Do I need a capture card to record PC gameplay?
No, in almost all cases. Modern GPUs have dedicated hardware encoders that record with a performance cost of a few per cent, and that silicon is separate from the graphics cores doing the rendering. A capture card is needed when the source is a console or a separate machine, or when you are running a game so demanding that even a small performance cost is unacceptable. For typical PC recording it is money spent on a problem you do not have.
What bitrate should I record at?
For local recording, considerably higher than you would stream at, because you are not limited by upload bandwidth. Around 40 to 50 Mbps for 1080p60 and 70 to 100 Mbps for 1440p60 gives clean results with room for editing. Low bitrate is the single most common reason recordings look blocky in fast motion, and no amount of resolution fixes it.
Does recording hurt frame rate?
With a hardware encoder, only slightly — typically a few per cent, because the encoding runs on dedicated silicon rather than the graphics cores. With software x264 encoding it is severe, because that runs on the CPU and competes directly with the game. Always select the hardware encoder for recording gameplay; x264 is for situations where quality at very low bitrate matters more than performance.
Should I record at 60 fps or higher?
Sixty is the sensible default for most content and doubles your file sizes going higher. Record above 60 only if you intend to use slow motion, since a 120 fps source slowed to half speed stays smooth where a 60 fps source does not. For straightforward gameplay footage, higher frame rates cost storage and editing performance for no visible benefit.
Why do my recordings stutter when the game runs fine?
Usually because the recording is being written to a drive that cannot keep up, or to the same drive the game is reading from. High-bitrate recording writes a lot of data continuously and a mechanical drive or a nearly full SSD will drop frames. Record to a separate fast drive. The second common cause is a mismatch between the game's frame rate and the recording frame rate, which produces uneven cadence.
About the author
PC Hardware & Performance Editor
Marcus has been building, breaking and repairing gaming PCs since 2011, first as a weekend favour for friends and then for eight years as a bench technician at an independent repair shop in Portland, where roughly a third of the job was diagnosing machines that "ran fine yesterday".
Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.