✅ 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 Valve Steam Deck OLED 512GB, with Samsung T9 Portable SSD 2TB as a strong alternative.

Community compatibility builds are where Linux gaming quietly gets much of its power. GE-Proton fixes cutscenes and stubborn launches that Valve’s official Proton cannot touch, Wine-GE does similar work outside Steam, and Luxtorpeda swaps in native Linux engines for classic games. The annoying part was never using these builds. It was fetching them: release pages, tarballs, checksums, and a different destination folder for every launcher.

ProtonUp-Qt exists to delete that chore. It is a small open-source graphical manager that downloads community Proton and Wine builds, verifies and unpacks them, and installs each one into the correct folder for Steam, Lutris, Heroic Games Launcher or Bottles. This explainer covers what it manages, where to get it, the path problem that trips up Flatpak Steam users, and the cases where installing a build by hand is still better.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

ProtonUp-Qt is a free graphical tool that installs and manages community compatibility builds — GE-Proton, Wine-GE, Luxtorpeda and more — for Steam, Lutris, Heroic and Bottles. Pick a launcher, click Add version, choose a build, and it downloads, verifies and unpacks it into the right folder. Get it from Flathub or as an AppImage, and restart the launcher afterwards so the new build appears.

What ProtonUp-Qt actually manages

The main window is built around two choices: a launcher at the top and a list of installed builds below it. The supported targets are wider than most people expect: alongside regular installs, the project supports Snap and Flatpak installations of the launchers too, which matters for the path problem covered below.

For Steam, the headline tool is GE-Proton, GloriousEggroll’s community build with the media codecs and game-specific patches that licensing keeps out of Valve’s releases. The Steam list also includes Luxtorpeda, which replaces a game’s engine with a native Linux source port where one exists, plus Boxtron for DOS titles, Roberta for ScummVM games, NorthstarProton for Titanfall 2’s Northstar client, and Proton-Tkg.

For Lutris, Heroic and Bottles, the menu shifts from Proton to Wine: Wine-GE, the GloriousEggroll build for use outside Steam, alongside Lutris-Wine and Kron4ek’s vanilla Wine builds. ProtonUp-Qt can also fetch DXVK and VKD3D-Proton for launchers that manage those components manually.

One detail makes the tool more useful than a download script: double-clicking an installed build shows which games are using it, which is exactly what you want to know before deleting anything.

Getting it: Flatpak, AppImage and distro packages

The project’s recommended route is Flathub, where ProtonUp-Qt is published under the application ID net.davidotek.pupgui2. On a Steam Deck that means installing it from the Discover store in Desktop Mode, like any other desktop application. On a regular distribution, any software centre with Flathub enabled will offer it.

The alternative is the AppImage published on the project’s release page: download the file, mark it executable, and run it. That suits portable setups and systems where Flatpak is not welcome, at the cost of updating it yourself. Some distributions also carry native packages, which integrate best with the system but can lag behind upstream releases.

One habit saves confusion: fully restart the launcher after installing a build. Launchers scan their tool folders at startup, so a build installed while the launcher is open will not appear until the next launch.

The Flatpak Steam path problem

The most common support question runs: the tool says the build installed, but Steam never shows it. Almost every time, the cause is a mismatch between where ProtonUp-Qt wrote the build and where that Steam reads from.

A native Steam install keeps custom compatibility tools in a compatibilitytools.d folder inside the Steam directory in your home folder. A Flatpak Steam keeps its data in a sandboxed location under the Flatpak application data area instead, and a Snap install has its own path again. Mixing a Flatpak ProtonUp-Qt with a native Steam, or the reverse, can leave the sandboxed tool unable to see or write the folder the other expects.

The fix is to check that the install directory shown in ProtonUp-Qt matches the Steam you run, and change it if it does not. If sandbox permissions block the folder, granting access with a tool such as Flatseal resolves it. The tax only needs paying once.

Day-to-day: adding, updating and removing builds

Adding a build is three steps for every launcher: select the launcher, click Add version, pick the tool and release. ProtonUp-Qt pulls the archive from the project’s official source, checks it, and unpacks it into the target folder with the correct name, so the launcher lists it as it would a hand-installed build.

There is no in-place upgrade. A newer GE-Proton is another build installed alongside the old one; you switch games over in each launcher’s settings, and the old build stays put until you remove it, which makes rolling back painless when a new release breaks a game.

Removal happens in the same list: select a build, remove it, and the tool deletes its folder. Each build occupies substantial disk space, and a year of chasing releases for four launchers accumulates into gigabytes of builds nothing uses. The double-click view turns cleanup from a gamble into a quick audit.

Advanced options and the ctmod question

ProtonUp-Qt keeps its advanced settings in an unglamorous place: the About dialog, which is also where the colour theme lives. The tool is deliberately conservative, and most users will never need to open that dialog.

The project’s documentation also references ctmod, inherited from the older command-line ProtonUp tooling: a feature for defining custom compatibility tool directories and variants. Its state has changed across releases, so treat the documentation for your installed version as the authority. Stock behaviour covers Steam, Lutris, Heroic and Bottles in their normal, Snap and Flatpak forms either way; custom directories are an opt-in extra for unusual layouts.

When manual installation is still the better route

For all its convenience, ProtonUp-Qt is not always the right tool. Installing a build manually — downloading the archive and unpacking it into the tools folder yourself — remains better in a few situations.

Pinning an exact archived release is one: anyone testing a patched or self-compiled build has to place it by hand anyway. Automation is another: a manual install can be scripted and repeated across machines, while a graphical tool asks for clicks every time. Finally, the manual route is the best troubleshooting skill you can own, because every launcher problem reduces to one question: is the right folder, with the right name, in the right directory? ProtonUp-Qt hides that question on good days. On bad days, you will be glad you know the answer.

