Discord offers hardware video encoding using your GPU to stream and share your screen with lower CPU usage and higher quality. On some driver versions, Discord automatically switches from hardware encoding to software encoding, which increases CPU load and can cause lag. This problem occurs because the GPU driver is either outdated, corrupted, or incompatible with Discord’s encoding API. This article explains why hardware encoding drops to software on certain drivers and how to fix it.
Key Takeaways: How to Keep Discord Hardware Encoding Active
- User Settings > Voice & Video > H.264 Hardware Encoding: Toggle this setting off and on to force Discord to renegotiate with the GPU driver.
- NVIDIA GeForce Experience or AMD Adrenalin driver clean install: Use DDU to remove old drivers fully before installing the latest stable driver.
- Discord Canary or PTB build: Test with a different Discord client version to bypass driver-specific API bugs.
Why Discord Falls Back to Software Encoding
Discord uses the H.264 video codec for hardware encoding. When you share your screen or stream, Discord asks your GPU to encode the video in real time. The GPU driver provides a set of functions called the Video Acceleration API (VAAPI on Linux, NVENC on NVIDIA, VCE/AMF on AMD, and Intel Quick Sync). If the driver does not respond to these API calls correctly, Discord cannot use the GPU and falls back to software encoding using your CPU.
The most common driver-related causes are:
Driver Version Mismatch with Discord’s Encoder Library
Discord ships with a specific version of the FFmpeg library that calls the hardware encoder. If your GPU driver is newer or older than the version Discord was tested against, the API calls may fail silently. This is especially common with NVIDIA drivers released right after a major Windows update or a new Discord build.
Corrupted or Partially Installed Drivers
A driver update that fails midway, or an upgrade from an older driver without a clean removal, leaves behind registry entries and DLL files that conflict with the new driver. Discord then sees an incomplete driver stack and disables hardware encoding to prevent crashes.
GPU Driver Overrides from Game Optimization Software
NVIDIA GeForce Experience, AMD Adrenalin, and Intel Graphics Command Center can override global encoding settings. If these tools force software encoding for Discord specifically, or if they apply a game profile that conflicts with Discord’s encoder call, the hardware encoder will not activate.
Steps to Restore Hardware Encoding in Discord
Follow these steps in order. Test hardware encoding after each step by starting a screen share and checking the stream quality indicator.
- Toggle H.264 Hardware Encoding in Discord
Open Discord. Go to User Settings > Voice & Video. Scroll to the Video section. Find the toggle labeled H.264 Hardware Encoding. Turn it off. Restart Discord. Turn it back on. Restart Discord again. This forces Discord to reinitialize the encoder and can clear a temporary driver handshake failure. - Update Your GPU Driver Using the Manufacturer’s Tool
Open NVIDIA GeForce Experience or AMD Adrenalin. Go to the Drivers tab. Click Check for Updates. If a new driver is available, download and install it. Choose the Express or Quick Install option. Restart your PC after the install. For Intel integrated graphics, use the Intel Driver & Support Assistant. - Perform a Clean Driver Installation with DDU
Download Display Driver Uninstaller from the official Guru3D website. Boot Windows into Safe Mode. Run DDU and select your GPU manufacturer. Click Clean and Restart. After the restart, install the latest driver from the manufacturer’s website using the Custom Install option and check the box for Clean Install. This removes all leftover files from previous driver versions. - Disable Game Optimization Overlays
Open NVIDIA GeForce Experience. Click the Settings gear icon. Under General, turn off In-Game Overlay. For AMD Adrenalin, go to Settings > General and disable In-Game Overlay. Restart Discord. These overlays can intercept the encoder API call and cause Discord to fall back to software encoding. - Test with Discord Canary or PTB
Download Discord Canary from the Discord website. Install it alongside your regular Discord. Log in and test screen sharing. If hardware encoding works in Canary, the stable build has a bug that will be fixed in a future update. Use Canary as a temporary workaround. - Roll Back the GPU Driver
If the problem started after a driver update, roll back to the previous driver. Open Device Manager. Expand Display Adapters. Right-click your GPU and choose Properties. Go to the Driver tab. Click Roll Back Driver. Follow the prompts. Restart your PC. Test Discord.
If Discord Still Uses Software Encoding After the Main Fix
Hardware Encoding Option Is Grayed Out
If the H.264 Hardware Encoding toggle is grayed out, Discord cannot detect any compatible GPU. This usually means the GPU driver is not installed or is severely corrupted. Run DDU in Safe Mode and reinstall the driver. If you are on a laptop with dual GPUs, make sure the dedicated GPU driver is installed and that Discord is set to use the high-performance GPU in Windows Graphics Settings.
Stream Quality Shows High CPU Usage
Even if the toggle is on, Discord may still use software encoding if the GPU cannot handle the resolution or frame rate. Open Task Manager during a stream. If Discord’s CPU usage is above 20% on a modern CPU, it is using software encoding. Lower the stream resolution to 720p and frame rate to 30 fps in Discord’s Voice & Video settings. This reduces the encoding load and may allow the hardware encoder to activate.
Multiple Monitors Cause Hardware Encoder to Drop
Some GPU drivers have a bug where hardware encoding fails when you share a secondary monitor. In Discord, when you start a screen share, select the specific application window instead of a full screen. If you must share a full screen, switch to the primary monitor before starting the share.
Discord Hardware Encoding: Driver Types Compared
| Item | Game Ready Driver (NVIDIA) | Studio Driver (NVIDIA) |
|---|---|---|
| Target audience | Gamers and streamers | Content creators and professionals |
| Update frequency | Monthly or more often | Quarterly |
| Stability with Discord | May have regressions on new game-optimized builds | More stable across Discord versions |
| Recommendation | Use if you play latest games and need day-0 support | Use if hardware encoding drops frequently on Game Ready drivers |
For AMD and Intel GPUs, there is no separate Studio driver branch. Use the latest Adrenalin or Intel DCH driver from the manufacturer’s website. Avoid beta drivers unless you are testing a specific fix.
You can now force Discord to use hardware encoding by toggling the H.264 setting and cleaning your GPU driver with DDU. If the problem persists, switch to Discord Canary or use an NVIDIA Studio driver for better stability. For the best performance, always keep your GPU driver up to date and disable game overlay software that interferes with the encoder API.