Run the experimental Linux AppImage.

Check the Linux prerequisites

The AppImage requires x86-64 Linux, glibc 2.39 or newer, an AVX-capable CPU, Vulkan 1.3 and your own compatible PS4 Remastered files. It uses the same community runtime and launcher as the Windows project.

The release notes list AppImage smoke tests on Debian 13, Arch Linux, Fedora 42, Ubuntu 24.04 and openSUSE Tumbleweed. These checks cover packaging and launcher startup. They do not establish that a full playthrough works on every GPU or distribution.

If you are unsure about your glibc version, ldd --version reports it on typical glibc systems. Check the installed graphics driver separately.

Download and run

1. Open the project release and choose gow3-x86_64.AppImage.
2. Download the matching gow3-x86_64.AppImage.sha256 file from that same release. In a terminal in the download folder, check the package:

sha256sum -c gow3-x86_64.AppImage.sha256

The result should name gow3-x86_64.AppImage and say OK. If the check fails, confirm that both files came from the same release and download them again. Do not use a checksum from an older version. This compares the downloaded bytes with the maintainer’s checksum; it does not establish that the software is safe.

3. Mark the verified file executable and launch it:

chmod +x gow3-x86_64.AppImage
./gow3-x86_64.AppImage

4. Choose the folder containing your own eboot.bin, sce_module and sce_sys.
5. If your game update is in a separate directory, choose it under Game → Update folder.
6. Save your chosen settings, then press PLAY.

The GNU checksum documentation explains the check option. The package and checksum filenames come from the 2.4.1 release assets.

An old AppImage can report GLIBC_2.44 not found. The maintainer rebuilt the AppImage for glibc 2.39; check that you downloaded the intended rebuilt package. A system older than the documented requirement is still outside that requirement.

Steam Deck and SteamOS

The AppImage is a native Linux application. If Steam tries to start it through Proton, the release README directs you to the shortcut’s Properties → Compatibility and Steam Linux Runtime.

That setting resolves a launch-method mismatch; it is not a guarantee that rendering and gameplay are fully compatible. The 2.4.0 known-issues list, carried into 2.4.1, includes some Steam Deck startup failures after the Steam client update of 15 October 2026.

For a Deck failure, record the SteamOS version, project release and exact stage where startup stops. Check current upstream issues before applying advice written for an older build.

Add a Steam shortcut

The launcher offers Advanced → Add to Steam. Close Steam before using it because Steam rewrites shortcut data when it exits. The project creates library artwork from pictures in your own game dump; this site supplies none of those files.

After adding the shortcut, reopen Steam and check which runtime it uses. Keep the original AppImage path stable so the shortcut continues to point at the file you intended.

Saves, settings and updates

The Windows in-launcher updater is unavailable on Linux. Download a newer AppImage from the maintainer’s release page when updating, and back up saves first.

Advanced → Linux includes window-system selection, GameMode and MangoHud options. Only tools already installed on your system can be enabled. If an option creates a problem, restore the prior setting and compare the log before changing another variable.

If startup or rendering fails

Use the troubleshooting guide to distinguish missing system libraries, CPU instruction errors, a failed game image and a GPU problem. Include the AppImage version and the exact error when filing a report. A vague “does not work on Linux” report gives the maintainer too little to reproduce.