How to Play DayZ on Linux
with Mods
DayZ runs on Linux through Steam's Proton. The hard part has always been modded community servers — DZSA and launchZ are Windows-only. DayZ Beans Launcher runs natively on Linux and handles the mods for you.
Before you start
Steam with DayZ installed
Native Steam or the Flatpak (com.valvesoftware.Steam) both work. Tested distributions include Ubuntu 20.04+, Debian 11+ and Fedora 35+.
Proton enabled for DayZ
In Steam, turn on Steam Play (Proton) for DayZ — globally under Settings → Compatibility, or per game under DayZ → Properties → Compatibility.
Start DayZ once from Steam
Launch DayZ from your Steam library once and get to the main menu. This creates the Proton prefix the game needs. If DayZ doesn't start from Steam on its own, no launcher can fix it — sort that out first.
Install DayZ Beans Launcher
Download the Linux AppImage from the download page, then make it executable and run it:
chmod +x DayZ-Beans-Launcher-*.AppImage
./DayZ-Beans-Launcher-*.AppImageIf Steam isn't running, the launcher starts it in the background. Updates install themselves: the AppImage downloads the new version, checks its checksum and replaces itself. Every download is also checksummed and signed — see the download page for how to verify it.
What happens when you join a server
Mods download through Steam
The launcher subscribes to the server's Workshop mods through Steam, exactly like clicking Subscribe on the Workshop page. Nothing is downloaded from anywhere else.
Mods are linked into DayZ
Each mod gets a symlink named @<workshop id> in your DayZ folder, pointing at Steam's Workshop copy — the same approach as dayz-ctl and DZTUI. No duplicate copies, and broken links are cleaned up at startup.
DayZ starts through Steam
The launcher checks every mod is present and up to date, then asks Steam to start DayZ (steam -applaunch 221100) with the server address and mod list. Steam runs it under Proton.
The launcher closes itself
About two seconds after DayZ starts, the launcher exits so Steam can track the game normally. That's expected, not a crash.
Using Flatpak Steam
Flatpak Steam is sandboxed, so the launcher has to run through Steam as a non-Steam game. The Flatpak runtime has no FUSE, so you run the extracted AppImage instead of the file itself. The launcher detects Flatpak Steam and shows these steps in Settings too.
Extract the AppImage
chmod +x DayZ-Beans-Launcher-*.AppImage
./DayZ-Beans-Launcher-*.AppImage --appimage-extractThis creates a squashfs-root/ folder next to the AppImage.
Let Steam see the folder
If the launcher lives outside Steam's sandbox, grant access once, then restart Steam:
flatpak override --user --filesystem=home com.valvesoftware.SteamAdd it to Steam
Library → Add a Game → Add a Non-Steam Game → Browse (filter "All Files") and pick squashfs-root/dayz-beans-launcher — not the .AppImage.
Set the launch options
Right-click the new entry → Properties → Launch Options, using your own path:
LD_LIBRARY_PATH="/path/to/squashfs-root:$LD_LIBRARY_PATH" %command% --no-sandboxAlways start the launcher from Steam. Re-run step 1 after each launcher update — the extracted folder is a snapshot.
Troubleshooting
"Steam not running" with Flatpak Steam
You started the launcher outside Steam. Start it from its non-Steam game entry so the Steam environment is injected.
The launcher won't start the game
It refuses to launch while a mod is still downloading, out of date, or failed to subscribe. Let downloads finish, then try again.
DayZ opens, then nothing
Start DayZ directly from Steam. If it fails there too, the problem is Proton or the game install — try a different Proton version in DayZ's Compatibility settings.
Crash on NVIDIA + Wayland
Handled for you: on Linux the launcher runs under XWayland with the GPU sandbox disabled, which avoids a known Electron crash.
Ready to play DayZ on Linux?
Free. No account required. Your Workshop mods stay where they are.