DLSS 5 Swapper: one-click DLSS 5 installs, an F8 overlay and a per-GPU community verdict
Install, tune and restore DLSS 5 in your games with one click. Native RenoDX, DLSS5-Feeder for games without DLSS, OptiScaler and multipass routes; DirectX 8/9/11/12, Vulkan, OpenGL, DirectDraw and emulators. In-game F8 overlay, automatic backups, and a community page showing what works on your games and your graphics card.
At a glance
- What is it?
- DLSS 5 Swapper is a Windows Electron app that finds your games across Steam, Epic, GOG and Game Pass folders, installs DLSS 5 Neural Rendering through several routes, and backs up the originals first. The interesting part is not the install button but the routing logic and the community reports filtered to your own graphics card.
- Who is it for?
- Adopt it if you run Windows 10 or 11 and want DLSS 5 in games that ship without it, and you accept that installs write into game folders, so Restore originals is your undo button. Skip it if you play on Linux, or if you want a tool that only swaps DLLs and never touches the renderer.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 5 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 16, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What DLSS 5 Swapper solves that a DLL swap does not
A plain DLSS DLL swap assumes the game already ships DLSS and that replacing one file is enough. DLSS 5 Swapper targets a wider set: games with native DLSS, games with no DLSS at all through DLSS5-Feeder, and older titles running DirectX 8, DirectX 9, DirectX 11, DirectX 12, Vulkan, OpenGL, DirectDraw and emulator builds. The README lists those APIs as the supported surface, and the 2.2.7 notes show how broad that gets in practice, with fixes for DirectDraw games such as Gens and other emulators.
The audience is Windows players who own a library spread across Steam, Epic, GOG and modern Xbox Game Pass folders, plus manually added games and emulators. The app scans those libraries, groups them by store or shows one list, and filters by title, graphics API, DLSS status and add-ons. Full-drive scanning is off by default, which is a deliberate choice: you add the folders you want indexed instead of handing the tool your whole disk.
Where this differs from a swapper is that it manages an installation rather than a file. Each install can be recorded, backed up and reversed, and the Save diagnostics button writes one file with the install log, the game's own ReShade and Feeder logs, the manifest and your driver, shown to you before it is written.
The four installation routes and what decides between them
The README names four routes: native RenoDX, DLSS5-Feeder for games without DLSS, OptiScaler, and multipass. They are not interchangeable. Native DLSS games take the direct path. Games with no DLSS of their own go through DLSS5-Feeder, which is the mechanism that makes a non-DLSS title render the neural pass at all. OptiScaler is a separate route exposed as an add-on alongside the integrated ones. Multipass is the most unusual: it runs the neural pass up to ten times per frame on DirectX 12, DirectX 11 and 64-bit DirectX 9, and the 2.2.5 release is where it appeared.
The app also exposes a rendering API override, per game, with Automatic as the default. Detection is never overwritten, so the override is an explicit escape hatch rather than the normal path. That matters because misidentifying a renderer is the most common way these tools break a game: the 2.2.7 notes describe Prey, Titanfall 2, Call of Duty 2 and Max Payne being read as "No 3D executable" because their renderer is a DLL beside the executable. The fix accepts a Direct3D library in the executable's own folder.
A second identification problem shows up with shared executables. Portal was filed under Half-Life 2 because both run hl2.exe. The 2.2.7 fix stops an executable many games share, including every emulator, from deciding which card a report lands on. If you have ever wondered why a tool mislabels your library, this class of bug is the answer.
Installing DLSS 5 Swapper and running your first install
The README points to the latest release page for both a Windows installer and a portable build, with SHA256SUMS.txt beside them. There is no package manager route documented and no npm install for end users, so the release page is where you start. The app targets Windows 10 and 11.
If you want to run it from source instead, the repository is an Electron app. The package.json defines a start script and a test suite:
git clone https://github.com/rakanki911/DLSS5-Swapper
cd DLSS5-Swapper
npm install
npm startThe start script is electron ., so npm start launches the desktop window. The same file defines npm test as node --test --test-concurrency=1 test/*.test.js, and there are separate payload checks for the Feeder and OptiScaler routes:
npm test
npm run test:payload
npm run test:optiscalerThose scripts run the project's own checks against the payloads it ships. They are not a substitute for launching a game.
Once the app is open, the workflow the README describes is: let it index your Steam, Epic, GOG and Game Pass folders, or add a game or emulator manually, then open a game and install. Before you press install, the game page shows what the community found for that title, directly above the install button. That ordering is intentional, and it is the part worth using on a game you have not modded before.
After an install, press F8 in the running game to open the app's panel and move the real DLSS Neural Rendering sliders while you play. The README states the overlay supports the DLSS5-Feeder and RenoDX v4.7 routes only, so do not expect it on every route. Drag the grip in the bottom right corner to resize it, and each game remembers its own size.
Where DLSS 5 Swapper fails, and the games it should not touch
The most direct limitation is documented by the project itself. Games installed under Program Files failed with EPERM because Windows protects that folder. The 2.2.7 fix does not bypass the protection; it tells you up front to run as administrator or move the game. If your library lives under Program Files and you cannot elevate, that is a wall, not a warning.
The driver warning is the second one, and the release notes are refreshingly honest about it. The warning previously read like a hard requirement. The 2.2.7 text says it is a warning, that many people run newer drivers without trouble, especially with MSI Afterburner and RivaTuner closed. Read that as: the check is advisory, and closing those two tools is the first thing to try when something misbehaves.
Uninstalling is the third. The uninstaller never touches game folders, and 2.2.7 changed it to say so and to point at Restore originals first. If you expect uninstall to clean a game back to stock, it will not. Restore originals is the operation you want, and it is a separate step.
Finally, the overlay is route-limited to DLSS5-Feeder and RenoDX v4.7. If you install through OptiScaler or multipass, F8 is not the control surface. The README does not document what tuning is available on those routes from inside the game.
How it compares to beeradmoore/dlss-swapper
The related searches for this project include DLSS DLL swap and the beeradmoore/dlss-swapper releases page, so the comparison is worth stating plainly. DLSS Swapper swaps DLSS DLLs. That is a narrower job: it assumes the game already uses DLSS, and it changes which library version the game loads.
DLSS 5 Swapper does the DLL work and then goes further, into games that have no DLSS to swap. DLSS5-Feeder is the mechanism for those titles, and multipass runs the neural pass multiple times per frame on DirectX 12, DirectX 11 and 64-bit DirectX 9. That is a different category of change: it modifies how the frame is rendered, not which library version is loaded.
The trade-off is scope. A DLL swapper touches one file and is easy to reason about. This app writes into game folders, keeps backups, maintains history, and can install ReShade as part of a route, which is why the 2.2.7 notes include a fix for a read-only ReShade.ini banner. If you want the smallest possible change to your install, the narrower tool is the safer pick. If your game has no DLSS at all, the narrower tool has nothing to offer you.
The community layer has no equivalent in a swapper. Reports are narrowed to the games installed on your PC and the graphics card in it, and 2.2.7 added a filter to show only reviews from people with your card. That is the feature that answers "does this work on my hardware" without forum archaeology. It is opt-in, and the README states everything you leave can be edited, deleted or withdrawn.
Licence, third-party components and what upgrades cost you
The project is MIT licensed, and package.json carries the same identifier. The only runtime dependency listed there is extract-zip, with Electron and electron-builder as dev dependencies. That is a thin dependency surface for a desktop app, which keeps the audit small.
MIT covers the application code. It does not cover what the app downloads and installs. The repository carries a THIRD_PARTY_NOTICES.md at the top level, and the build configuration ships it inside the packaged app, which tells you the authors treat the bundled components as a licensing matter. The README names dgVoodoo in the DirectDraw fix, and ReShade appears throughout the install and overlay descriptions. Those are separate projects with their own terms. If you plan to redistribute a modded game folder, check those notices rather than assuming the MIT licence travels with the payload.
The upgrade cost is low and the cadence is fast. Three releases landed in the week before the last push on 2026-09-13: v2.2.5 on 2026-09-09, v2.2.6 on 2026-09-10 and v2.2.7 on 2026-09-12. Each one carries tracker fixes, and several of them change installer behaviour. That means an install performed with an older build may not match what the current build does, which is an argument for keeping History and the diagnostics file rather than deleting them after a successful install.
Editorial conclusion
Adopt it if you run Windows 10 or 11 and want DLSS 5 in games that ship without it, and you accept that installs write into game folders, so Restore originals is your undo button. Skip it if you play on Linux, or if you want a tool that only swaps DLLs and never touches the renderer. Before your first install, check the DirectDraw and Direct3D library fixes in the 2.2.7 notes against the game you care about, and confirm your card appears in the Community filter.
Frequently asked questions
What does DLSS 5 Swapper do that a DLSS DLL swap does not?
It installs DLSS 5 Neural Rendering through several routes, including DLSS5-Feeder for games that ship no DLSS at all, and multipass, which runs the neural pass up to ten times per frame on DirectX 12, DirectX 11 and 64-bit DirectX 9. A DLL swap only changes which DLSS library an already-DLSS game loads.
Which games and graphics APIs does DLSS 5 Swapper support?
The README lists DirectX 8, 9, 11 and 12, Vulkan, OpenGL, DirectDraw and emulators, alongside native DLSS games and compatible non-DLSS games through DLSS5-Feeder. It targets Windows 10 and 11.
Does the F8 overlay work on every installation route?
No. The README states the in-game overlay supports the DLSS5-Feeder and RenoDX v4.7 routes only, so it is not available when you install through OptiScaler or multipass.
How do I undo a DLSS 5 Swapper installation?
Use Restore originals, which the app provides per game and which the 2.2.7 uninstaller points to. The README states uninstalling never touches game folders, so uninstall alone will not return a game to its original files.
What does NVIDIA DLSS actually do?
The repository does not explain DLSS itself; it treats DLSS 5 Neural Rendering as the thing it installs and manages. The README offers no description of the technology beyond the name and the routes it supports.
Is it better to have DLSS on or off?
The README does not answer this. It describes installing and tuning DLSS 5 Neural Rendering, and the in-game overlay lets you move the real sliders while you play, but it makes no claim about whether enabling it is better for any given game.
Community notes