✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.
⭐ Key Takeaways
Quick answer: Our top pick is MSI GeForce GTX 1660 Super Ventus XS OC, with MSI GeForce RTX 3060 Ventus 2X 12G OC as a strong alternative.

NVK is the open-source Vulkan driver for NVIDIA graphics cards inside Mesa, the same graphics library that carries AMD’s RADV and Intel’s ANV drivers. Developed in the open, mainly by engineers at Collabora, Red Hat and NVIDIA itself, it raises an obvious question for anyone gaming on Linux with a GeForce card: can the driver that runs your games one day be the one that ships with your system, with no proprietary download at all?

The short answer is that NVK has crossed the line from experiment to shipping driver, but not yet the line from shipping driver to default recommendation. Mesa documents it as a conformant Vulkan 1.4 implementation on its supported hardware, distributions build it into Mesa, and OpenGL on newer NVIDIA cards already runs on top of it by default. What it does not yet do is match the proprietary driver feature for feature. One boundary: a companion article in this series covers NVIDIA’s kernel modules, the open-versus-proprietary choice on the kernel side. This article covers only the layer above that, the userspace Vulkan driver in Mesa.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

NVK is Mesa’s open-source Vulkan driver for NVIDIA GPUs, and it is a conformant Vulkan 1.4 driver on Turing and newer cards, from the GTX 16 series through the RTX 50 series. It is ready to try for everyday and older gaming, but the proprietary driver remains the safer choice for new releases, ray tracing and DLSS.

The stack in one view

An NVIDIA game on the open stack passes through four layers, and NVK is only one of them. At the bottom sits a kernel driver, today the Nouveau DRM driver, which talks to the hardware. Mesa’s documentation sets the floor for NVK at a Linux 6.6 kernel, a requirement any current distribution clears easily.

Above the kernel sits the firmware. On Turing and newer cards, the kernel driver loads NVIDIA’s GSP firmware, which runs on a small processor built into the GPU itself. The GSP, short for GPU System Processor, handles jobs such as power management and clock control that used to require the proprietary driver. That divide explains the support map: generations with a usable GSP path can be driven by open code, and generations without one cannot.

NVK itself is the third layer, the userspace Vulkan driver inside Mesa. Games, DXVK and VKD3D-Proton talk to NVK, which translates their Vulkan calls into GPU commands with its own shader compiler, NAK, written in Rust. NVK implements Vulkan only, so OpenGL games reach the hardware through a fourth layer, Zink, a Mesa driver that turns OpenGL calls into Vulkan ones. Since Mesa 25.1, that NVK plus Zink pairing is the default OpenGL implementation on Turing and newer cards, and Mesa counts it as conformant OpenGL 4.6.

One more name belongs in this picture. Nova is a new kernel driver being written in Rust, developed upstream by Red Hat engineers with NVIDIA participation, aimed in the long term at succeeding Nouveau for GSP-based GPUs. Its core code landed as a skeleton and is not usable yet, but it shows where the kernel layer under NVK is heading.

Which GPUs are actually supported

Mesa’s documentation draws the support line at Turing. The officially supported generations are Turing (the RTX 20 series and the GTX 16 series), Ampere (RTX 30), Ada (RTX 40) and consumer Blackwell (RTX 50). On those GPUs NVK is a conformant Vulkan 1.4 implementation, a status first reached at the 1.3 level in Mesa 24.1, when distributions were told to start shipping it.

Older hardware exists in a greyer zone. The code can recognise Kepler, Maxwell and Volta cards (GeForce 600 through GTX 10), but those GPUs are not enumerated by default. Turning them on requires an environment variable Mesa documents as a developer-only tool for hardware whose support is, in its own framing, poorly tested or completely broken. Without a firmware path for clock and power control, an open driver cannot run those cards at their proper speeds. If your card is a GTX 10 series or older, NVK is not your driver today.

