How to play Final Fantasy 14 Online on Linux

Before you begin: pick the right path (Steam vs. non-Steam)

The first decision is less “Do you like cats or dogs?” and more “Do you like your account to actually log in?”
FFXIV licenses generally fall into a few buckets:

• Steam license: You own FFXIV through Steam. You typically launch via Steam (usually with Proton).
• Windows (non-Steam) license: You bought it from Square Enix or another retailer. You can use XIVLauncher or Lutris/Wine.
• Free Trial: Works too, but the launcher can be finicky depending on method.

Most headaches come from mixing Steam and non-Steam expectations. Be honest with yourself (and your Mog Station account) about what you own,
then choose one of the setups below.

Option A: Play FFXIV on Linux using Steam Proton (the “easy button”)

If you have the Steam version, this is usually the smoothest route. Proton is Valve’s Windows-compatibility layer built into Steam,
designed to run Windows games on Linux with minimal fuss. For FFXIV, Proton often “just works,” with occasional launcher quirks.

What you need

• Steam installed on Linux
• Updated GPU drivers (Mesa for AMD/Intel; proprietary driver for NVIDIA)
• A little patience the first time shaders compile (your fans may briefly audition for a jet engine)

Step-by-step setup

1. Enable Steam Play (Proton):
   • Open Steam → Settings → Compatibility (or Steam Play, depending on client version).
   • Enable Steam Play for supported titles (and optionally “for all other titles”).
2. Install FINAL FANTASY XIV Online from your Steam library.
3. Choose a Proton version:
   • Right-click FFXIV → Properties → Compatibility.
   • Check “Force the use of a specific Steam Play compatibility tool.”
   • Select Proton Experimental if you want the freshest fixes. If that’s unstable, try a stable Proton release.
4. Launch and log in. The first launch can take longer while Proton sets up its prefix (Windows-like folder environment).

Common Proton gotchas (and fixes that don’t involve screaming)

• Launcher weirdness or blank windows:
  • Try a different Proton version (Experimental ↔ stable).
  • Disable Steam overlay temporarily if the launcher behaves like it just saw a ghost.
  • If the embedded browser is the problem, some players use “old launcher” settings via config edits (varies by patch and setup).
• Movies/cutscenes don’t play or hang:
  • This can happen depending on video playback components. Switching Proton versions often resolves it.
  • As a workaround, you can skip the opening movie in-game settings if it’s consistently problematic.
• Slow patching / heavy disk usage:
  • FFXIV patches can be I/O-heavy. Using an SSD helps a lot.
  • Make sure your Steam library is on a Linux-native filesystem (see the storage section below).

Steam Deck notes

Steam Deck is basically Linux gaming’s victory lap. FFXIV is playable on Deck with Proton, but text/UI can be small and you may want
controller-friendly hotbars and UI scaling. If you’re docking, a keyboard/mouse setup feels much closer to the “real” MMO experience.

Option B: XIVLauncher on Linux (best for non-Steam, great quality-of-life)

XIVLauncher is a popular community launcher that aims to make installing, patching, and running FFXIV easierespecially on Linux.
It commonly ships with a tuned Wine setup and can reduce the “why is the official launcher like this” moments.

Quick, important disclaimer: XIVLauncher is third-party software. Many players use it, but you’re still responsible for your account
and for following Square Enix’s terms. Also: plugins exist. Some are harmless quality-of-life; others are… let’s say “morally complicated.”
If you like staying unbanned, keep it clean.

Install XIVLauncher via Flatpak (simple and distro-friendly)

Flatpak is popular because it bundles dependencies and keeps your system cleaner. The quick idea looks like this:

• Install Flatpak (if your distro doesn’t ship it by default).
• Enable Flathub.
• Install the XIVLauncher Flatpak.

Once installed, open XIVLauncher, sign in, and point it to your game files (or let it download/install them). This route is especially friendly
for non-Steam Windows licenses.

Steam account with XIVLauncher: the “compatibility tool” approach

If you own FFXIV through Steam, XIVLauncher can still be used, but the cleanest approach is usually integrating it with Steam as a compatibility tool.
In plain English: Steam launches FFXIV, but the compatibility tool swaps the official launcher step with XIVLauncher in a way that plays nicer with Steam’s setup.

Practically, this means:

1. Install the compatibility tool method (commonly referred to as XLCore/XLM in community guides).
2. In Steam, force the game to use that compatibility tool (similar to forcing Proton).
3. Launch from Steam; XIVLauncher handles patching/login from there.

