How to use AnyPS5

How to use AnyPS5: before you start

New to the project? Read what AnyPS5 is, then choose a setup from the compatibility list. Keep the relinker and libraries from the same build. Follow the official build instructions if your report requires source changes.

01. Find a report for your exact title.

Search the game library by name or PPSA ID. Check the edition, platform, hardware, test date and build. A result on an integration branch does not establish the same result on a release or current main.

02. Prepare the input files.

The native relinker takes a clean executable ELF. Keep the game’s extracted resources and bundled modules available. The upstream usage documentation describes the supported layout and additional module directories.

source/
  input.elf
  sce_module/
    <bundled ELF modules>

The default lookup accepts sce_module/, sce_modules/ or prx/ beside the input. Both sce_module/ and sce_modules/ together cause an error. If you supply --sce-module-path, use the parent of these directories.

You can use the local ELF checker for a basic header check. It cannot prove that a payload is decrypted, safe or compatible.

03. Choose your conversion route.

The official browser converter handles supported ZIP or folder inputs locally. Its documented executable-and-module limit is 256 MiB combined; other memory and output limits also apply. Read the current limits on that page before choosing a large input.

For a native workflow, get or build the relinker using the official repository. Our command builder supports Windows PowerShell and Linux Bash. Windows needs --windows; naming an output .exe alone does not select the Windows format.

Native conversion examples

From a folder containing the relinker and source/, use the command for your target. Add report-specific options through the command builder.

# Windows PowerShell
.\relinker.exe --windows source/input.elf app.exe

# Linux Bash
./relinker source/input.elf app.elf

04. Prepare the runtime layout.

Keep the converted executable, matching host libraries, converted modules and the title’s resources in the layout required by upstream. Conversion alone does not supply the complete game or make missing system functions work.

app.exe (Windows) or app.elf (Linux)
libs/
  <AnyPS5 system libraries for the target OS>
app0/
  eboot.bin
  <game resources>
  sce_module/
    <converted guest modules>

Follow the output paths printed by the relinker. Original console modules do not belong in libs/. For self-built Windows libraries, also supply the matching toolchain DLLs listed in the upstream runtime instructions.

On Windows and Linux, the host needs the CPU extensions used by the title’s compiled code. The runtime checks required capabilities at startup. Intel translation cannot handle AMD-specific instructions generated by the title at runtime. Graphics, memory requirements and driver behavior vary by game and build.

05. Launch and record what happens.

Run from the output folder using .\app.exe in PowerShell or ./app.elf in Bash. A Linux download that lost executable permission needs chmod +x app.elf first.

Keep the title ID, platform, GPU, build or commit, extra patches, error text and observed stage together. If a title reaches a menu and later crashes, preserve both observations. The upstream Game bring-up discussions are the place to share your result.

Why does conversion succeed but the game still fail?

Check runtime paths and build matching first. A valid output file alone says nothing about unimplemented system calls or rendering. Compare the failure with your game’s source-linked report before trying unrelated flags.

Guide checked on October 16, 2026 against usage at commit 5d9dcc42d. Always check the current upstream instructions for your build.