OBS NVENC Encoder Missing After a Driver Update on Linux? Fixes

You update your NVIDIA driver, reboot, open OBS Studio to record or stream, and the NVENC encoder has vanished. In its place you only see software encoding, CPU usage shoots up, and recordings that were smooth yesterday now stutter. This is frustrating, but on Linux it has clear causes and a logical fix order.

Quick Answer

NVENC disappears when OBS, the NVIDIA driver, and the FFmpeg libraries no longer match after an update. Reboot after the driver update, check that nvidia-smi works in the Terminal, reinstall or update OBS from a trusted source, and confirm the driver libraries are complete. If OBS is a Flatpak, update its NVIDIA runtime so it matches your driver version exactly.

What NVENC Is and Why It Matters

NVENC is the dedicated video encoding chip inside most modern NVIDIA graphics cards. Instead of making your main processor compress video, OBS hands that job to the GPU. The result is much lower CPU use, smoother gameplay while streaming, and better recording quality at the same file size.

When NVENC is missing, OBS falls back to x264 software encoding. Your computer can still record, but it runs hotter and slower. Games may drop frames, and older CPUs may not keep up at 1080p at all.

On Linux, OBS depends on the NVIDIA kernel driver, the user-space driver libraries, and FFmpeg, which OBS uses to access the encoder. If any one piece updates without the others, or a reboot is skipped, OBS may decide NVENC is unavailable and hide it completely.

Why a Driver Update Makes NVENC Disappear

First, the new driver may be installed but not yet running. Linux cannot swap the active NVIDIA kernel module during a desktop session. Until you reboot, apps may see a broken driver.

Second, if you installed the driver manually from a .run file, a kernel update can break it. The driver was built for one kernel and does not rebuild for the next unless DKMS is set up correctly.

Third, Flatpak and Snap versions of OBS use their own runtimes. Your system driver can update perfectly while the Flatpak NVIDIA runtime stays older. When versions do not line up, NVENC fails inside the sandboxed app even though it works elsewhere. Our guide to updating NVIDIA drivers safely on Ubuntu explains how to keep driver and kernel in step.

Step 1: Reboot and Check the Driver Works

Always start here, even if you already rebooted once. A clean reboot after a driver install solves more cases than people expect.

1. Save your work, close OBS, and reboot fully. Do not just log out.
2. Open the Terminal and run nvidia-smi. You should see your GPU name, driver version, and a process table.
3. If nvidia-smi says no devices were found or cannot communicate with the driver, OBS will not see NVENC either. Fix the driver first.
4. Run uname -r to note your kernel version, useful later for compatibility checks.

If nvidia-smi fails, reinstall the recommended driver through Ubuntu’s tool. Run ubuntu-drivers devices to see what is recommended, then sudo ubuntu-drivers autoinstall and reboot again. Avoid mixing a manual install with the packaged driver, because mixing methods is a common cause of broken updates.

Step 2: Look in the Right Place in OBS Settings

Many users look in the wrong settings view and think the encoder is gone when they are simply in Simple output mode.

1. Open OBS and go to Settings, then Output.
2. Change Output Mode at the top from Simple to Advanced.
3. Open the Streaming tab and click the Video Encoder dropdown. Look for NVIDIA NVENC H.264.
4. Open the Recording tab and check the same dropdown there. OBS keeps streaming and recording encoders separate, so set both.

If NVENC is still absent, close OBS and launch it once from the Terminal with obs. Read any startup messages. Errors mentioning libnvidia-encode or failed encoder loading point directly to a driver library mismatch. The official OBS NVENC guide also explains quality settings once the encoder returns.

Step 3: Fix Flatpak OBS and Its NVIDIA Runtime

If you installed OBS from Flathub, this is the most important step. Flatpak apps need a runtime extension matching your exact driver version.

1. Run flatpak update and install every update offered, including runtimes you do not recognize.
2. Run flatpak list | grep -i nvidia to see the installed NVIDIA runtime and its version.
3. Compare it with the driver version in nvidia-smi. The main version numbers must match.
4. If they do not match, reinstall OBS from Flathub so Flatpak pulls the correct runtime, then fully close and reopen OBS.
5. Check the encoder list again in Advanced output mode.

