Why OBS Has No AMD H.264 and HEVC: Diagnosing AMF and the Graphics Card

Why AMD H.264 and HEVC Are Missing in OBS

OBS gets AMD hardware encoders through AMF — a component of the Radeon driver. The program doesn't add H.264 or HEVC based on the graphics card's name: it needs a working driver, access to a suitable graphics adapter, and encoding support in the GPU's media block.

If AMF doesn't load, OBS is running in an unsuitable graphics environment, or the Radeon itself can't encode the selected format, AMD H.264 and HEVC won't appear in the list. Instead, you'll usually be left with x264, another graphics card's encoder, or basic recording options.

Having a Radeon in Device Manager doesn't mean OBS has gained access to its hardware encoder.

Where to Look for AMD Encoders in OBS Settings

Open "Settings" — "Output". The encoder for live streaming is on the "Stream" tab, and for a local file it's on the "Recording" tab. Depending on the OBS and driver version, the options may be called AMD H.264, AMD AVC, AMD HEVC, H.265, AMD AMF, or AMD HW.

Don't compare the encoder list against a random screenshot from the internet. OBS, Windows, and the Radeon driver change the layout and names of the items. Look for the words AMD, AMF, AVC, H.264, HEVC, or H.265.

Simple and Advanced Output Modes

In the "Output" section, check the "Output Mode" item. In Simple mode the interface is deliberately simplified: some parameters and encoding options may not be displayed. To check, switch to Advanced, then open "Stream" and "Recording" separately.

Expand the "Encoder" list and see whether AMD H.264 and AMD HEVC options are present. At this stage, don't change the bitrate, profile, preset, or resolution: first you need to determine whether the program has detected the hardware encoder.

The downside of Advanced mode is that it's easy to accidentally save unsuitable streaming, recording, or audio settings here. After checking, don't leave changes you're not sure about.

Why H.264 May Be Present but HEVC Missing

Hardware encoding on Radeon is handled by a separate media block. In older AMD generations it's usually associated with VCE, and in newer ones with VCN. The card's gaming performance, amount of video memory, and membership in the Radeon lineup don't by themselves confirm support for a specific codec.

Some older GPUs can encode H.264 but don't support hardware creation of HEVC video. Another situation is also possible: the card plays H.265 files but can't encode them. HEVC decode support and HEVC encode support are different features.

Check the specifications of the exact graphics card model for video encode, hardware encoding, VCE, or VCN. Look specifically for HEVC encoding support, not decoding. If there's no hardware HEVC encode, the driver and OBS settings won't add it.

Check the Radeon in Windows Device Manager

Open Windows "Device Manager" and expand the "Display adapters" section. A specific Radeon or AMD integrated graphics should be listed there. An entry of "Microsoft Basic Display Adapter" means the full driver isn't installed, is corrupted, or didn't start.

Open the graphics card's properties and check the device status. A disabled adapter, a startup error, or an error code must be resolved before working with OBS. Windows can output an image to the screen with a limited driver, but AMF is often unavailable in such a configuration.

If the system has multiple graphics cards, note their exact names. This will be needed when checking which GPU OBS is running on and which adapter is listed in the program's log.

Multiple GPUs and Hybrid Graphics

On laptops and some desktop PCs, OBS may not run on the Radeon you intend to use. For example, the system may simultaneously have the processor's integrated graphics, a discrete Radeon, and a graphics card from another manufacturer. OBS may render the scene on one GPU, while encoder availability depends on the driver and configuration of all adapters.

The problem is especially common on laptops with hybrid graphics. The discrete card is working and visible in Windows, but the application gets a graphics context from the integrated adapter. As a result, the required AMF encoder may not be detected or may work unstably.

How to Assign the Radeon to OBS in Windows Settings

Open Windows "Settings" — "System" — "Display" — "Graphics". Find OBS in the list of apps. If the program isn't there, add a classic app manually and specify the obs64.exe file from the OBS Studio installation folder.

