How to Use AnyPS5 on Windows and Linux

1. Check what you need before you start

AnyPS5 combines a relinker, which converts an executable into a native target format, with implementations of system libraries. Downloading the relinker alone does not supply the complete runtime layout.

• A Windows or Linux environment. Use the download pair for the operating system where you intend to run the output.
• A clean ELF executable and its bundled ELF modules. Renaming a container or encrypted file to .elf does not convert its contents.
• The game's resources. The relinker does not populate the resource directory for you.
• A separate workspace. Keep your original files and write converted output to a different path.

Check the documented compatibility results first. They describe specific tests, not a general hardware requirement or a guarantee for another game. This guide covers the published Windows/Linux release; it does not apply newer development options to v0.1.1.

2. Download a matching pair of release files

Open the original v0.1.1 release page. Choose one row below. The relinker and library archive are separate downloads; GitHub's source-code archives serve a different purpose.

Create a folder named anyps5-work and place your downloaded relinker inside it. Keep the library archive ready for step 6. Use a fresh workspace for a different target OS so its libraries and generated modules stay separate.

3. Prepare the input and bundled modules

Inside your workspace, create source/My Game. Place your input ELF there and use its actual filename in the commands. Our example calls it eboot.elf:

anyps5-work/
├── relinker-v0.1.1.exe       # Windows; relinker-v0.1.1 on Linux
└── source/
    └── My Game/
        ├── eboot.elf
        └── sce_module/
            └── <bundled ELF modules>

In v0.1.1, the module directory must be named sce_module or sce_modules and sit beside the input executable. Keep the name supplied with your input; use exactly one of the two directories. The converter examines files directly inside it.

An absent directory and both directory names being present are separate errors. Creating an empty folder does not establish that a game can work without its modules. The normal commands below preserve module processing.

4. Convert the executable on Windows

Open PowerShell in anyps5-work. Run the following command after adjusting the input filename if needed. Quoting each path keeps My Game together as one argument.

& ".\relinker-v0.1.1.exe" --windows ".\source\My Game\eboot.elf" ".\app.exe"

Keep --windows. This flag selects Windows output. An .exe filename by itself still produces Linux ELF output in this release.

Read the complete terminal output. If conversion fails, stop at that stage rather than trying to launch a file left by an earlier attempt.

5. Convert the executable on Linux

Open a terminal in anyps5-work. Make the downloaded relinker executable, then convert the input. Linux output is the default in v0.1.1.

chmod +x "./relinker-v0.1.1"
"./relinker-v0.1.1" "./source/My Game/eboot.elf" "./app.elf"

For an Intel host, add --to-intel between "./relinker-v0.1.1" and the input path. The same supported-instruction limits described in the Windows section apply.

6. Arrange the libraries and game resources

Extract the library archive into anyps5-work. Its entries already sit under libs/, so extracting directly into another libs folder can create the incorrect path libs/libs/.

Place the game's resources under app0, preserving the generated modules. The output layout should be:

anyps5-work/
├── app.exe                  # Windows; app.elf on Linux
├── libs/
│   ├── <AnyPS5 system libraries>.prx
│   └── <included runtime DLLs>.dll   # Windows archive
└── app0/
    ├── <game resources>
    └── sce_module/
        └── <generated modules>.guest.prx

If your input used sce_modules, the generated directory retains that name under app0. A module named libfoo.prx, for example, produces libfoo.prx.guest.prx. Follow the paths printed by your conversion.

The two library locations have different jobs. libs contains AnyPS5's system libraries for the target OS. app0/sce_module contains generated modules belonging to the title. Keep all files supplied in the Windows library archive, including its runtime DLLs.

7. Launch the output and record what happens

Stay in anyps5-work. Use the command for your target OS after the runtime checklist passes:

& ".\app.exe"

chmod +x "./app.elf"
"./app.elf"

The Linux output needs its own executable permission; granting it to the relinker does not grant it to the generated file.

Record the stage reached: conversion completed, process started, a menu appeared, or gameplay worked. Those observations establish different things. A generated executable, working menu or shader compilation result alone does not establish full playability.

Common setup questions

Sources and verification

Reviewed October 11, 2026. Release instructions use commit fe1935ef682d0b6fb94c0a3554a531b695302a8c. These checks establish what the inspected source implements; they do not replace a game test.

• v0.1.1 release and assets: downloadable components.
• Release CLI parser: flags and positional input/output paths.
• Release conversion entry point: target format, output and runtime layout.
• Release module builder: directory rules and generated module paths.
• Release packaging script: archive layout and Windows dependencies.

For the original repository and other downloads, return to the AnyPS5 download overview. Send guide corrections to [email protected].