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

For years, running a Windows game with Proton outside Steam meant every launcher improvised its own method. Lutris, Heroic and Bottles each assembled the runtime environment differently, so the same game on the same Proton build could work in one front-end and fail in another, and a fix discovered by one community rarely transferred cleanly to the others. UMU Launcher, from the Open-Wine-Components project, exists to end that fragmentation: it is a single shared runtime that puts any Proton build inside Valve’s Steam Runtime container, exactly the way Steam itself does, no matter which front-end started the game.

This explainer walks through why that container matters, what the umu-run tool actually does between you pressing Play and the game window appearing, and what changes inside each launcher that has adopted it. It also covers the shared protonfixes database — arguably the bigger deal: one library of per-game fixes every front-end now draws from.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

UMU Launcher is a shared runtime from the Open-Wine-Components project that runs Windows games with Proton outside Steam. Its umu-run tool places the game inside Valve’s Steam Runtime container, exactly as Steam does, so Lutris, Heroic and Bottles all launch Proton builds the same consistent way instead of each improvising.

The problem UMU exists to solve

Proton was never designed to run naked on a Linux desktop. When Steam launches a Proton game, the game does not run directly against your distribution’s libraries. It runs inside the Steam Runtime, a containerised environment built with Valve’s pressure-vessel tooling that supplies known versions of the libraries Proton expects. That controlled environment is a large part of why a Proton build behaves predictably across thousands of different Linux installs.

The trouble started when launchers outside Steam began offering Proton as a runner. Proton is attractive: it carries Valve’s patches, media components and per-game work that plain Wine lacks. But each front-end had to fake the Steam environment on its own, and each did it incompletely and differently. Environment variables were set inconsistently, runtime libraries were missing or doubled, and prefix behaviour diverged. The result was a familiar support pattern: a game reported working in Heroic failed in Lutris, a workaround written for one launcher did nothing in the other, and nobody could reproduce anyone else’s bug report because no two setups launched the game the same way.

UMU’s answer is architectural rather than cosmetic. Instead of every front-end maintaining its own Proton plumbing, the plumbing moves into one upstream tool that every front-end calls. The front-ends keep doing what they are good at — libraries, store logins, banners, settings screens — while the actual business of starting Proton is delegated to umu-run.

What umu-run does under the hood

When a front-end launches a game through UMU, it hands umu-run a small set of facts: the path to the game executable, the Wine prefix to use, the Proton build to run, and a game identifier. From there, umu-run reproduces the sequence Steam itself performs. It obtains the current Steam Runtime — the Sniper runtime used by modern Proton — and enters it through pressure-vessel, so the game sees the same library environment it would see under Steam. It points the runtime at the chosen Proton build, whether that is a build distributed for use with UMU, a GE-Proton release, or another compatible build installed on the system.

The prefix handling matters more than it sounds. Proton expects to create and maintain prefixes in particular ways, and several historical non-Steam bugs traced back to prefixes built under slightly different assumptions. Because umu-run follows the same code path Steam uses, the prefix a game gets in Lutris is now structurally the same prefix it would get in Steam. That sameness is what makes support advice portable again: instructions written against one front-end’s UMU launch apply to the others, because underneath, they are the same launch.

The game identifier deserves its own mention. Front-ends pass an ID for the title — drawn from the store the game came from where one exists. That ID is the key UMU uses to look up per-game fixes, which is the subject of the next section. Where no meaningful ID exists, a default identifier is used and the game simply runs without title-specific adjustments.

Protonfixes: one fix database for every launcher

Alongside the runtime, the UMU project maintains a database of per-game fixes, continuing the protonfixes tradition that GE-Proton popularised. A fix is a small, targeted adjustment applied automatically for a specific title: an environment variable the game needs, a component installed into the prefix, a library override, or a workaround for a launcher or anti-cheat quirk. Under the old fragmented model, these fixes lived inside individual projects, so a fix written for one front-end’s users never reached the others.

With UMU, the fix database is keyed to the game identifier and applied by umu-run itself, below the front-end layer. A fix contributed once now lands for Lutris, Heroic and Bottles users alike, and for people running umu-run directly from a terminal. This also sharpens bug reports: when every launcher runs the game through the same runtime with the same fixes, a failure that remains is far more likely to be a real Proton or game issue than a quirk of one front-end’s plumbing, which makes it actionable upstream.

What changes inside each front-end

In Lutris, UMU has become the standard path for Proton-based runners, replacing the older pattern of Lutris-specific Wine and Proton handling; the practical effect is that choosing a Proton build in Lutris now behaves like choosing one in Steam, fixes included. Heroic Games Launcher offers UMU for its Epic, GOG and Amazon library titles, which closes the odd gap where a game’s Steam version enjoyed Valve’s environment while the identical GOG version, launched from Heroic, did not. Bottles has integrated UMU support as well, notable because Bottles’ own bottle model was the most independent of the three; even there, delegating Proton launches to the shared runtime proved simpler than maintaining a parallel implementation.

For people who avoid front-ends entirely, umu-run also works standalone from the command line: supply the executable, prefix, Proton build and game ID, and the game launches in the same container Steam would have used. That makes UMU useful as a scripting tool for testers, who can finally reproduce a front-end user’s launch exactly, and for minimal setups that want Proton’s behaviour without installing Steam.

