Questions people ask

A tool that turns a PS5 game's executable into a native Linux or Windows program. It ships a relinker, which rewrites the executable, and reimplementations of the PS5's system libraries, which the converted program calls instead of the console's. Start with the setup guide.

No. An emulator interprets a console while a game runs. AnyPS5 converts the executable once, so the game's own code runs directly on your CPU, with no emulation layer and no separate runtime process. Its calls into the system libraries go to native code, and its GPU shaders are recompiled to Vulkan.

AnyPS5 is free, open-source software under the GNU GPL v2. It does not include or download any game, firmware or keys: you convert a game you dumped yourself from a console you own. Whether dumping and running your own copy is allowed depends on where you live, so check your local law. This is not legal advice.

Yes, to make the dump. AnyPS5 works on a decrypted dump of a game you own. The dump step of the guide lists what it needs.

An x86-64 CPU with the instruction set extensions of the PS5's Zen 2 processor (AVX2, FMA, F16C, BMI1, BMI2, LZCNT and MOVBE), a GPU with Vulkan 1.1, and plenty of memory: a PS5 game can reserve up to 13.5 GiB. The requirements page has the details.

Mostly. Some games use AMD-only instructions, so convert with Convert AMD-specific instructions for Intel CPUs ticked, or --to-intel on the command line. A few titles generate AMD-only code while they run; those still need an AMD CPU.

On paper it qualifies: its APU is the same Zen 2 generation as the PS5's, and it runs Linux with a Vulkan driver. Its 16 GB is shared between the CPU and GPU, though, and games can reserve up to 13.5 GiB, so memory will be tight. If you try it, please share how it went.

The relinker itself runs on macOS, including Apple silicon, and can write macOS executables. Games need the system libraries too, and those are built for Linux and Windows; macOS support for them is still in progress.

Each stage on the compatibility list is a step further than the one before: the game's code runs, then draws, then shows frames, and so on. A game usually stops because it calls a system function that is not implemented yet, or uses a GPU feature the shader recompiler does not handle. Game pages show What it needs when the latest report names it, and the progress page lists what most games are waiting on.

AnyPS5 stops on purpose when it meets something it does not support yet, and prints why. Look the message up in troubleshooting. If it is not there, put it in a run report or the game's discussion thread: the exact error text helps most.

The first time a game runs, its GPU shaders are recompiled and cached. Later starts reuse the cache and are much faster.

In the _sd folder next to app0/; copy _sd and _sd_mem to move your progress. See running the game.

Don't count on them yet. The network and PlayStation Network libraries are among the least complete; the library map shows how far each one is.

Test games and report the results, including crashes: every report makes the compatibility list more accurate and shows developers what to fix next. If you write C++, the most wanted list and the contributing guide are good places to start. Questions are welcome on Discord.

Every game page has a Suggest a correction link that opens the right file to edit. A maintainer's correction always wins over automatic reports.