Lutris Setup Guide: Running Non-Steam Games on Linux

To run non-Steam games on Linux with Lutris, install Lutris from your distribution’s package manager or Flatpak, make sure your graphics driver and Vulkan support work, then add each game by using a community install script or by creating a manual entry with the Wine runner. Lutris keeps a separate Wine environment (a prefix) for each game, so one broken setup does not affect the others.

That one-paragraph answer hides the details that decide whether a game launches or fails, so this guide walks through the setup in the order that saves time in 2026: prerequisites, runners, installing a game, tuning performance and fixing common problems. Menu names and runner options change between versions, so check the current Lutris documentation if something here looks different on your screen.

What Lutris Does and When to Use It

Lutris is a game launcher that wraps tools such as Wine, DXVK and emulators into one interface. It is useful for games from stores that Steam does not cover, for older Windows titles, and for keeping several launchers organized in one library.

Lutris or Steam with Proton?

If a game is on Steam, Proton inside Steam is usually the simpler path. Lutris becomes the better choice for games bought elsewhere, for installers you downloaded yourself and for launchers that Steam does not manage. Many players use both.

Lutris or a dedicated store launcher?

Some store-specific launchers exist for particular libraries and can be simpler for those stores alone. Lutris is more flexible when you want one place for everything, though it asks for a bit more configuration.

Prerequisites Before You Install a Game

Most Lutris failures come from missing basics rather than from the game. Check these before blaming the installer.

Graphics drivers and Vulkan

Modern Windows games on Linux rely on Vulkan through translation layers. Install the current open-source driver stack for AMD and Intel, or the proprietary driver for Nvidia, and confirm that Vulkan works with a tool such as the vulkaninfo command. Your distribution’s documentation explains the correct packages.

32-bit libraries

Some distributions require 32-bit graphics libraries for Wine and older games. If a game opens a window and closes immediately, missing 32-bit support is a common cause. Your distribution’s wiki will list the packages to install.

Wine dependencies

Lutris includes a Wine build of its own, but other libraries may be needed for codecs and fonts. If you see error messages about missing libraries, read them carefully and install the packages named.

Installing a Game Step by Step

Search for an install script

Open Lutris and search for the game. Many titles have a community install script that selects a runner, downloads required components and sets options. Read the script description and recent comments, since an outdated script may need changes.

Choose a runner and install location

Scripts normally pick the runner for you, usually a Wine build, and ask where to put the game. Install on a drive with plenty of space, and avoid placing the prefix on a slow external disk.

Run the installer and finish setup

Follow the installer’s prompts. After the installer exits, Lutris adds the game to your library. Right-click the entry and open its configuration to check the executable, Wine version and prefix.

Manual Setup for Games Without a Script

If no script exists, add the game by using “Add game” and choosing the Wine runner. Point it to the executable, set a new prefix, and pick a recent Wine or Proton-based runner from the options. Lutris can download several runners; a build that is patched for games often works better than plain upstream Wine, but check which runners your Lutris version currently offers.

In the runner options, turn on DXVK for DirectX 9, 10 and 11 games, and VKD3D for DirectX 12 titles. These layers translate Windows graphics calls to Vulkan and are central to good performance. Enable the game-mode and overlay tools if installed, then launch and read the log if the game fails.

Performance and Compatibility Tuning

Keep a note of each change you make, and change only one setting at a time. That habit makes it easy to undo a bad guess, and it saves hours when a game has several possible causes.

Keeping Lutris Healthy Over Time

Update runners and Lutris itself

New Wine and Proton-based builds fix many game bugs. Update Lutris regularly, and keep a previous runner version in case a new one breaks a game that worked before.

One prefix per game

Separate prefixes prevent changes made for one game from breaking another. They use more disk space, but they make troubleshooting cleaner. Back up the prefix of any game you have spent time configuring.

Check the community

Compatibility databases and forums list known working settings for particular games. Review recent reports before you spend time on a title with known anti-cheat problems or kernel-level protection.

Reading Logs and Debugging a Stubborn Game

When a game fails to start, the log tells you more than guesswork. Lutris can show a log window when you launch a game, and the output usually names the missing file, library or graphics call that caused the failure. Copy the first error message rather than the last, since later lines are often side effects of the first problem.

Turn on the debug output

In the game’s configuration, enable the option that shows the runner’s output or writes a log file. Run the game again, let it fail and read what appears. Search for the exact message together with the game’s name, and look at recent reports, because a fix that worked for an older Wine version may no longer apply.

Isolate one variable at a time

Switch the runner version, then the translation layer, then the launch options, but never all at once. Keep the settings that work and write down what changed. If the game worked in a previous runner version, roll back and wait for a later update instead of fighting the new one.

Use overlays and helpers carefully

Performance overlays, game-mode helpers and frame limiters are useful, but they can also be the cause of a crash. Turn them off when you troubleshoot, then add them back after the game runs. This is especially true for games with their own launcher or anti-tamper checks.

If a game still refuses to run after a few reasonable attempts, check whether the developer states Linux support for it. Some titles depend on protections that Wine-based layers cannot run, and no setting will change that. In those cases, a cloud streaming service or a dual-boot setup may be the practical answer.

Common Mistakes

• Skipping Vulkan and driver checks, then blaming Lutris for failures that come from the graphics stack
• Reusing one prefix for many games, so a single change breaks several libraries
• Installing an old community script without reading recent comments and updating the runner
• Changing many options at once, which makes it impossible to see what fixed or broke the game
• Expecting games with kernel-level anti-cheat to work without checking the developer’s Linux support

Before You Start Checklist

• Confirm your graphics driver and Vulkan support work
• Install Lutris from your distribution or Flatpak and update it
• Look up the game on a compatibility database first
• Pick a drive with enough space for the prefix and game files
• Save logs and notes for each game you configure

Related guides

• Aio Liquid Coolers For High Performance Gaming
• Wireless Gaming Headsets Under 100 For Pc
• Ssds For Large Video And Raw Photo Files

Frequently Asked Questions

Is Lutris free?

Yes, Lutris is open-source software that you can install without a license fee. Games you add to it still need to be purchased from their stores.

Can Lutris run Epic or GOG games?

Often, yes. Lutris can integrate with several stores, and community scripts exist for many launchers. Support for specific stores changes over time, so check the current options in your version.

Should I use Wine or Proton in Lutris?

Proton-based builds tend to include extra patches for games, while plain Wine suits many older titles and applications. Try the runner suggested in the install script first, then test another if the game misbehaves.

Why does my game stutter at first launch?

This is often shader compilation, where the game builds graphics code the first time it needs it. It usually improves after a short session, but check game-specific notes if the stutter continues.