Lutris
Lutris 0.5.22 is an open-source Linux game manager for native games, emulators, compatibility layers and connected libraries, with community installers for configuring runners.
What Lutris does
Lutris organizes native games, emulators, compatibility layers and several game-library sources in one client. A game entry combines an executable, working directory, runner, prefix and optional launch parameters; it does not guarantee that every title or online service is compatible.
Platform and library boundaries
Version 0.5.22 targets current Linux systems and can be used on Steam Deck in desktop mode. Windows and macOS are not the official desktop targets for this package. Connected services mainly provide library information and installation entry points, while tokens and the local game database remain sensitive.
Community installer scripts
Community scripts can download files, create prefixes and execute setup actions. Review their source, maintenance date, download targets, requested permissions and resulting paths before running them. Test in a separate directory with an ordinary user account.
Backups and migration
The pga.db database, configuration directory, runners, Wine prefixes and game saves form separate parts of a working setup. Back up the required parts together and verify paths on the new machine before deleting the old environment.
Maintenance note
Review date: 2026-08-23. The page was checked against Lutris 0.5.22, Linux and Steam Deck support, runner configuration, library tokens, community scripts and migration boundaries.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Lutris to this cloud drive
Baidu Netdisk
Save Lutris to this cloud drive
Lutris installation, script review and runner configuration guide
Install Lutris on Linux or Steam Deck desktop mode, add a local game, review a community script, configure a Wine runner and back up the database before migration.
Before you start
- Use a maintained Linux distribution, current graphics drivers, Vulkan components, Wine packages and system updates.
- Prepare games acquired through permitted channels and keep their files in a dedicated directory.
- Back up saves, Wine prefixes, runners and the Lutris database before upgrades or moving an installation.
Installation steps
- 01
Choose a distribution package or Flatpak
Prefer the current distribution repository, a verified DEB or Flatpak. A source checkout requires the complete Python, GTK and system dependency set and is better treated as a development setup.
- 02
Check drivers and runner paths
Launch Lutris and confirm graphics, Vulkan and required 32-bit components, then place games and runners on stable storage. Check sandbox access when using Flatpak with external directories.
- 03
Connect only the libraries you use
Add a service only when needed, complete its sign-in and inspect the synchronized library. Keep tokens, configuration files and pga.db out of public archives.
Quick start
- 01
Add a native local game
Create an entry from a local executable, set its working directory and architecture, and verify launch, exit and save paths before adding a more complex compatibility layer.
- 02
Review a community installer
Read the script description, download sources, target paths and maintenance date. Avoid scripts that request root, disable security controls or fetch unverified binaries.
- 03
Configure and record a Wine runner
Select an installed Wine version and keep the default prefix as a baseline. Change one DXVK, environment or launch option at a time and record the result.
Usage tips
- Lutris manages entries, runners and configuration; it does not guarantee game licensing, online service support or anti-cheat compatibility.
- pga.db stores library and installation state, while the configuration directory includes runner and game settings. Migrate them as a documented set.
- A script that worked once can later change because its source or dependency changed. Keep a copy of important installers and notes.
Troubleshooting and uninstall
Why does a game exit immediately after launch?
Review the game log, working directory, architecture, runner, missing libraries and graphics driver. Restore baseline options and change one variable at a time.
Why can Flatpak not see an external game directory?
Check that the mount is stable and grant access to that specific directory. Avoid exposing the whole home directory when only a game library is needed.
- Back up database, configuration and savesExit games and Lutris, copy pga.db, game configuration, runner records, Wine prefixes and independent saves, then inspect the paths in the backup.
- Separate the client from game filesUninstall Lutris while keeping games, runners and caches only when another tool still needs them; revoke unused connected-service sessions separately.
Frequently asked questions
Can Lutris be installed on Windows or macOS?
This client targets current Linux systems and Steam Deck desktop mode. Windows and macOS are not the official targets for this package, so similarly named unofficial ports need separate verification.
Are community installer scripts safe to run without review?
Review is essential because a script can download files, create prefixes and execute commands. Check its source, permissions, target paths and maintenance state, then test it in an isolated directory.
Does linking Steam or GOG upload my local games?
Linking normally synchronizes library information and installation entry points. The local client still stores tokens and a game database, so never publish its configuration or logs.