Where to find AMD GPU settings in OBS
OBS detects your AMD graphics card automatically when you launch the program, but you need to tell it to use the GPU for encoding instead of your CPU. The settings live in the same place whether you have a Radeon RX 7000-series card, an older RX 6000-series, or an integrated Radeon GPU in your processor. Open OBS, click Settings in the bottom right, then select Output from the left menu.
In the Output tab, look for the dropdown that says Encoder. By default, OBS uses your CPU (labeled something like "x264" or "Software"). Click that dropdown and look for an option containing "AMD" or "HEVC" — you'll see choices like AMD VCE H.264 or AMD VCE HEVC. The difference between them matters: H.264 works on older streaming platforms and is more widely compatible, while HEVC produces smaller files at the same quality but requires newer hardware on the viewer's end.
If you don't see any AMD options in that dropdown, your card either isn't detected or doesn't support hardware encoding. Restart OBS first. If the options still don't appear, check that your AMD graphics drivers are fully updated — OBS can only use the encoder if the driver includes it.
Key Takeaways
- AMD GPU encoding is found in Settings > Output > Encoder, where you select either AMD VCE H.264 or AMD VCE HEVC instead of the CPU default.
- H.264 is more compatible with older platforms and viewers, while HEVC saves bandwidth but requires newer hardware to decode.
- If AMD encoder options don't appear, update your AMD graphics drivers first, then restart OBS.
- Bitrate and quality settings work the same way whether you use CPU or GPU encoding, but GPU encoding frees your processor for other tasks.
- Some AMD cards have limited encoding capabilities — older models may only support one resolution or frame rate at a time.
Choosing between H.264 and HEVC for your stream
H.264 is the safer choice for most streamers. It works on Twitch, YouTube, Facebook, and every other major platform. Older phones and computers can decode it without trouble. If your audience includes people on budget hardware or older devices, H.264 keeps your stream watchable for them. The trade-off is that H.264 files are larger — at the same visual quality, an H.264 stream uses roughly 30 percent more bandwidth than HEVC.
HEVC (also called H.265) makes sense only if you know your viewers have modern devices. It's the default on newer iPhones, recent Android phones, and computers built in the last three to four years. If you're streaming to a platform that supports HEVC and your audience is mostly on current hardware, HEVC cuts your bandwidth use noticeably. The catch: if even a few viewers have older devices, they'll see a black screen or get an error instead of your stream.
For most people starting out, pick H.264 and leave it there. You can always switch later if you find your bandwidth costs are too high or your platform specifically recommends HEVC.
Setting bitrate and quality after you pick your encoder
Once you've selected your AMD encoder, the bitrate and quality controls work the same way as they do with CPU encoding. Bitrate is the amount of data your stream sends per second, measured in kilobits per second (Kbps). Higher bitrate means better picture quality, but it also means you need faster internet to stream without dropping frames.
Start with a bitrate based on your upload speed. If your internet upload is 10 Mbps (10,000 Kbps), set your stream bitrate to 6,000 Kbps and leave 4,000 Kbps as a buffer for network hiccups. You can find your upload speed by running a speed test at speedtest.net. If you're streaming to multiple platforms at once (called multistreaming), divide your available bandwidth among them — don't send 6,000 Kbps to each platform if your total upload is only 10,000 Kbps.
The Rate Control option below the bitrate field matters more with GPU encoding than CPU encoding. Set it to CBR (constant bitrate) for live streaming — this keeps your bitrate steady, which streaming platforms prefer. VBR (variable bitrate) works for recording but can cause buffering during live streams if your bitrate spikes.
Why GPU encoding frees up your CPU for other tasks
When OBS encodes video using your CPU, it uses 20 to 40 percent of your processor's power depending on your resolution and frame rate. That's power that can't go to your game, your browser, or anything else running. If you're streaming a game at 1080p 60fps with CPU encoding, your game performance drops noticeably because OBS and your game are fighting for the same processor cores.
AMD GPU encoding moves that work to your graphics card, which has its own dedicated hardware for video encoding. Your CPU stays free to run your game at full speed. The trade-off is that GPU encoding is slightly less flexible — you can't adjust quality as finely, and some older AMD cards have limits on what resolutions and frame rates they can encode at the same time.
If you're streaming a demanding game like Baldur's Gate 3 or Cyberpunk 2077, GPU encoding often makes the difference between a smooth stream and one that stutters. Test it by opening your game, starting a stream, and watching your CPU usage in Task Manager (Windows) or Activity Monitor (Mac). If CPU usage is above 80 percent, switch to GPU encoding and watch it drop.
Checking if your AMD card supports encoding
Not every AMD graphics card has encoding hardware. Older Radeon cards and some budget models lack the encoder entirely. If you selected an AMD encoder in OBS but your stream won't start, or if OBS shows an error message, your card probably doesn't support it.
The easiest way to check is to look at your card's name. AMD cards from the RX 5000-series and newer (including RX 6000, RX 7000, and RX 8000 series) all have encoding support. Older cards like the RX 480 or RX 590 may or may not — it depends on the specific model. If you have an integrated GPU (Radeon graphics built into your processor), check your processor's name: AMD Ryzen 5000-series and newer have encoding support, while older Ryzen processors don't.
If your card doesn't support encoding, you'll need to use CPU encoding instead. Switch back to the x264 encoder in OBS Settings > Output > Encoder. Your stream will work fine, but your CPU will handle all the encoding work.
Troubleshooting when AMD encoder options don't appear
The most common reason AMD encoder options are missing is outdated drivers. AMD releases driver updates regularly, and OBS can only use the encoder if your driver includes it. Open AMD Radeon Settings (right-click your desktop and look for it, or search for it in your Start menu), click the gear icon, then select Check for Updates. If an update is available, install it and restart your computer.
After updating drivers, restart OBS completely — don't just close and reopen it, actually shut down the program and launch it again. OBS loads driver information when it starts, so a fresh launch picks up the new drivers. Go back to Settings > Output > Encoder and check if the AMD options appear now.
If they still don't show up after a driver update and restart, your card may not support encoding. Check your card's model number against AMD's list of supported hardware. You can also try uninstalling OBS completely, restarting your computer, and reinstalling the latest version of OBS from obsproject.com — sometimes a fresh install picks up drivers that an older OBS installation missed.
Comparing GPU encoding quality to CPU encoding
AMD GPU encoding produces slightly lower quality than CPU encoding at the same bitrate. The difference is visible on a large monitor or TV, but less noticeable on a phone or laptop screen. If you're streaming gameplay, most viewers won't notice — the motion and action matter more than perfect image sharpness. If you're streaming a presentation, document, or anything with small text, CPU encoding looks cleaner.
The quality gap narrows if you increase your bitrate. At 6,000 Kbps, GPU encoding looks noticeably softer than CPU encoding. At 8,000 or 9,000 Kbps, the difference becomes hard to spot. If you have the bandwidth available, bumping your bitrate up by 1,000 to 2,000 Kbps when using GPU encoding brings the quality much closer to CPU encoding.
Test both on your own stream and ask viewers which looks better to them. Many streamers find that the CPU savings are worth a small quality trade-off, especially if they're streaming demanding games. Others prefer the cleaner image and accept the CPU hit. There's no wrong choice — it depends on what matters more for your specific stream.
Frequently Asked Questions
Can I use AMD GPU encoding and CPU encoding at the same time?
No, OBS uses one encoder at a time. You pick either AMD GPU or CPU encoding in Settings > Output > Encoder. If you want to compare them, switch the setting, restart OBS, and stream again. You can't split the work between both.
Why does my stream drop frames when I use AMD GPU encoding?
Dropped frames usually mean your bitrate is too high for your internet upload speed, or your GPU is overloaded by something else. Check your upload speed at speedtest.net and make sure your bitrate is no more than 60 percent of it. If that doesn't help, lower your stream resolution from 1080p to 720p and try again.
Does AMD GPU encoding work on integrated Radeon graphics?
Yes, if your processor is Ryzen 5000-series or newer. Older Ryzen processors and Intel processors with integrated graphics don't have encoding support. Check your processor model in Settings > System > About (Windows) or Apple menu > About This Mac (Mac) to confirm.
What's the difference between VCE and HEVC in the encoder dropdown?
VCE is AMD's encoding technology. H.264 and HEVC are the two video formats it can produce. H.264 is more compatible, HEVC saves bandwidth. Both use the same AMD VCE hardware — the difference is just the output format.
Will GPU encoding make my graphics card overheat?
No, encoding hardware uses very little power and generates minimal heat. Your GPU will run warmer than when idle, but not noticeably hotter than when you're gaming. If your card is overheating, the problem is something else — check that your case fans are working and your GPU isn't clogged with dust.