How to read an AnyPS5 compatibility report

Oct 14, 2026AnyPS5 Ledger

Playable, in game, a question mark, and a bring-up thread do not mean the same thing. Use this scale before you repeat an AnyPS5 screenshot.

AnyPS5 reports are easy to over-read. A log line, a thread title, and an archived table cell are three different kinds of evidence.

The scale used here

Playable. Reserved for the archived official table. Today that is Dreaming Sarah on Windows.
In game. A cited report reached gameplay on a named setup. It is not a promise for your GPU.
Menus. The report stopped at UI, team select, or a load screen.
Thread only. A GitHub bring-up discussion exists. No reviewed result is copied onto this site.
Not listed. The archived table has no row. That is not a yes, and it is not a no.
Wrong console. The search is for a PS4 game. Bloodborne belongs with shadPS4.

"?" is not a failure. On the archived Dreaming Sarah row, Linux is unknown.
Exit code 0 is not gameplay. The relinker can finish and the game can still throw runtime_error on the first missing function.
A pull-request title is not a status. v0.1.0 mentioned booting Demon's Souls to its first level. Later public notes still describe a broken tutorial.

Test reports belong in the Game bring-up discussions, one thread per title. Library and shader coverage is on the upstream progress page. The blocker map is a community view of public GitHub data.

The compatibility list on this site was checked on 14 Oct 2026. If a row and a newer discussion disagree, believe the discussion that names a commit.