Account
Confirm the Steam or standalone license and use the matching login route. Keep one-time-password details private and never paste account secrets into a public support thread.
Linux platform guide
FFXIV Linux Guide: Install XIVLauncher Safely
This FFXIV Linux guide explains the safe XIVLauncher route instead of downloading the Windows installer and guessing through compatibility layers. It covers account checks, setup steps, and troubleshooting.
Quick answer: use the Linux-specific XIVLauncher path
If you want to play FFXIV on Linux, start with the maintained official XIVLauncher Linux instructions. Do not treat XIVLauncher-win-Setup.exe as the normal desktop Linux installer, and do not mix a Windows tutorial with a Steam Deck tutorial unless you understand which step is platform-specific.
The order is: confirm your FFXIV account and license, read the current Linux guide, install the launcher through the recommended path, launch the base game once, and only then add Dalamud or plugins. That gives you a clean baseline when an update or plugin causes trouble.
A platform boundary worth checking
FFXIV Linux setup is a workflow, not a single download
Searches for ffxiv linux often combine several questions: whether the game can run, whether XIVLauncher works, whether Steam or a standalone account is required, and where Dalamud belongs. A useful guide must separate those questions instead of promising that one command fixes every distribution.
Linux gaming changes at more than one layer. Your distribution, graphics driver, Proton or Wine components, game installation, launcher configuration, and plugins can each fail independently. Keeping those boundaries visible is more useful than copying an old command.
Return to the official guide when a game update changes the supported route.
Which FFXIV Linux setup path matches your device?
| Setup | Start with | What to verify | Avoid |
|---|---|---|---|
| Desktop Linux | The official Linux/XIVLauncher guide | Distribution instructions, graphics stack, game path, and login flow | Using a Windows installer as the only plan |
| Steam Deck | The official Steam Deck section | Steam account ownership, storage location, controller flow, and desktop-mode steps | Copying desktop commands without checking the Deck workflow |
| Standalone FFXIV account | The account path supported by the current guide | Your license and launcher login match the installed game | Assuming a Steam license and standalone license are interchangeable |
| Steam FFXIV account | The Steam-aware setup path | The game is installed and launched through the expected Steam context | Moving files before confirming the account boundary |
| Plugin-enabled setup | A clean base-game launch first | Dalamud and plugins are added only after the launcher works | Blaming Linux for a plugin-only failure |
How to install XIVLauncher on Linux safely
- 1. Confirm the account boundary. Before changing files, decide whether you use a Steam or standalone FFXIV account and where the game is installed. The launcher can be working correctly while the account or game path is wrong, so write down the path you intend to use.
- 2. Read the current official Linux instructions. Open the maintained project guide before installing packages or copying commands. Linux support details can change with launcher releases, game patches, Proton or Wine changes, and distribution packaging. Treat older forum posts as background, not as the source of truth.
- 3. Choose the path for your device. Desktop Linux and Steam Deck share the Linux platform but not always the same interface or storage steps. Follow the device-specific section instead of combining commands from two paths.
- 4. Install the launcher from the supported source. Use the official project route and inspect what you are running before granting permissions. Avoid unknown mirrors, repackaged executables, and commands that hide their source.
- 5. Point to the real game installation. When the launcher asks for the FFXIV location, select the existing installation rather than creating a second copy. Check the mount, Steam library, or compatibility prefix carefully.
- 6. Launch the base game before plugins. Sign in and test the game with the smallest supported configuration. Confirm that the launcher reaches the game and that the account can load the correct character or title screen. This clean test becomes your comparison point later.
- 7. Add Dalamud and plugins gradually. If your supported setup includes Dalamud, add it after the base path works. Enable only a small number of plugins at a time and record changes. When an update breaks the launch, you can then compare a clean run with a plugin-enabled run.
- 8. Keep a recovery note. Record the distribution, launcher route, game path, graphics driver, compatibility component, and last successful launch. This note is more useful than repeatedly reinstalling everything when asking for help.
Desktop Linux and Steam Deck are related, not identical
Keep the device-specific setup steps together
Steam Deck users normally need to think about desktop mode, Steam library locations, controller-friendly launch behavior, and how the game is added back to Steam. Desktop Linux users may instead need distribution packages, a desktop shortcut, graphics-driver checks, or a manually selected game prefix. The shared keyword is Linux; the practical path is not identical.
If you switch between Steam and standalone service accounts, do not use the same account assumptions for both. A launcher can open successfully and still reject the login or show the wrong installation because the license context does not match the game files.
The safest setup is reversible. Keep the first launch clean, keep the original game directory intact, and change one variable at a time. That approach also makes it easier to decide whether a problem belongs on the Linux platform page, the general troubleshooting page, or the patch-download error guide.
What to check before you add plugins
A working Linux launcher is the baseline. These checks keep a platform question separate from a plugin question.
Game path
Verify the real library, mount, or prefix location. If the launcher cannot find the game, check the path before downloading a second copy or deleting configuration.
Plugins
Add optional components only after a clean launch. If a plugin causes the next failure, you have a clear comparison instead of a mixed diagnosis.
What to do when the FFXIV Linux setup stops working
Start with the last visible checkpoint. If the launcher does not open, inspect the launcher source, permissions, compatibility components, and recent package changes. If the launcher opens but cannot find the game, inspect the library path and mounted storage. If the game reaches a window and then closes, compare graphics drivers, overlays, and the selected compatibility layer.
If the problem began immediately after a game patch, test without optional plugins and check the current official project notes before deleting files. If the message specifically says that patch files cannot be downloaded, use the dedicated patch-file troubleshooting page; that is a network, storage, permissions, or service boundary rather than proof that Linux is unsupported.
Keep the first failed test reproducible. Note what changed and whether a clean launch works. Do not report private tokens, full account identifiers, or unredacted paths. A short redacted log and a precise failure layer are more useful than a generic screenshot.
Troubleshooting boundary
Find the first checkpoint that fails
A platform guide cannot promise that every Linux distribution behaves the same. It can, however, give you a reliable order: account and license, game location, launcher startup, game launch, then optional plugins. Each successful checkpoint narrows the next question.
If you change the launcher, graphics stack, game path, and plugin list at the same time, a later success does not tell you what fixed the problem. Make one controlled change, launch once, and record the result. This is slower than a blind reinstall but faster than losing the evidence you need.
When the current official guide changes, follow its newer instructions even if an older article or video uses different package names. This page explains the decision boundaries; it is not a replacement for the maintained project documentation.
Common FFXIV Linux mistakes to avoid
Most difficult Linux setup problems begin with a reasonable step applied to the wrong platform, account, or layer. Check these first.
- Do not treat the Windows XIVLauncher installer as the default desktop Linux path.
- Do not mix Steam and standalone account instructions without checking the license context.
- Do not move the game directory before confirming its real library or prefix location.
- Do not add a large plugin collection before the base game launches cleanly.
- Do not delete the launcher, game, or compatibility folders just because a forum post suggests it.
- Do not assume Steam Deck storage steps are identical to a desktop distribution.
- Do not publish private login or full filesystem details in support channels.
- Do not call a patch-download error proof that the entire Linux setup is unsupported.
Safety, support, and Terms of Service boundaries
XIVLauncher, Dalamud, and plugins are third-party tools. Compatibility can change after an FFXIV update, and this guide cannot promise account safety or uninterrupted service. Use official project sources, keep credentials private, and understand the rules for your account.
Use the Linux path only when it fits your device and needs.
Does FFXIV work on Linux?
FFXIV can be run on Linux through the maintained Linux setup path, but the exact steps depend on the distribution, device, account type, game location, and current compatibility guidance. Start with the official XIVLauncher Linux documentation.
Does XIVLauncher work on Linux?
The project documents a Linux route for XIVLauncher. Use that route instead of treating the Windows installer as the normal Linux setup, and check the current guide before copying older commands.
Is the Steam Deck setup the same as desktop Linux?
They share the Linux platform but are not identical workflows. Steam Deck adds desktop-mode, Steam library, controller, and storage checks, while desktop Linux can require distribution-specific packages or paths.
Can I use Steam and standalone FFXIV accounts interchangeably?
Do not assume they are interchangeable. Confirm which license and login context your game installation uses, then follow the matching launcher instructions.
Should I install Dalamud before testing the game?
No. Launch the base game first, confirm the clean path works, and add optional components gradually. That gives you a useful comparison if a plugin or game update causes a failure.
What should I do if patch files will not download on Linux?
First separate the patch-download symptom from the platform question. Check the current service status, storage, network, permissions, and security boundaries, then use the dedicated FFXIV patch-file troubleshooting guide rather than deleting the whole installation.