Blender Cycles Not Detecting Your RTX 5090? Version and Driver Requirements Explained

If you’ve just installed Nvidia’s flagship GPU only to find that Blender’s Cycles renderer isn’t detecting your RTX 5090, you’re not alone. This issue usually stems from a compatibility gap between older Blender releases and the modern Blackwell architecture, as Cycles requires specific CUDA toolkits and minimum driver versions to recognize next-gen hardware. 

In this guide, we’ll walk you through the exact Blender version requirements, necessary Nvidia driver updates, and step-by-step fixes to get your RTX 5090 recognized and rendering at full power.

Image Source: Chaos

Cycles has supported the GeForce RTX 50-series only since Blender 4.4. If you are running 4.3 or anything older, Cycles has no GPU code compiled for your card, so it either lists nothing or refuses to use the device.

This is a software version problem, not a dead card. Check your build in Blender under Help > About Blender, or read the version in the corner of the splash screen. If that number is below 4.4, you have found your answer and the fix is an upgrade.

Blender 4.4, released on March 18, 2025, is the first version that supports the NVIDIA GeForce RTX 50×0 series in Cycles. The official release notes for 4.4 list Blackwell support under GPU rendering.

Cycles ships precompiled CUDA binaries for each GPU architecture it supports. Blackwell cards such as the RTX 5090 use the sm_120 architecture, and pull request 134170 added sm_120 to the default set of Cycles CUDA binaries for the 4.4 release, built with CUDA toolkit 12.8 or higher. A Blender 4.3 build never had that binary in the package. When Cycles finds no code it can run on the installed device, the device stops being an option.

You should install 4.4 or later. If you are moving an older project across, open it on the new version and check it before you start a long render.

Blackwell card also needs a recent NVIDIA driver. If Blender 4.4 or newer still does not list the card, the driver is the next place to look.

Download the current driver from NVIDIA’s official site rather than letting Windows Update pick one, and prefer the Studio for creative work, since it is validated against content creation applications and updated on a slower, steadier cadence than the Game Ready.

To confirm the driver sees the card at all, open a command prompt and run nvidia-smi. If the RTX 5090 appears there with a driver version listed, the operating system layer is fine and the problem sits above it, inside Blender. If the card does not appear even in nvidia-smi, stop looking at Blender and fix the driver installation first.

In Preferences, the device has to be ticked. Go to Edit > Preferences > System > Cycles Render Devices. Appearing in the list is not the same as being enabled. There is a checkbox next to the card, and Cycles ignores an unticked device completely.

In Render Properties, Device has to be GPU Compute. This is in the Render tab of the Properties editor, and it defaults to CPU. A ticked card in Preferences and a Device set to CPU produces a render that runs perfectly and never touches the GPU.

One more thing to look at while you are in Preferences. The Cycles Render Devices panel has separate tabs for the backends, CUDA and OptiX among them, and each tab keeps its own device list and its own tick state. Enabling your card on the CUDA tab does nothing for a render that is using OptiX. If a card looks enabled in one place and missing in another, you are most likely looking at two different tabs. 

Do this before you commit a sequence, because a silent CPU render until the frame times arrive.

Render a single test frame and watch two things. The frame time should drop sharply compared with a CPU render of the same frame. And GPU utilisation should climb while the render runs, which you can see in the Performance tab of Windows Task Manager or by running nvidia-smi during the render.

On a machine you rent by the hour, discovering that on frame 200 means paying for every frame that ran on the wrong device.

You are on Blender 4.4 or newer, the driver is current, both settings are correct, and the card is still missing. Two things are left to try.

Reinstall the driver cleanly. Choose the custom installation option in the NVIDIA installer and tick Perform a clean installation, which clears settings left behind by previous drivers. Leftovers from an upgrade path are a common cause of a card that behaves strangely only after a driver update.

Try a different Blender build. Install a fresh copy of the current stable release in a separate folder, with a clean user preferences profile if you can, and open it without your add-ons loaded. If the card appears there, something in your existing installation or your add-on set is the cause.

AI denoising and generative add-ons that run outside Blender’s own render pipeline need their own Blackwell-capable versions of whatever framework they use. An add-on that throws GPU errors on a Blackwell card is reporting its own problem, and it says nothing about whether Cycles can see your card. 

Put your next Cycles project on a dedicated NVIDIA RTX 5090 32GB GDDR7 machine at iRender, with 21,760 CUDA cores per card, full administrator rights, and your own Blender and Cycles render farm build installed by you. 

Register today to claim a 100% Bonus on your first recharge within 24 hours of registration.

• Package 3i (1x RTX 5090): AMD Ryzen Threadripper PRO 5975WX, 256GB RAM, 2TB NVMe
• Package 4i (2x RTX 5090): AMD Ryzen Threadripper PRO 5975WX, 256GB RAM, 2TB NVMe
• Package 5i (4x RTX 5090): AMD Ryzen Threadripper PRO 5975WX, 256GB RAM, 2TB NVMe
• Package 9i (8x RTX 5090): AMD Ryzen Threadripper PRO 5975WX, 256GB RAM, 2TB NVMe

Let’s watch the tutorial video to see how our service works:  

Q1: Which Blender version supports the RTX 5090?

Blender 4.4, released on March 18, 2025, is the first version that supports the GeForce RTX 50×0 series in Cycles, and the official release notes list Blackwell support under GPU rendering. If you are running 4.3 or older, upgrade before investigating anything else.

Q2: Why does my RTX 5090 not appear in Blender preferences?

The most frequent cause is a Blender version older than 4.4, which predates Blackwell support in Cycles. The next is a driver too old for the card. After those two, look at which tab you are reading in the Cycles Render Devices panel, since CUDA and OptiX are separate backends with separate device lists, and a card enabled on one is not enabled on the other.

Q3: Blender sees my RTX 5090 but rendering is still slow. Why?

The card is probably listed without being switched on. Ticking it in Edit > Preferences > System > Cycles Render Devices is one step, and setting Device to GPU Compute in Render Properties is a second, separate one. If either is missed, the render completes normally on the CPU with no error to warn you. 

Maximum Speed – Absolute Freedom