Why do this? Because Flatpak sandboxing and Steam integration can fight each other like two Lalafells in a single doorway.
The compatibility tool method is designed to reduce that friction.

Why people like XIVLauncher (even if they won’t admit it at parties)

• Smoother patching/login flow for many Linux setups
• Better control over Wine configuration without hand-editing arcane files
• Quality-of-life options (use responsibly)

Option C: Lutris (for tinkerers who want knobs, dials, and levers)

Lutris is a Linux gaming manager that can install and run Windows games using Wine, DXVK, and community scripts.
For FFXIV, Lutris can work wellespecially if you like controlling your Wine version, toggling DXVK/VKD3D, and tweaking launch parameters.

When Lutris is a good idea

• You don’t use Steam for FFXIV and want a dedicated launcher environment
• You need to experiment with Wine builds for a specific launcher issue
• You enjoy the feeling of “I fixed it” more than the feeling of “I played the game” (no judgment)

What’s happening under the hood

Most Lutris install scripts for Windows games set up:

• Wine (Windows API compatibility)
• DXVK (DirectX 9/10/11 to Vulkan translation)
• VKD3D (DirectX 12 translation, if needed)
• Optional toggles like esync/fsync (performance-related synchronization tweaks)

If you go this route, focus on stability first: use known-good Wine builds, keep DXVK enabled, and only tweak one variable at a time when troubleshooting.
Otherwise you’ll end up with the classic Linux gaming mystery: “I changed four things and now it works. I have no idea why.”

Performance tips for FFXIV on Linux (a.k.a. keep your FPS out of the basement)

1) Use Vulkan-friendly drivers and keep them current

FFXIV under Proton/Wine typically benefits from Vulkan translation (via DXVK), so your Vulkan stack matters:
Mesa updates help AMD/Intel; NVIDIA users usually want a recent proprietary driver. If your GPU driver is ancient,
the game might still run… with the enthusiasm of a chocobo carrying eight retainers’ worth of furniture.

2) Expect shader compilation the first time

The first session (or after major updates) can include stutters while shaders compile. This often improves after a few zones, duties, or dungeon pulls.
It’s normalannoying, but normal.

3) Consider GameMode (easy performance boost on some systems)

GameMode can temporarily change CPU governor and apply gaming-focused tweaks while you play.
If you use Steam, you can sometimes add it as a launch helper (exact setup varies by distro).

4) Don’t install your Steam library on NTFS if you can avoid it

This one trips people up: Proton and Steam often rely on filesystem behaviors that are happiest on Linux-native filesystems (ext4, btrfs, xfs).
NTFS drives (common in dual-boot setups) can cause odd issuesespecially with symbolic links and permissions.
If you can, keep FFXIV on a Linux-native partition. Your future self will send you a thank-you card.

5) Use in-game settings like a grown-up (not everything must be “Maximum”)

FFXIV is generally well-optimized, but big cities and alliance raids can still bully your CPU.
Practical tweaks:

• Lower shadows a notch (high impact, decent gain)
• Reduce ambient occlusion if you’re GPU-limited
• Cap FPS to keep frame pacing smooth and reduce heat/noise
• Use UI scaling and font size so you’re not squinting like you’re reading an ancient Allagan tablet

Troubleshooting checklist (fast fixes before the panic spiral)

When something breaks, don’t reinstall your entire operating system. (Yes, people do that. No, it’s not necessary.)
Try these in order:

Steam Proton troubleshooting

• Switch Proton version (Experimental ↔ stable). This solves an unreasonable number of problems.
• Verify game files in Steam.
• Disable overlays temporarily (Steam overlay, Discord overlay, etc.).
• Move the install to a Linux-native filesystem if you’re on NTFS.
• Clear shader cache only if you’re diagnosing a major issue (it can cause more stutter next launch).

XIVLauncher troubleshooting

• Check permissions if using Flatpak (sandbox rules can block access to game folders).
• Point to the correct game directory (especially if you already have the files downloaded elsewhere).
• Patch day issues: community launchers sometimes need updates after major patches. Update the launcher first.
• Avoid risky plugins. If you’re diagnosing crashes, disable all plugins and test vanilla.

Lutris troubleshooting

• Try another Wine build (Lutris-managed Wine versions can behave differently).
• DXVK on unless you have a very specific reason to turn it off.
• One change at a time. Lutris makes it easy to change everythingdon’t.