Usually the executable is inside the bin folder, then 64bit. If OBS is installed elsewhere, open its shortcut's properties and look at the path in the target field.

1. Select OBS in the list of graphics apps.
2. Open the "Options" item.
3. Select high performance mode.
4. If Windows shows multiple adapters, specify the discrete Radeon.
5. Save the change.
6. Completely close OBS, including the process in the notification area if it's still there.
7. Launch the program again and check the encoders in Advanced mode.

The downside of assigning the discrete GPU is that the laptop may heat up more, get louder, and drain the battery faster. On some models, the graphics card choice is limited by the display connection scheme and the manufacturer's driver, so setting high performance doesn't always change OBS's actual adapter.

How to Find Out Which GPU OBS Is Using

Open Windows Task Manager, go to the "Details" tab, and enable the GPU engine column. Find the obs64.exe process. Match the GPU number from this column with the adapter names on the "Performance" tab.

The check is useful but not absolute. It shows the process's current activity but doesn't guarantee that AMF is available to start encoding. OBS may use one adapter to render the scene, while the hardware encoder's operation depends on the driver, AMF version, and hybrid graphics mode.

Check the OBS Log After a Fresh Launch

In OBS, open "Help" — "Log Files". You can view the current or last log, as well as open the logs folder. For diagnostics you need a fresh file: completely close OBS, launch it again, open the output settings, and only then look at the log.

An old log may relate to a different driver version, another profile, a connection via Remote Desktop, or a GPU configuration before Windows settings were changed. When searching the log, use the words AMF, AMD, H264, AVC, HEVC, H265, encoder, adapter, failed, error, and unsupported.

What AMF Mentions in the Log Mean

The exact text of the lines depends on the OBS, Windows, and Radeon driver version. In a working configuration, the log usually contains mentions of available AMD encoders or AMF components. What matters isn't a single fragment of text but the whole chain of messages about adapter and encoder initialization.

• There's a mention of AMF and H.264 or AVC — OBS has detected an available AMD H.264 encoder.
• There's a mention of AMF and HEVC or H.265 — the driver reports the possibility of hardware HEVC encoding.
• AMF is found, but there's an encoder creation error nearby — the encoder is detected but won't start due to the driver, software conflicts, or GPU load.
• "unsupported" is indicated next to the required codec — the active adapter may not support this encoding option.
• The log lists an unexpected integrated GPU — check the graphics settings for obs64.exe.
• There are no AMF mentions — check the Radeon driver, the active graphics card model, the OBS version, and how the system was started.

When an AMD Driver Update or Reinstall Is Required

If the Radeon is correctly displayed in Device Manager, OBS is assigned to the right GPU, but AMF doesn't appear in the log, the cause may be the driver. Problems occur after replacing the graphics card, updating Windows, installing drivers over old versions, or switching between different graphics adapters.

First download the driver suitable for your Radeon model and Windows version. Save important monitor settings, color profiles, and AMD panel settings: they may reset after cleaning.

1. Close OBS, games, editors, capture programs, and apps with overlays.
2. Uninstall the current driver using Windows or AMD's standard tools.
3. If a normal uninstall didn't help, use a driver cleanup tool strictly according to its developer's instructions.
4. Restart the computer.
5. Install the previously downloaded Radeon driver.
6. After the next restart, check the graphics card in Device Manager.
7. Open OBS, check the encoder list and the new log.

The downside of a clean reinstall is that resolution, display arrangement, refresh rate, and color settings may temporarily change. It also won't add HEVC to a card that doesn't have hardware H.265 encoding.

OBS Version, Plugins, and a Corrupted Profile

An old OBS version sometimes works worse with a new driver than the current stable release. Update OBS, then create a test profile and scene collection without third-party plugins. This makes it easier to separate an encoder problem from corrupted settings, filters, or add-ons.