Gear that makes build-hopping painless

The routine around this software — several launchers, big downloads, a Deck in Desktop Mode — is more comfortable with a few basics in place.

Valve Steam Deck OLED 512GB

Valve Steam Deck OLED 512GB

Valve Steam Deck OLED 512GB

Check price on Amazon

The Deck is where ProtonUp-Qt feels most at home, run in Desktop Mode whenever a new GE-Proton lands. The 512GB model leaves room for several builds alongside a real game library.

Specs:
– Display: 7.4-inch HDR OLED, 1280 by 800, up to 90 Hz
– Storage: 512GB NVMe SSD with microSD expansion
– Processor: AMD Zen 2 CPU with RDNA 2 graphics
– Memory: 16GB LPDDR5
– System: SteamOS 3, an Arch-based Linux distribution
– Wireless: Wi-Fi 6E and Bluetooth 5.3

Samsung T9 Portable SSD 2TB

Samsung T9 Portable SSD 2TB

Samsung T9 Portable SSD 2TB

Check price on Amazon

Builds and their games add up quickly. The T9 gives a desktop or docked Deck a fast two terabytes for a shared library, though its headline speed needs a USB 3.2 Gen 2×2 host many machines, the Deck included, lack.

Specs:
– Capacity: 2TB
– Interface: USB 3.2 Gen 2×2, 20 Gbps
– Maker-rated sequential read: up to 2,000 MB/s on a Gen 2×2 host
– Model: MU-PG2T0B/AM
– Weight: 4.3 ounces
– Cables: USB-C to USB-C and USB-C to USB-A included

8BitDo Ultimate 2 Bluetooth Controller

8BitDo Ultimate 2 Bluetooth Controller

8BitDo Ultimate 2 Bluetooth Controller

Check price on Amazon

Build testing means launching the same games repeatedly; a controller that pairs over Bluetooth and drops into its dock afterwards keeps that loop tidy on desktop and Deck alike.

Specs:
– Connection: Bluetooth and wired USB-C
– Sticks: TMR electromagnetic joysticks
– Extras: two back buttons, extra shoulder bumpers, trigger mode switches
– Dock: charging dock included
– Maker-listed platforms: Nintendo Switch, Windows and SteamOS

SanDisk Extreme microSDXC 1TB

SanDisk Extreme microSDXC 1TB

SanDisk Extreme microSDXC 1TB

Check price on Amazon

On the Deck, a large microSD card is the simplest home for a second library tier, leaving internal storage for the system, shader caches and the builds themselves.

Specs:
– Capacity: 1TB
– Class ratings: UHS-I, U3, V30, A2
– Maker-rated speeds: up to 190 MB/s read and 130 MB/s write, host dependent
– Model: SDSQXAV-1T00-GN6MA

Logitech K380 Multi-Device Bluetooth Keyboard

Logitech K380 Multi-Device Bluetooth Keyboard

Logitech K380 Multi-Device Bluetooth Keyboard

Check price on Amazon

ProtonUp-Qt lives in Desktop Mode, where a paired keyboard beats the on-screen one. The K380 switches between three paired devices, so one keyboard serves a desktop and a docked Deck.

Specs:
– Layout: compact multi-device keyboard
– Connection: Bluetooth with Easy-Switch keys for up to three devices
– Power: two AAA batteries, maker-rated life up to 24 months
– Model: 920-007558, Dark Grey
– Maker-listed systems: Windows, macOS, ChromeOS, Linux, Android and iOS

How to choose your setup

Choose the Flathub build if your launchers also come from Flathub or your distribution’s store, because matching sandbox styles avoids most path surprises. Choose the AppImage for one portable file you control, or a native package if your distribution maintains one.

Steam-only players need nothing more than GE-Proton and occasional pruning. Multi-launcher players get the most from the tool, because Wine-GE for Lutris, Heroic and Bottles is where folder conventions diverge and manual installs go wrong. Either way, keep at most two or three builds per launcher: the newest, the one your games are pinned to, and nothing else.

Who should skip this

Skip ProtonUp-Qt if you only ever use Valve’s official Proton and it runs everything you play; the tool manages community builds, and if you never install one it has nothing to do. Skip it if you are comfortable with release tarballs and already keep your compatibility folders tidy by hand. And skip the community builds themselves if a game’s anti-cheat situation makes unofficial builds a policy question rather than a technical one — follow the publisher’s stated position.

FAQ

Is ProtonUp-Qt safe to use?

It is open-source, published on Flathub, and it downloads builds from the official release pages of the projects it supports, verifying the archives it fetches. Install it from Flathub or the project’s own page, not third-party download sites.

Does ProtonUp-Qt update my builds automatically?

No. Each build is its own folder, and a new release is added alongside the old one rather than replacing it. You switch games to the newer build in your launcher’s settings, then remove the old build from the list when nothing uses it.

Why does Steam not show the build I just installed?

Restart Steam first, because it scans for compatibility tools at startup. If the build is still missing, it is probably the Flatpak path problem: check that the install directory in ProtonUp-Qt matches the Steam you run, especially if either is a Flatpak or Snap install.

Can I use ProtonUp-Qt on the Steam Deck?

Yes. Install it from the Discover store in Desktop Mode. It manages builds for the Deck’s Steam exactly as on a desktop, and it is the easiest way to keep GE-Proton current on the handheld.

Final verdict

ProtonUp-Qt does one unglamorous job — putting the right build in the right folder — for every launcher that matters on Linux. That makes it standard equipment for anyone who uses GE-Proton or Wine-GE regularly. Learn the manual route once so the folders are never a mystery, then let the tool handle the routine.

Explore Our Guides & Free Tools