Quick Start

Quick Start

This walk-through takes a debug package game.pkg to a running game. Replace ~/AnyPS5/build with the build directory of your AnyPS5 checkout.

1. Look inside the package

pkg-to-anyps5 game.pkg --list

This writes nothing. It prints the content ID, the outer and inner filesystem details, and every file with its size:

package     game.pkg
content ID  XX0000-XXXX00000_00-XXXXXXXXXXXXXXXX
FIH         format 3, PFS 0x10000+0x...
outer PFS   5 inodes, block size 0x10000, seed PPRPLAIN-NOAUTH!
inner image 7.74 GiB logical in … blocks (… stored, … Kraken, … sparse)
files       2144 under uroot, 7.74 GiB
        37725424  eboot.bin
        ...

The files line tells you how much disk space a full extraction needs.

2. Try the executables first (seconds)

pkg-to-anyps5 game.pkg out --executables-only
~/AnyPS5/build/core/relinker/relinker out/source/eboot.bin out/app.elf

This unwraps only eboot.bin and the modules, then runs the relinker on them. If this step fails, a full copy would fail too, and you only spent a few seconds finding out.

3. Extract everything

pkg-to-anyps5 game.pkg out --verbose
~/AnyPS5/build/core/relinker/relinker out/source/eboot.bin out/app.elf
mkdir -p out/libs && cp ~/AnyPS5/build/core/libs/libs/*.prx out/libs/
chmod +x out/app.elf

On a 2.4 GB package the extraction takes about 10 to 25 seconds; large games take minutes. --verbose shows a live progress line; without it, progress is printed every 4 GiB.

Deprecated: --relink, and --module-dir and --windows with it, are no longer maintained and will be removed in v1. They still work in 0.2.x and print a warning. Run the AnyPS5 relinker yourself instead, as above.

4. Run it

cd out
./app.elf

How far a game gets depends on AnyPS5's coverage of the PS5 system libraries, not on this tool. See Running with AnyPS5.

Re-running

The tool writes into the output directory and overwrites files with the same name. Use a fresh directory (or delete the old one) after a failed run, because files finished before the error stay behind.