If AMD H.264 or HEVC disappeared right after an OBS, driver, or Windows update, save a fresh log and the component versions. To check, you can temporarily use the previous working driver or OBS version from the official archive.

The downside of rolling back is that an old version may lack compatibility, security, and new plugin support fixes. Don't leave an old driver as a permanent solution if it causes problems in games or other programs.

Why HEVC Is Available for Recording but Not for Streaming

If AMD HEVC is visible on the "Recording" tab, the Radeon can create H.265 video in hardware. This doesn't yet mean the platform will accept such a stream. For streaming, HEVC must be supported simultaneously on the service side, by the selected protocol, channel type, and ingest parameters.

Many common broadcasting scenarios are oriented toward H.264/AVC. A platform may accept the stream key but reject the HEVC stream, fail to show the broadcast to viewers, or process it with errors. Conditions may also differ for regular broadcasts, test programs, and alternative protocols.

For broadcasting, choose HEVC only with direct confirmation of H.265 support from the specific platform. In other cases, AMD H.264 is usually safer in terms of compatibility. The downside of H.264 is that at comparable quality it usually requires more bitrate than HEVC.

Remote Desktop, Virtual Machines, and Cloud PCs

When connecting via Remote Desktop, Windows may create a virtual graphics adapter or limit the program's access to the GPU's hardware features. In such a session, OBS sometimes doesn't show AMF, even though AMD H.264 and HEVC are available when logging in locally on the same computer.

A similar problem is possible in a virtual machine and on a cloud PC: having a Radeon on the physical host doesn't mean the guest system has gained access to its video encoder. Check the encoder list when launching OBS locally with a monitor connected, if possible.

The downside of such a check is that it's inconvenient for a remote streaming computer. But it helps separate a driver malfunction from a remote session limitation.

If the AMD Encoder Is Present but Recording or Streaming Won't Start

The appearance of AMD H.264 or HEVC in the list means the detection problem is solved. Next you need to find the cause of the startup failure. Close programs that may be occupying the hardware encoder: screen recording apps, video editors, browsers with video calls, remote access programs, overlays, and instant replay utilities.

After restarting OBS, make a short local recording with a simple scene. If it's created normally, add sources one at a time: game capture, camera, browser widgets, filters, plugins. Separately check operation during a game, because a conflict or overload sometimes only manifests under high GPU load.

The downside of this method is that diagnostics take time, and a simple test scene doesn't always replicate the load of a real broadcast. But it lets you find the source after which the encoder stops starting.

What to Use Instead of Missing AMD HEVC

If the Radeon supports AMD H.264 but can't do hardware HEVC, use H.264/AVC for streaming. It's usually better compatible with streaming platforms, viewers' devices, and viewing programs. For local recording, H.264 is also suitable when the file needs to be quickly passed to editing or opened on another device.

Another option is software x264. It doesn't depend on AMD AMF and can work when the hardware encoder is unavailable. The downside of x264 is that encoding is shifted to the processor. During a game, screen capture, browser sources, and filters, this can cause CPU overload, encoder frame drops, or a drop in game performance.

Checklist If AMD H.264 and HEVC Are Still Missing

1. Confirm the exact Radeon model and its H.264 encode or HEVC encode support.
2. Check that Device Manager has no Microsoft Basic Adapter, disabled GPU, or startup errors.
3. Switch OBS to Advanced mode and check the encoders separately for streaming and recording.
4. Assign obs64.exe to the discrete Radeon in Windows graphics settings if the system has multiple GPUs.
5. Restart OBS and open a fresh log.
6. Look in the log for AMF, AMD, encoder, adapter, failed, error, and unsupported.
7. Update or reinstall the Radeon driver if AMF isn't detected.
8. Check OBS in a new profile without third-party plugins.
9. Launch OBS locally if the problem appeared via Remote Desktop, a virtual machine, or a cloud PC.
10. If HEVC is needed for streaming, separately confirm that the selected streaming platform accepts it.