The hardware that makes it feel instant

UMU is software, but the launches it standardises lean on storage and input hardware. These are the sensible companions for a multi-launcher library.

Samsung 990 PRO 2TB NVMe SSD

Samsung 990 PRO 2TB NVMe SSD

Samsung 990 PRO 2TB NVMe SSD

Check price on Amazon

  • Specs: PCIe 4.0 x4 interface, NVMe; maker-rated sequential reads up to 7,450 MB/s; M.2 2280 form factor.

One large, fast drive keeps Steam, GOG and Epic prefixes side by side, and prefix creation through umu-run is a storage-bound task.

WD Black SN850X 2TB NVMe SSD

WD Black SN850X 2TB NVMe SSD

WD Black SN850X 2TB NVMe SSD

Check price on Amazon

  • Specs: PCIe Gen4 x4 interface; maker-rated sequential reads up to 7,300 MB/s; M.2 2280; Game Mode 2.0 feature set.

A second strong Gen4 option for a dedicated games drive, well suited to holding several front-ends’ libraries on one volume with a single shared UMU setup.

Xbox Wireless Controller (Carbon Black, 2025)

Xbox Wireless Controller (Carbon Black, 2025)

Xbox Wireless Controller (Carbon Black, 2025)

Check price on Amazon

  • Specs: Xbox Wireless and Bluetooth connectivity; USB-C wired option; hybrid D-pad and dedicated Share button; model EP2-29929.

Games launched outside Steam rely on the front-end and Steam Input alternatives for pad support; this controller’s dual wireless standards make it the low-friction choice across all of them.

Valve Steam Deck OLED 512GB

Valve Steam Deck OLED 512GB

Valve Steam Deck OLED 512GB

Check price on Amazon

  • Specs: 7.4-inch HDR OLED display; custom AMD APU; 512GB NVMe internal storage; Wi-Fi 6E.

The Deck is where many players meet non-Steam libraries first, and its front-ends use the same UMU runtime, so fixes learned on the desktop carry over to the handheld unchanged.

Samsung T9 Portable SSD 2TB

Samsung T9 Portable SSD 2TB

Samsung T9 Portable SSD 2TB

Check price on Amazon

  • Specs: USB 3.2 Gen 2×2 interface; maker-rated speeds up to 2,000 MB/s; USB-C connection; compact metal enclosure.

A fast portable drive lets a UMU-based library travel between a desktop and a laptop, with prefixes built by the same runtime on both machines.

How to choose

Choose by where your library lives. If every game you play is in Steam, you gain nothing from UMU directly: Steam already runs Proton inside its runtime, and UMU deliberately replicates that rather than improving on it. Your front-end is Steam, and it is already doing the job.

If your library is mixed — GOG releases, Epic giveaways, itch.io downloads, Amazon titles — choose a front-end you like for its library features and let UMU handle the launches underneath. Lutris suits script-driven installs and broad source support, Heroic suits store libraries with minimal fuss, and Bottles suits people who think in self-contained app environments. Because all three now delegate Proton launches to umu-run, that choice is about interface and library management, not about which one runs games better. For a single loose executable with no library at all, plain umu-run from the terminal is the honest option: no front-end, same runtime, same fixes.

Who should skip this

Skip UMU if your gaming is entirely inside Steam, since Steam’s own launch path already provides everything UMU replicates. Skip it if you play only native Linux games, which never touch Proton or Wine. And skip the standalone command-line route if you are new to Linux gaming entirely: a front-end using UMU under the hood gives you the same runtime with a far gentler learning curve, and you can graduate to umu-run later without changing anything about how your games launch.

FAQ

Is UMU a replacement for Proton?

No. UMU is the launcher layer that runs Proton builds the way Steam does. You still choose a Proton version — a UMU-distributed build, GE-Proton or another compatible release — and umu-run places that build inside the Steam Runtime container with the right prefix and environment.

Does UMU work for games that are not on Steam?

That is its main purpose. Epic, GOG, Amazon and standalone games launched through Lutris, Heroic or Bottles can all run through umu-run, gaining the Steam Runtime environment and the shared protonfixes database previously available only to Steam launches or one front-end’s private implementation.

What is a game ID, and why does it matter?

The game ID identifies the title to UMU so it can apply that game’s specific fixes from the protonfixes database. Front-ends usually supply the store’s identifier automatically. With the wrong or default ID the game still runs, but it will not receive its title-specific adjustments.

Is UMU the same thing as GE-Proton?

No, though they are closely related and share people. GE-Proton is a Proton build carrying extra patches and components. UMU is the runtime that launches Proton builds outside Steam. The two are designed to work together: GE-Proton is one of the builds umu-run can launch.

Final verdict

UMU Launcher is the least glamorous kind of progress: infrastructure. It does not add frames, features or a prettier interface. What it does is collapse three divergent ways of running Proton outside Steam into one shared, Steam-faithful runtime, and unify the per-game fixes every community maintained separately. If your library lives in one store, you may never notice it. If your library lives everywhere, UMU is the reason your front-end of choice now launches games the same way Steam would — and why a fix written by a stranger in another launcher’s community quietly fixes your game too.

Explore Our Guides & Free Tools