✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.

Frame generation is the feature that sells new graphics cards on Windows: the GPU renders one frame, generates another to sit between rendered frames, and the displayed frame rate climbs without the game itself rendering any faster. Linux players reasonably ask how much of that survives the move to Proton and open-source drivers. The honest answer is that the map splits cleanly into three territories, and which one you land in depends on your GPU vendor and on whether the game itself offers the toggle.

This site’s upscaling coverage treats frame generation as one section of the wider DLSS and FSR picture. This article is narrower and deeper: generated frames only, vendor by vendor, covering what works today, what exists only on Windows, and what the community has built to fill the gaps. The Lossless Scaling app has its own full guide on this site, so its Linux port is covered here at status level rather than as a setup walkthrough.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

Yes, with limits. In-game frame generation works on Linux through Proton: DLSS Frame Generation on RTX 40-series cards, Multi Frame Generation on RTX 50-series, and FSR frame generation on any GPU brand. Driver-level options are thinner: NVIDIA documents Smooth Motion in its Linux driver, AMD’s Fluid Motion Frames stays Windows-only, and the community lsfg-vk layer covers everything else.

Three routes to a generated frame

Every frame generation method takes one of three routes. Engine-integrated generation lives inside the game, where it can read motion vectors, depth data and HUD information, and it produces the cleanest results. Driver-level generation is added by the graphics driver to games that never shipped support for it. External generation works from finished frames after the game has rendered them, asking nothing of the developer. On Windows, all three routes exist. On Linux, the first route is in good shape, the second is mostly missing, and the third belongs to the community.

NVIDIA: in-game generation works, and a driver route exists

NVIDIA has the deepest Linux support of the three vendors. Valve added support for NVIDIA’s Optical Flow API and DLSS Frame Generation to Proton, and current Proton builds carry that work, so an RTX 40-series card, such as the MSI GeForce RTX 4070 SUPER 12G VENTUS 2X OC, can use DLSS Frame Generation in any game that offers the toggle, provided the proprietary driver is current. The feature reaches the game through the same NVAPI implementation that carries DLSS upscaling. On RTX 50-series cards, such as the GIGABYTE GeForce RTX 5070 WINDFORCE OC SFF 12G, Multi Frame Generation extends the same path, generating more than one frame per rendered frame in titles that expose the option. NVIDIA pairs frame generation with its Reflex latency feature, which reaches Linux through the same NVAPI path, though coverage varies by title.

The genuine surprise is the driver-level route. NVIDIA documents Smooth Motion in its own Linux driver documentation: it is an implicit Vulkan presentation layer, switched on per game with an environment variable, that infers one additional frame between rendered frames in DirectX 11, DirectX 12 and Vulkan titles without native DLSS Frame Generation. It arrived in the Linux driver for RTX 50-series cards and is documented for RTX 40-series cards in current drivers. NVIDIA’s documentation also carries the key warning: Smooth Motion and native DLSS Frame Generation are competing technologies that should not be used together, and the layer’s asynchronous presentation can conflict with some third-party overlays, with a documented fallback that presents from the graphics queue instead.

AMD: in-game FSR generation works, Fluid Motion Frames does not

AMD’s Linux story is split down the middle. FSR frame generation is part of the game, not the driver: where a title ships FSR 3 or FSR 3.1 frame generation, it runs under Proton on Linux exactly as it does on Windows, and it is brand-agnostic, working on AMD, NVIDIA and Intel hardware alike. That makes it the most widely available form of frame generation on Linux. On RX 9000-series cards, such as the PowerColor Hellhound AMD Radeon RX 9070 XT, FSR 4 upscaling in supported games pairs with that same frame generation path, while RX 6000 and RX 7000 cards, such as the GIGABYTE Radeon RX 7800 XT Gaming OC 16G, use FSR 3 upscaling and frame generation as their ceiling.

The gap is driver-level generation. AMD documents Fluid Motion Frames as a feature of its Adrenalin software, and Adrenalin is Windows software; AMD ships no equivalent for its Linux driver stack, and the open Mesa and RADV drivers have no AMD-built counterpart. The Windows trick of forcing frame generation into almost any game from the driver panel has no official Linux version. What exists instead is community work: afmf-linux, an open-source Vulkan layer that reimplements the Fluid Motion Frames idea using FidelityFX optical-flow components, tuned mainly for RDNA 3 and RDNA 4 cards on the RADV driver, and now bundled by configuration tools such as Goverlay. It is a promising experiment, but it is a reimplementation by enthusiasts, not support from AMD, and it should be described that way.

Intel: upscaling yes, generation mostly borrowed

Intel’s position is the thinnest. XeSS upscaling works on Linux in games that carry it, using the XMX hardware on Arc cards such as the Intel Arc B580 Limited Edition. XeSS frame generation, however, has only limited availability on Linux compared with Windows, and Intel offers no driver-level generation for Linux at all. In practice, Arc owners who want generated frames use a game’s FSR frame generation where offered, and turn to the community layer below for everything else.

The community route: lsfg-vk

The gap-filler is lsfg-vk, a free, open-source Vulkan layer created by community developer PancakeTAS that brings the frame generation model from Lossless Scaling to Linux. The layer sits in the Vulkan presentation path and inserts generated frames as the game presents its own, which lets it work with native Vulkan games and with Proton titles whose graphics reach Vulkan through DXVK or VKD3D-Proton. It runs on any GPU brand, offers fixed frame-rate multipliers and a lighter performance model for modest hardware, and a ground-up version 2 rewrite has since been documented by its developer as substantially faster and lighter on memory than the first release. The dual-GPU offload trick from the Windows app is not supported on the Linux port.

