Choose by the hardware you have
| Encoder | Where it runs | When to start with it |
|---|---|---|
| NVENC | dedicated block on NVIDIA GPUs | machine with a compatible NVIDIA card |
| QSV | Intel integrated video | Intel with Quick Sync exposed to the system |
| AMF | encoder on AMD GPUs | machine with a compatible AMD card |
| x264 | CPU | no hardware available, or a CPU with measured headroom |
OBS recommends a hardware encoder on modern machines because it takes work off the CPU and uses a block built for video. Older generations can deliver a worse picture at the same bitrate; test your actual card, not just the name of its family.
Multistream changes the math
Straight up copies the signal from your streaming software and doesn't open a new encoder session per platform. Smart only transcodes what doesn't fit the destination. All out can open a session for every output.
Cards and drivers set different limits on simultaneous sessions. Corneta shows the detected estimate, but it doesn't promise that your game, OBS and several transcodes will all fit together. The confirmation is a test stream with your heaviest scene.
Test order
- Pick the hardware you have.
- Run your real scene with the game's FPS capped.
- Watch rendering and encoding lag in OBS.
- Add transcodes one at a time.
- If you start dropping frames, go back to the last stable profile.
If the picture already fits all three platforms, copying instead of transcoding saves more resources than switching encoders.