If Flatpak keeps causing trouble after driver updates, consider switching to the official Ubuntu package or OBS PPA. System OBS uses the system driver directly, with no matching runtime in between, so many streamers make that switch once and never see this problem again.

Step 4: Reinstall OBS and FFmpeg Cleanly

When the driver works and you are not using Flatpak, the next culprit is a broken OBS or FFmpeg install after a system upgrade.

1. Check your OBS version in Help, then About. You want OBS 30 or newer on current systems.
2. If OBS came from an old PPA or manual build, remove it and reinstall from a current trusted source.
3. On Ubuntu or Debian-based systems, run sudo apt update && sudo apt install --reinstall ffmpeg obs-studio for the packaged versions.
4. Check the encode library exists with ldconfig -p | grep nvidia-encode. If nothing appears, the driver install is incomplete.

That library check is especially useful. NVENC needs libnvidia-encode.so from the driver package. Some minimal, server, or compute-only driver installs omit what desktop recording needs. Installing the full recommended desktop driver usually restores the missing library.

Step 5: Confirm Your Card Supports NVENC

Not every NVIDIA card has an encoder. Most GTX 900 series and newer cards, and all RTX cards, support NVENC for H.264. Some entry-level MX laptop GPUs and a few low-end GT models have no NVENC chip at all.

Check your exact GPU model on the official NVIDIA video encode support matrix to confirm it supports encoding, not just decoding. If your card never supported NVENC, no driver fix will add it, and you will need software encoding or a different GPU.

Also note newer features have extra requirements. AV1 encoding in OBS needs an RTX 40 series card and a recent OBS version. If you expected AV1 and only see H.264 and HEVC, check card generation and OBS version before assuming something is broken.

Common Mistakes to Avoid

• Skipping the reboot: The new driver cannot load until you restart. Testing OBS before rebooting leads to false conclusions.
• Mixing driver methods: Do not combine the NVIDIA .run installer with Ubuntu packaged drivers. Pick one method and stick with it.
• Looking only in Simple mode: Simple mode hides encoder choices. Always check in Advanced mode.
• Forgetting the Flatpak runtime: Updating the system driver without updating Flatpak runtimes is the most common cause for Flatpak OBS users.
• Using a minimal driver package: Compute or headless packages may lack the encode libraries OBS needs.
• Ignoring terminal errors: Launching OBS from the Terminal shows encoder errors the interface hides. Those messages tell you exactly what is missing.

Conclusion

When NVENC goes missing after a driver update on Linux, work in order and do not guess. Reboot, prove the driver works with nvidia-smi, check OBS in Advanced mode, fix the Flatpak runtime if you use Flatpak, and reinstall OBS and FFmpeg cleanly if needed. Confirm your card supports NVENC in the first place. In most homes the cause is a simple version mismatch between driver, runtime, and OBS, and once those three line up, NVENC returns and your CPU can relax.

Frequently Asked Questions

Why did NVENC work yesterday and disappear after an update?

An update changed one part of the chain: the kernel, driver, FFmpeg, OBS, or Flatpak runtime. Until all parts match, OBS hides the encoder. A reboot plus a package or Flatpak update fixes most cases.

How can I test if NVENC works outside OBS?

Run ffmpeg -encoders | grep nvenc. If FFmpeg lists nvenc_h264 and nvenc_hevc, the system encoder is present and the problem is likely inside OBS or its install. If nothing is listed, focus on driver and FFmpeg packages.

Is x264 good enough while I fix NVENC?

For short 720p recordings or simple desktop capture, many CPUs handle x264 on the veryfast preset. For gaming streams at 1080p, software encoding often causes dropped frames, so treat it as a temporary workaround.

My driver and Flatpak runtime versions do not match. What should I do?

Run a full flatpak update first. If the matching runtime is not offered, reinstall OBS from Flathub, or switch to the system package. Do not force an old runtime to work with a new driver.

Can a kernel update break NVENC if I did not touch the driver?

Yes. If the driver was installed manually without proper DKMS, a new kernel may boot without the NVIDIA module built for it. Reinstalling the recommended packaged driver is the most reliable way to stop this repeating.