XIVLauncher Linux Installation Guide

XIVLauncher for Linux is distributed in many different formats depending on your system setup. Please read below for the recommended way to install XIVLauncher for your system:

Install XIVLauncher as a Steam compatibility tool

The XIVLauncher Steam compatibility tool is handled by a project called XLM. Automatic install scripts are provided for all major system configurations that will do most of the setup work for you (However if your system configuration is not covered here you can always manually download the XLM binary from the GitHub Releases Page and install that way). Regardless of how you install XLM from it will always be kept up to date automatically.

Run one of the following commands to install XLM as a Steam compatibility tool. What command you need to run depends on how you have Steam installed. These scripts CANNOT and SHOULD NOT be run with sudo or root permissions.

Steamdeck Install Script:

sh -c "$(curl -fsSL https://raw.githubusercontent.com/Blooym/xlm/main/setup/install-steamdeck.sh)"

Steam Install Script (Native)

sh -c "$(curl -fsSL https://raw.githubusercontent.com/Blooym/xlm/main/setup/install-native.sh)"

Steam Install Script (Flatpak)

sh -c "$(curl -fsSL https://raw.githubusercontent.com/Blooym/xlm/main/setup/install-flatpak.sh)"

Experimental

Steam (Snap) [Unsupported - may be broken on Wayland]

sh -c "$(curl -fsSL https://raw.githubusercontent.com/Blooym/xlm/main/setup/install-snap.sh)"

After the installer has finished, please follow these steps to use the compatibility tool:

Optional Advanced Features

Using a fork of XIVLauncher

To use a fork of XIVLauncher you can add the flags --xlcore-repo-owner and --xlcore-repo-name to the Steam “Launch Arguments” section.

Forks of XIVLauncher can also offer their own install scripts that automate this process for you so you don’t have to manually add these flags.

Pre + Post launch scripts (Advanced)

When installed as a Steam compatibility tool XLM supports running scripts before and after XIVLauncher has been ran. These scripts allow for extending the functionality of XLM or XIVLauncher. On startup, XLM will look for directories inside of the XLM compatibility tool folder named prelaunch.d and postlaunch.d and run all scripts contained inside. These scripts have to be placed manually after installing XLM and no support is offered if you create/use a script that breaks something.

Install XIVLauncher as a flatpak or system package

Flatpak

First, check to see if flathub is installed by running flatpak remotes. If you don’t see an entry for flathub, check https://flathub.org/setup for instructions on how to install it.

Via terminal

To install XIVLauncher as a flatpak using the terminal, run the command flatpak install flathub dev.goats.xivlauncher as a regular user ( without sudo).

Via your software store (GNOME/KDE)

Some desktop environments provide graphical frontends for Flatpak repositories, allowing you to browse an app store to install Flatpaks in a more intuitive way.

Other desktop environments may or may not have XIVLauncher available in their own Flatpak frontend applications. If XIVLauncher does not appear in GNOME Software or KDE Discover, verify that Flatpak is installed and running, and verify that you have the Flathub repos enabled.

Installing FFXIV to an external drive

If you would like to install Final Fantasy XIV to any folder outside of the default (~/.xlcore/ffxiv), you will also need Flatseal from the Discover Store.

Run Flatseal. On the left, scroll down to XIVLauncher. In the main part of the window, scroll down to Filesystem. Click the Folder icon next to Other files. Type the path where you would like to install Final Fantasy XIV.

System package

A list of alternative packages and formats can be found here. Please note that apart from the compatibility tool and the Flatpak, the rest are maintained by members of the community and are deemed unofficial. You will, however, still receieve community support as long as the package is up-to-date.

FREQUENTLY ASKED QUESTIONS

Q: Where are my configuration files kept?

Configuration files are saved to ~/.xlcore, except when running the compatibility tool with the Steam flatpak wherein the configuration files are saved to ~/.var/app/com.valvesoftware.Steam/.xlcore.

Q: The game is disappearing randomly and won’t resume after sleep mode on Steam Deck

Please make sure that FFXIV or the FFXIV Free Trial from the Steam Store is installed on your Steam Deck’s internal memory.

Q: My audio is crackling/distorted

Try adding PULSE_LATENCY_MSEC=60 in your XIVLauncher environment variable settings.

Q: I can’t control my game

Change the control layout for the game SteamOS thinks FFXIV is running as. For non-Steam service accounts, this means FINAL FANTASY XIV Online Free Trial.

If that does not fix it, rename ~/.xlcore/ffxivConfig/FFXIV.cfg to FFXIV.cfg.bak and run the game again from Gaming Mode. This will reset all Final Fantasy XIV System settings to default. Renaming FFXIV.cfg.bak back to FFXIV.cfg will restore these settings.

Q: Final Fantasy XIV doesn’t close properly / Steam constantly thinks Final Fantasy XIV is playing

Please switch to the compatibility tool version of XIVLauncher and remove the old XIVLauncher flatpak to resolve this problem.

Q: I can’t enter my username/password on Steam Deck

Due to a limitation of Steam’s text input API, please use the Steam Deck’s Gaming Mode to finish setup.

Q: I’m seeing “No secrets provider installed or configured”

This means that XIVLauncher was unable to find a secure way to store your passwords. This is usually because you don’t have a secrets manager like GNOME Keyring or KDE Wallet installed on your system. It’s recommended you install a recognised and well known secrets manager to solve this problem.

If you are using a Steamdeck or are unable to install a secrets manager, you can run XIVLauncher with XL_SECRET_PROVIDER=file to store your credentials insecurely via a file. This will be done for you if you are using the compatibility tool on Steamdeck or with Flatpak Steam.

Return to the top Return to the main FAQ