Feature posture: what is in, what is flagged, what is missing

Start with the core. Vulkan conformance is the headline, and it is the right one: a conformant driver has passed the Khronos test suite, so games that speak standard Vulkan get correct behaviour, not an approximation. Around that core, Mesa keeps filling in the pieces games ask for. Mesh shading is supported, DXVK runs on upstream Mesa, and completing the D3D12 path through VKD3D-Proton is a stated project focus. The NAK compiler improves release by release, including tuning for older supported cards such as Turing.

Two features sit behind an experimental switch in Mesa’s own documentation. DLSS on NVK exists only as an experimental option a user must explicitly enable, and only where precompiled support for the GPU is found in the DLSS library; video acceleration through Vulkan Video is likewise an experimental enable, with the first hardware decode support only recently arriving, limited to newer generations. Neither is part of the default, supported surface.

Ray tracing is the thinnest part of the story. The conformance claims Mesa publishes for NVK are claims about core Vulkan, and ray-traced gaming remains where the proprietary driver is most clearly ahead, as the path NVIDIA tunes per title. Treat ray tracing on NVK as emerging work, not a reason to switch.

Two absences round out the picture. CUDA does not exist on the open stack at all; anything needing NVIDIA’s compute platform, from creative tools to local AI workloads, needs the proprietary driver, whose control panel and per-game profiles have no open equivalent. What NVK offers instead is integration: it updates with your system, the same on every distribution shipping a current Mesa.

NVK versus the proprietary driver, by use case

For a desktop that also games, NVK’s case is strongest. It is simply there after installation, updates arrive with Mesa, and Vulkan plus Zink covers the APIs desktop software and older games use. Players with older libraries are the most likely to try NVK and simply stay.

For day-one gaming, the proprietary driver still wins on process rather than on any single feature. NVIDIA validates new releases against its own driver, publishes game-ready updates, and owns the DLSS and ray tracing paths those releases advertise. NVK improves in public, on Mesa’s release cadence, and a game that hits an NVK bug waits for a Mesa fix rather than a vendor hotfix. The same caution applies to laptops, where power management and hybrid GPU switching are the youngest parts of the open stack, and anyone who needs CUDA has no choice at all.

How to choose

Choose by generation first. If your card is Turing or newer, NVK is a legitimate option on any current distribution, and switching back costs little. If your card is older than Turing, stay where you are; the open Vulkan driver does not meaningfully support your hardware.

Choose by library second. A backlog of older and mid-weight games is NVK-friendly territory. A habit of buying demanding releases at launch, turning on ray tracing, or relying on DLSS points back to the proprietary driver: those are the features Mesa keeps behind experimental flags or leaves to NVIDIA.

Choose by temperament third. NVK rewards players who like an open, uniform system and can wait a release cycle for a bug fix. It punishes players who want a new game working on launch evening.

Who should skip this

Skip NVK for now if you own a Pascal or older card, since your hardware is outside the supported set. Skip it if CUDA, DLSS or ray tracing is part of your weekly routine, or if a driver bug in a new-release title would cost you an evening. Skip it, finally, on an old Mesa: NVK moves fast enough that a stale package undersells it.

Cards that sit inside NVK’s supported range

Every card below is Turing or newer, inside NVK’s conformant, officially supported set, from budget tier to high end.

MSI GeForce GTX 1660 Super Ventus XS OC

MSI GeForce GTX 1660 Super Ventus XS OC

MSI GeForce GTX 1660 Super Ventus XS OC

Check price on Amazon

The entry point to the supported map, and a clean test of NVK’s core Vulkan and Zink story at 1080p.

  • GPU architecture: Turing
  • Memory: 6GB GDDR6, 192-bit
  • Interface: PCIe 3.0
  • NVK status: officially supported generation

MSI GeForce RTX 3060 Ventus 2X 12G OC

MSI GeForce RTX 3060 Ventus 2X 12G OC