Two status points matter. First, lsfg-vk is not standalone: it uses the frame generation library from Lossless Scaling, so it requires a purchased copy of that app, which is why the app’s own Steam listing points Linux users to the project. Second, it is community software with no vendor behind it; on Steam Deck it is usually installed through the Decky LSFG-VK plug-in, and because it hooks presentation, the compositor setup matters, with the project documenting the Gamescope configuration its layer needs. Treat it as the enthusiast route: remarkably capable, officially nobody’s product.

What every route costs

All frame generation shares the same physics. A generated frame can only be built once the next rendered frame exists, so output is held back by roughly a frame, and the input sampling rate never changes: the picture moves more smoothly, but the game is not responding any faster. That is why every vendor’s guidance assumes a healthy base frame rate. The developer of Lossless Scaling, for example, documents a base rate of at least 30 frames per second as the floor for its model and prefers more. Generation also runs on the same GPU as the game, so a card already at full load pays for generated frames out of its own rendering budget. Finally, quality follows information: engine-integrated methods know where the HUD sits and how objects move, while layer-based methods infer everything from finished pixels, so busy interfaces and fast camera pans are where their artifacts appear first.

How to choose

Route by GPU vendor. On an RTX 50-series card, use in-game DLSS Multi Frame Generation where a game offers it, and NVIDIA’s documented Smooth Motion for titles without it. On an RTX 40-series card, in-game DLSS Frame Generation is the first choice, Smooth Motion is the driver-level fallback, and lsfg-vk covers games with neither. On RTX 20 or 30-series cards there is no DLSS generation path, so use in-game FSR frame generation where offered and lsfg-vk otherwise. On a Radeon RX 9000-series card, pair FSR 4 upscaling with FSR frame generation in game, and treat afmf-linux as an experiment for the rest of your library. On RX 6000 or 7000-series cards, in-game FSR frame generation is the ceiling, with lsfg-vk behind it. On Intel Arc, take XeSS for upscaling and FSR frame generation for generated frames. On Steam Deck and other handhelds, lsfg-vk through its Decky plug-in is the standard route.

Who should skip this

Skip frame generation if you play competitive titles and already reach your monitor’s refresh rate at native resolution: generated frames do not reduce input latency, and responsiveness is the thing you actually feel. Skip it if your games already run at the rate your display can show. And skip it as a rescue measure: layered on a struggling base frame rate, every route in this article produces smoother-looking output that still responds like the low rate underneath, with artifacts on top.

FAQ

Does DLSS Frame Generation work on Linux?

Yes. DLSS Frame Generation works on RTX 40-series cards through Proton in games that offer it, and Multi Frame Generation works on RTX 50-series cards in titles that expose the option. The requirements are a current proprietary NVIDIA driver and an up-to-date Proton build.

Is AMD Fluid Motion Frames available on Linux?

Not from AMD. Fluid Motion Frames is part of AMD’s Adrenalin software for Windows, and neither AMD’s Linux driver nor the open Mesa stack ships an equivalent. A community Vulkan layer called afmf-linux reimplements the idea for RADV users, but it is an unofficial experiment, not an AMD feature.

Is lsfg-vk an official Lossless Scaling product?

No. lsfg-vk is a free, open-source community project that carries the Lossless Scaling frame generation model to Linux through a Vulkan layer. The Lossless Scaling Steam listing itself points Linux users to it, but support runs through the community project, and it requires owning the app because it uses the app’s frame generation library.

Will frame generation make a slow game feel responsive?

No. Frame generation raises the displayed frame rate without sampling your input more often, so motion looks smoother while responsiveness stays at the underlying base rate. It works best layered on a base rate that already feels playable, not as a fix for one that does not.

Final verdict

Frame generation on Linux is real, but it is uneven in a way that maps almost exactly onto GPU vendors. The in-game route is the story: DLSS generation on RTX cards and FSR generation everywhere else both work through Proton today. NVIDIA goes further, with a documented driver-level option in Smooth Motion. AMD’s gap is precisely at the driver level, where Fluid Motion Frames remains a Windows feature, and Intel owners mostly borrow AMD’s in-game route. Everything the vendors leave out, the community has patched over with lsfg-vk, at the usual community price of extra setup and a step down in quality. Check which camp your card falls into before assuming a Windows feature list applies to you.

MSI GeForce RTX 4070 SUPER 12G VENTUS 2X OC Graphics Card

MSI GeForce RTX 4070 SUPER 12G VENTUS 2X OC Graphics Card

Check price on Amazon

GIGABYTE GeForce RTX 5070 WINDFORCE OC SFF 12G Graphics Card

GIGABYTE GeForce RTX 5070 WINDFORCE OC SFF 12G Graphics Card

Check price on Amazon

PowerColor Hellhound AMD Radeon RX 9070 XT 16GB GDDR6 Graphics Card

PowerColor Hellhound AMD Radeon RX 9070 XT 16GB GDDR6 Graphics Card

Check price on Amazon

GIGABYTE Radeon RX 7800 XT Gaming OC 16G Graphics Card

GIGABYTE Radeon RX 7800 XT Gaming OC 16G Graphics Card

Check price on Amazon

Intel Arc B580 Limited Edition Graphics Card

Intel Arc B580 Limited Edition Graphics Card

Check price on Amazon

Explore Our Guides & Free Tools