“It launches, but it’s cursed” symptoms

• Audio issues: check your system audio backend (PipeWire/PulseAudio), and test with another game to isolate the issue.
• Controller weirdness: Steam Input can help, but it can also double-map buttons. Try enabling/disabling Steam Input per game.
• Login loops: confirm you’re using the correct account type (Steam vs non-Steam) and the correct launcher method for that license.

FAQ: the questions everyone asks (usually after something explodes)

Is FFXIV officially supported on Linux?

No. You’re relying on compatibility layers and community tools. That said, many people play successfully on Linux and Steam Deck.

Will I get banned for playing on Linux?

Playing via Proton is generally just running the Windows game in a compatibility environment, not a cheat tool.
Still, Square Enix doesn’t officially endorse Linux clients, and third-party launchers/plugins always carry some risk.
If you want the safest approach: use Steam + Proton, avoid shady add-ons, and keep your setup clean.

Which is better: Proton or XIVLauncher?

If you own the Steam version, start with Steam Proton. If you’re non-Steam or want extra quality-of-life around patching,
XIVLauncher is often the community favorite. Lutris is great if you enjoy fine-grained control.

What about updates breaking things?

It happens. When it does, the best first move is usually switching Proton versions (for Steam) or updating XIVLauncher (for community launcher users).
Big patch days can cause short-term hiccupstry not to take it personally. The patch is not out to get you. Probably.

Conclusion

Playing Final Fantasy XIV Online on Linux isn’t a novelty anymoreit’s a practical setup thanks to Proton, improved Vulkan tooling,
and community projects like XIVLauncher. The key is choosing the right path for your license type:
Steam + Proton for the smoothest start, XIVLauncher for a powerful alternative (especially non-Steam),
and Lutris if you want full control over Wine and translation layers.

Once you’re in, the experience can be excellent: solid performance, reliable gameplay, and the smug satisfaction of clearing content on an OS that
some people still think “can’t game.” (Tell that to your raid parse.)

Extra: of “real-world” experiences and tips (from the Linux gaming trenches)

If you’ve never played an MMO on Linux before, your first few hours can feel like a small cultural exchange program between Eorzea and your desktop.
Here are the most common experiences Linux players reportand how to make them work in your favor.

First launch jitters are normal. The game may take longer to start the first time because Proton (or Wine) is building a Windows-like
environment behind the scenes. This can look like “nothing is happening” when something is happeningquietly, in the background, like a Ninja using
Shukuchi to reposition your files.

Patching day can be spicy. FFXIV patches are big, frequent, and occasionally launcher-breaking.
The most common success pattern is hilariously low-tech: update Steam, switch to Proton Experimental, reboot, try again.
For XIVLauncher users, updating the Flatpak or compatibility tool setup usually fixes things quickly once the project pushes a release.
The moral: don’t schedule your Linux migration on expansion launch week unless you thrive under pressure.

Where you install the game matters more than people expect. Lots of dual-boot folks try to keep one giant NTFS “Games” drive shared
between Windows and Linux. It’s a great idea in theory and a recurring source of Proton heartbreak in practice. Linux-native filesystems avoid weird
permission issues, symbolic link problems, and mysterious “why is this folder acting haunted” moments.
If you want the “set it and forget it” vibe, install FFXIV to a Linux-native partition and let Windows fend for itself.

Performance tuning is mostly about consistency, not max numbers. Many players chase the highest FPS, then wonder why their machine
sounds like it’s preparing for orbital launch in Limsa Lominsa. A smarter approach is capping FPS to a stable value (like 60),
lowering a couple of heavy settings (shadows, AO), and enjoying smooth frame pacing.
The game feels better, your system runs cooler, and your household pets stop judging you.

Controller setups can be amazingafter one awkward hour. On Linux, Steam Input is a blessing and a prank depending on the day.
If buttons double-trigger or menus freak out, try toggling Steam Input per game, then retest.
Once it’s dialed in, FFXIV’s controller support is genuinely strong, especially for casual play, crafting, gathering, or lounging on a couch like a
victorious catboy with a mechanical keyboard in the distance.

Finally: write down what you changed. Linux gaming is powerful because it’s configurable… and dangerous because it’s configurable.
If you switch Proton versions, add launch flags, toggle DXVK, and change audio backends all in one night, you’ll eventually reach the classic state:
“It works. I am afraid to touch it.” Keep a tiny notes file with changes. Your future self will thank you when the next patch arrives.