MSI GeForce RTX 3060 Ventus 2X 12G OC

Check price on Amazon

Ampere is where NVK’s conformance story became solid; a sensible mid-range home for a Proton library.

  • GPU architecture: Ampere
  • Memory: 12GB GDDR6, 192-bit
  • Memory speed: 15 Gbps
  • Interface: PCIe 4.0
  • NVK status: officially supported generation

ASUS ROG Strix GeForce RTX 4060 OC Edition

ASUS ROG Strix GeForce RTX 4060 OC Edition

ASUS ROG Strix GeForce RTX 4060 OC Edition

Check price on Amazon

An Ada card from the generation where NVK plus Zink became Mesa’s default OpenGL path.

  • GPU architecture: Ada Lovelace
  • Memory: 8GB GDDR6
  • Interface: PCIe 4.0
  • Outputs: HDMI 2.1a, DisplayPort 1.4a
  • NVK status: officially supported generation

ASUS Prime GeForce RTX 5060 Ti 16GB

Blackwell at the mainstream tier, with memory headroom for growing texture budgets in a compact design.

  • GPU architecture: Blackwell
  • Memory: 16GB GDDR7
  • Model: PRIME-RTX5060TI-16G
  • Interface: PCIe 5.0
  • NVK status: officially supported generation

ASUS Prime GeForce RTX 5070 Ti 16GB

The high-end Blackwell option here, for 1440p and 4K players.

  • GPU architecture: Blackwell
  • Memory: 16GB GDDR7
  • Model: PRIME-RTX5070TI-16G
  • Interface: PCIe 5.0
  • NVK status: officially supported generation

FAQ

Is NVK installed by default on Linux distributions?

On distributions shipping a current Mesa, NVK is built as part of Mesa for supported NVIDIA cards, and since Mesa 25.1 the NVK plus Zink combination is the default OpenGL path on Turing and newer hardware. A machine with the proprietary driver installed will normally keep using it for Vulkan until you change the setup.

Can NVK run my Steam library through Proton?

That is the use case it is built for. Vulkan games talk to NVK directly, DirectX 11 games reach it through DXVK, and DirectX 12 games through VKD3D-Proton, which the project has been actively completing. Expect the strongest results in established titles and the roughest edges in brand-new releases.

Does NVK support DLSS or ray tracing?

Only in limited form. Mesa’s documentation places DLSS behind an experimental enable that depends on precompiled support in the DLSS library, so it is not a default feature, and ray tracing remains the proprietary driver’s strongest ground. If either is central to how you play, the proprietary driver remains the recommendation.

What kernel and Mesa versions does NVK need?

The documented floor is a Linux 6.6 kernel, and the practical requirement is a recent Mesa, because NVK changes quickly between releases. A rolling or current-release distribution gives the fairest picture; an old long-term-support package shows where NVK was, not where it is.

Final verdict

NVK is the real thing: a conformant Vulkan 1.4 driver for NVIDIA hardware, written in the open, shipping in Mesa, and already carrying the OpenGL load on Turing and newer cards. Its boundaries are equally real, and Mesa draws them honestly: Turing is the floor, DLSS and video sit behind experimental flags, CUDA is absent, and ray tracing and day-one support still belong to the proprietary driver. Try NVK if your card is supported and your library is established; stay proprietary if your gaming depends on the features NVIDIA keeps for itself.

ASUS Prime GeForce RTX 5060 Ti 16GB (PRIME-RTX5060TI-16G)

ASUS Prime GeForce RTX 5060 Ti 16GB (PRIME-RTX5060TI-16G)

Check price on Amazon

ASUS Prime GeForce RTX 5070 Ti 16GB (PRIME-RTX5070TI-16G)

ASUS Prime GeForce RTX 5070 Ti 16GB (PRIME-RTX5070TI-16G)

Check price on Amazon

Explore Our Guides & Free Tools