Installing a game on Linux may work at launch, then an hour later you are trying to remember which launcher set it up. Heroic, Lutris, and Bottles all promise to make Windows games run on Linux, and at a glance they look interchangeable. They are not. Each is built around a different idea of how you manage games, and that idea shapes where save files live and how many clicks a game needs before it boots.
This guide breaks down the workflow differences that actually matter: how each tool organizes game environments, how it handles installs, and which type of player each one suits. The focus stays on practical habits rather than hype. (Keyboard foam mod sound differences actually changes)
What Each Launcher Actually Is
Before comparing workflows, it helps to know what each tool does under the hood. None of them is a compatibility layer. All three ultimately lean on Wine, the open-source layer that translates Windows system calls, and on DXVK, which translates Direct3D calls into Vulkan. The differences live in the management layer on top.
Lutris is a launcher and manager first. It does not run games by itself; it orchestrates runners like Wine, Proton, and various emulators, then ties them together with install scripts. It has been around since 2010, which explains its sprawling, community-driven approach.
Heroic Games Launcher is a front-end for specific stores. It logs into your Epic Games, GOG, and Amazon Games accounts and pulls your library across. For Windows-only titles, it wraps them in Wine or Proton. Its center of gravity is your store account, not a per-game recipe.
Bottles flips the model entirely. Instead of launching games, it manages bottles: isolated Wine prefixes, each with its own settings, installed components, and runner version. You create a bottle, install something into it, and that environment stays sealed off from everything else.
| Tool | Core model | Primary job | Typical user |
|---|---|---|---|
| Lutris | Launcher plus install scripts | Automate per-game setup | Tinkerers with mixed libraries |
| Heroic | Store front-end | Sync and launch store libraries | Epic, GOG, and Amazon owners |
| Bottles | Isolated prefixes | Manage Windows apps and games | People who want clean separation |
That table is the whole argument in miniature. Everything else follows from these three starting points.
The Install Workflow: Scripted, Synced, or Sealed
The single biggest day-to-day difference is how a game gets installed.
Lutris uses community-maintained install scripts, usually written in YAML and hosted in a public repository. When you pick a game from its catalog, the script handles the boring parts: creating the prefix, choosing a runner version, applying known tweaks, and sometimes downloading patches. For popular titles this feels close to magic. For obscure ones, you may find no script at all and end up configuring everything by hand. The trade-off is real: scripts are only as good as their last maintainer, and a stale script can produce a broken prefix that looks identical to a working one until launch day.
Heroic skips scripts almost entirely. You log in to a store, your library appears, and you press install. The heavy lifting is done by backends such as Legendary for Epic and gogdl for GOG, which handle downloads and authentication. There is no per-game recipe to maintain because there is no per-game recipe. The catch is scope: if a game is not in one of the supported stores, Heroic has little to offer beyond adding it manually as a sideloaded title.
Bottles asks you to think in environments. You create a bottle, choose a runner, install DXVK or VKD3D components if needed, then run an installer inside it. This is more work upfront, but it gives you something the other two cannot: a container you can back up, copy, or delete without touching anything else. If you have ever broken one game’s prefix and watched three others stop working, the appeal is obvious.
Where Your Files and Settings Live
File layout is the quiet workflow difference that bites people months later.
Lutris keeps game data under its own directory structure, with prefixes and configuration stored per game. Backups mean copying folders and hoping you remember which runner version was in use. Heroic stores prefixes per game as well, but because it is store-driven, your cloud saves from Epic or GOG often do the heavy lifting. Bottles is the most portable of the three: each bottle is a self-contained directory, which makes migration between machines almost trivial.
If you already run a local-first notes setup for tracking configs and fixes, the same instinct applies here. Keeping a plain-text log of which runner version each game uses saves hours of guessing later, much like the discipline described in this comparison of Obsidian vs Logseq local first notes compared by workflow. The tools differ, but the habit is identical: own your data, write it down, and keep it where you can find it.
Sandboxing and System Integration
Bottles ships primarily as a Flatpak, which changes how it interacts with your system. Sandboxing is good for stability and security, but it also means filesystem access is restricted by default. New users often install a game, then discover the launcher cannot see a folder on a secondary drive. The fix is a permission toggle, but you have to know it exists. This is the most common Bottles stumbling block, and it has nothing to do with Wine at all.
Lutris and Heroic, by contrast, typically run with full access to your home directory, which makes them feel more permissive and slightly less predictable. Neither approach is wrong. Bottles trades convenience for isolation; Lutris and Heroic trade isolation for convenience.
Performance and Compatibility: The Same Engine, Different Tuning
Here is the part people overthink. Because all three rely on Wine, Proton, and DXVK, raw performance is usually within a few percent between them for the same game on the same hardware. What differs is how easily you can tune it.
Lutris exposes runner versions and environment variables openly, and its scripts often pre-set the options that matter. Heroic offers per-game settings for Proton versions and launch arguments, which is enough for most store titles. Bottles gives you the deepest control through per-bottle runner and component selection, but you must understand what you are changing.
A useful rule: if a game runs badly in one launcher, it will probably run badly in the others until you fix the underlying issue, whether that is a missing Vulkan driver, a shader cache problem, or an outdated runner.
Which Launcher Fits Your Habits?
The right choice depends less on features than on how you like to work.
Choose Heroic if your library lives on Epic, GOG, or Amazon and you want a login-and-play experience with minimal fiddling. It is the closest thing to a console-style workflow on Linux.
Choose Lutris if you own games from many sources, including old discs, standalone installers, and emulated titles, and you appreciate a catalog that has probably already solved your problem.
Choose Bottles if you want clean separation between apps, plan to run non-game Windows software, or value portable, disposable environments you can rebuild in minutes.
Many experienced users run more than one. A common split is Heroic for store libraries, Lutris for oddball titles, and Bottles for anything experimental. If you are the type who also disables background assistants to keep a machine lean, the same logic from this guide on how to disable copilot windows 11 without breaking your workflow applies: remove what you do not need, keep what earns its place.
Common Mistakes That Waste Hours
A few patterns show up again and again.
The first is mixing runners inside one prefix. Installing a game with one Wine version and then switching runners mid-stream can leave libraries in an inconsistent state. Pick a runner, test, then change deliberately.
The second is ignoring logs. Every one of these tools surfaces launch output somewhere, and the error message almost always names the missing piece. Reading it beats reinstalling.
The third is treating a working setup as permanent. Runner updates can break games that ran fine last month. Keeping one known-good configuration per game, and noting the version, turns a crisis into a two-minute rollback.
The fourth is forgetting about save locations. Wine prefixes hide saves in unexpected folders, and a prefix reset can wipe progress. Back up before you experiment, every time.
Conclusion
Heroic, Lutris, and Bottles are not rivals fighting for the same slot. They answer three different questions. Heroic asks which store your games came from. Lutris asks which game you want to run and whether someone already solved it. Bottles asks which environment you want to build and keep. Once you see those questions clearly, the “which one is best” debate dissolves, and you can pick the tool that matches the way you actually manage a library. Start with one, learn its file layout, and add a second only when a real gap appears. That approach beats any launcher comparison table.
Frequently Asked Questions
Do Heroic, Lutris, and Bottles all use Wine?
Yes. All three depend on Wine or Proton to run Windows software, plus DXVK or VKD3D for graphics translation. The launchers manage those components; they do not replace them.
Can I use Heroic and Lutris at the same time?
Absolutely. They store games separately, so installing the same title in both is possible, though it wastes disk space. Many users split their libraries by convenience.
Why can’t Bottles see my second drive?
Bottles usually runs as a Flatpak, which sandboxes filesystem access. You need to grant permission to the extra drive through your system’s Flatpak settings before the launcher can browse it. (Flatpak documentation: Introduction)
Is Lutris still worth using in 2027?
For mixed libraries and older titles, yes. Its install script catalog remains its strongest asset, though script quality varies and some entries go stale. Check recent comments before relying on one.
Which launcher is easiest for beginners?
Heroic is generally the simplest for store-owned games: log in, install, play. Bottles and Lutris reward patience with more control but ask more questions upfront.
Do I need to reinstall games when switching launchers?
Usually yes, because each launcher creates its own prefix and file layout. Save files can often be copied across, but the game installation itself typically has to be redone.
The FAQ entries above cover the questions that come up most often in support threads, but they also hint at a deeper point: the workflow you choose shapes what you learn. A Heroic user becomes fluent in store authentication and cloud saves. A Lutris user learns to read YAML scripts and diagnose prefix failures. A Bottles user understands Wine components and Flatpak permissions. None of these skills is wasted, and each one transfers partially to the others.
That is why the “best launcher” question never resolves cleanly. The tools are stable enough in 2027 that the deciding factor is almost always habit, not capability. If you already have a library split across stores, Heroic removes friction you would otherwise fight every session. If your collection predates digital storefronts, Lutris remains the only realistic bridge. If you treat Windows software as something to be contained rather than absorbed, Bottles is the honest answer.
Pick the workflow that matches how you already organize files, saves, and notes. Then document it, back it up, and stop reinstalling things that were never broken.
