First answers — then the limits

Is AnyPS5 an emulator?

No. README describes a tool for automatic executable porting to Linux and Windows. The relinker converts the executable to the target system’s native format, and replacement system PRX libraries supply the functions that executable calls. README: no emulation or separate runtime process. The converted title is an ordinary host process.

A converted process is not a claim that every title works. The official web converter says conversion does not guarantee that an app runs. Check the title page and live Game bring-up threads before you treat a name as working. Game bring-up.

Do I need a PS5 console?

You do not need a PS5 connected while the converted title runs on the PC. Official runtime targets are x86-64 Windows and Linux.

You must supply your own dump: a clean ELF executable, its bundled modules, and the game resources. USAGE.md: use a clean ELF; place bundled ELF modules in sce_module/, sce_modules/, or prx/; unwrap SELF/fSELF before relinking if those containers need to be included. Preparing those files is separate from downloading the tools.

Where do the games come from?

You supply them. This site does not host games, firmware, or keys. Official GitHub Releases ship the relinker and matching host libraries.

README: the project does not include, distribute, or require copyrighted software, firmware, cryptographic keys, or proprietary libraries. The tools zip is not a game pack, ROM set, or key dump. SELF/fSELF files are not inputs. Users are responsible for using only files they are legally allowed to use.

Why are there so few official titles?

The project’s archived official tested-compatibility table, quoted in discussion #2475, lists few rows: Dreaming Sarah (PPSA02929) and DOOM Shareware homebrew (PPSA99666). Current README points per-game progress to the community blocker map and Game bring-up discussions.

Community reports on this site keep their own build source (release, main, fork, patched, or unknown). Official table membership is not a release-zip claim. Playable and In-game on those reports are not full-game completion.

Does Playable mean the game is finished?

No. On this site Playable means the cited report can be played, with only minor problems. In-game means gameplay was reached, with serious problems, low frame rate, or extra patches. Menus, Boots, and Nothing stop earlier.

The snapshot shows the furthest public stage, including testing branches. It is not an official playable verdict and not a full-game completion claim. A window is not Playable. The official zip may stop earlier than a later main or patched report.

Does AnyPS5 run on Mac?

Official GitHub Releases ship host libraries for Linux and Windows only. README and BUILD.md: the relinker-only build runs on macOS, including Apple silicon. USAGE.md: --macos writes x86-64 Mach-O, which runs under Rosetta on Apple silicon; --to-rosetta lowers instructions Rosetta lacks.

A passing relinker-only compile, or a Mach-O convert, is a conversion experiment. It is not a shipped Mac game runtime and not Playable. Converted titles still need system libraries built for the target OS. This page does not invent Mac playable.

Where are save files?

GAME_TESTING.md: save data is kept under the runtime’s _sd/ folder, and save-data memory under _sd_mem/. Copy them into a new runtime to continue from the same point. Source: libSceSaveData.native uses _sd as the save directory; libc maps a guest mount such as /savedata0 to _sd/<dir name>.

Some titles write elsewhere. The official DOOM homebrew notes in discussion #2475 record /download0/doom1sav0.dsg through plain I/O, not sceSaveData. USAGE.md: a present param.json creates data/; a non-zero downloadDataSize also creates download0/.

Test both save and load. Reaching gameplay does not prove that either works. This site marks save support known or unknown per title when a reviewed deepen block exists; unknown stays unknown.

Why is my result different?

Compare the title ID, content version, AnyPS5 tag or commit, patches, host OS, and the GPU and driver from the Physical device candidate / Selected GPU lines. GAME_TESTING.md asks for those fields in that order.

Leave missing fields empty. Do not fill them from another report. A mixed Windows relinker with Linux libraries, or mixed tags, is a failed layout, not a title test. Vulkan 1.1 is a device filter, not a playable claim. Docs do not publish a universal minimum RAM or GPU for every title. USAGE.md selects the first Vulkan 1.1 device with graphics and compute queues and swapchain presentation, preferring a discrete GPU over an integrated one.

After these answers

If you still need the two files, the folder layout, the host filters, or a named error, use the pages below. Do not treat this FAQ as a stage upgrade.

Download: official zip pair · Setup: two files and folder layout · Compatibility: public stages · Host requirements: OS, GPU, CPU · Troubleshooting: 193, 126, host limits · Build from source: relinker vs full runtime

Do not claim

• That AnyPS5 is a classic console emulator with a separate runtime process.
• That the official zip includes games, ROMs, firmware, or keys.
• That a PS5 must stay connected while the converted title runs on the PC.
• That official table membership is a release-zip claim or a full-game completion.
• That Playable or In-game means the whole title is finished.
• That official releases ship a Mac game runtime, or that a Mach-O convert is Playable.
• That reaching gameplay proves save and load both work.
• That Linux audio is fixed on the latest tag.
• A universal minimum RAM or GPU for every title.

Original sources

• README on current main (porting tool, no separate runtime, disclaimer)
• USAGE.md on current main (clean ELF, modules, --macos, download0/)
• BUILD.md on current main (relinker-only on macOS, Linux/Windows libraries)
• GAME_TESTING.md (_sd/ and _sd_mem/, report fields)
• Official tested-compatibility table (quoted in discussion #2475)
• libSceSaveData.native Export.cpp (SAVE_DIR _sd)
• libSceSaveData SaveDataCore.hpp (guest /_sd)
• libc General.cpp (guest /savedata0 → _sd/<dir name>)