How We Track AnyPS5 Progress
By AnyPS5 Progress Tracker · Published · Updated
Every number on AnyPS5 Progress Tracker is read from a public source, shown with that source, and never edited by hand. This page explains which sources we use, how often we read them, how we count, and what we refuse to publish.
Sources
| What you see | Source | Owner |
|---|---|---|
| Releases, version numbers, asset sizes | GitHub Releases | Official AnyPS5 repository |
| Declared functions implemented (44.78%), shader recompiler progress | progress.json from the official progress workflow | Official AnyPS5 repository |
| Game stages, confidence, blockers, progress history | roadmap.json of the AnyPS5 blocker map | Community project by AlxcBTW (MIT), linked from the official README |
| Stars, latest release and last commit of other emulators and PC ports | GitHub API, one request per listed repository | Each project’s own repository |
The official AnyPS5 repository used to keep its own compatibility list (COMPATIBILITY.md). It was removed on October 12, 2026, and the official README now points to the blocker map instead. Since then the blocker map is our only source for game results. Older entries from the removed list are kept only as history on the progress page.
How the data is updated
- Daily read. A script runs every day at 02:00 UTC and downloads the sources above. The last run read the official repository on Nov 21, 2026 and the blocker map on Nov 21, 2026; the blocker map itself was generated on Oct 23, 2026.
- Schema check. If the blocker map changes its data format or is missing a required field, the script stops and keeps the previous data instead of publishing something half-read.
- Change check. The read time changes every day, so it is ignored. The site is only rebuilt when an actual figure changed: a new release, a new stage, a new report, a changed library count.
- Build check. Before anything goes live, the site must pass a full build and lint. A failed check means yesterday’s version stays online.
Each page that shows these figures names its source and the date it was read, right next to the number.
The 8 stages
The blocker map ranks how far a game gets on AnyPS5 with eight stages. A stage only counts when it was reached on the AnyPS5 main branch (or main plus pull requests that have since been merged). Results from unmerged branches are shown separately on game pages as “reported further, not confirmed”.
| # | Stage | Definition (blocker map) |
|---|---|---|
| 1 | Converts | The package unpacks and the relinker converts the executable. |
| 2 | Loads | All imports resolve and the ELF loads. |
| 3 | Starts | Guest code runs past startup. |
| 4 | First draw | The first GPU draw or dispatch executes. |
| 5 | Presents | Frames reach the screen (loading screens and black frames count). |
| 6 | Menus | A menu or title screen renders and responds. |
| 7 | Ingame | Gameplay is reached. |
| 8 | Playable | Playable from start to finish with minor issues. |
The first stages are technical milestones that a player never sees. A game at “First draw” has already loaded and started running its own code; it fails before a picture reaches the screen. Only Menus, Ingame and Playable describe something you could actually interact with. That is why a game page answers “Can AnyPS5 run it?” with “Not yet” for anything below Ingame.
Confidence levels
Next to every stage we show the blocker map’s own confidence label. We never raise or lower it. The definitions below are quoted from the blocker map data:
| Label | Definition (blocker map) | Games |
|---|---|---|
| Checked by hand | A person checked the source (data/blockers.json, a stage review), or the maintainers' list has it. | 94 |
| N reports on main (N ≥ 2) | Two or more GitHub accounts report the stage on main, or on main plus merged PRs. | 76 |
| 1 report on main | One account reports the stage on main, or on main plus merged PRs. | 131 |
“N reports on main” is a count of different GitHub accounts, not a verification: two people can make the same mistake. “Checked by hand” means a person reviewed the source, such as the blocker map’s curated data or a stage review. Even then, a result describes one build, one operating system and one GPU; the game page shows which ones when the report says.
How we count
- One game set. All counts use the same list: the 301 games that have a recorded stage on the blocker map. We do not merge in lists from elsewhere.
- Totals use confirmed results only. The status bar and home page show 7 playable and 38 reaching gameplay. Those totals only include the 170 games that are checked by hand or have two or more reports. Single reports stay visible in the games list but are not counted.
- Game pages. We publish a page for a retail game once it reaches at least Presents with a qualifying report (134 pages today). Lower stages and tech demos stay in the list only, because a page would have nothing to say beyond “it does not start yet”. Pages whose only evidence is a single report at Presents, with no other information such as an official PC status, are kept for visitors but marked
noindexand left out of the sitemap (38 today); they return to search automatically once the data grows. - Library coverage is not compatibility. 44.78% is the share of declared system functions that are implemented. The denominator grows as new functions are declared, so the number can fall while the project improves. See what it measures.
Official PC versions
Some game pages and the PS5 exclusives not on PC list say whether a game has an official PC version. We check each game by hand against an official source only: its Steam or Epic Games Store page, playstation.com, or the publisher's site or blog. Every entry links that source and shows the date it was checked. “None announced” means we found no official PC announcement on that date; rumours, leaks and ratings-board listings do not count. These entries are re-checked monthly. This is separate from the AnyPS5 stage, which always comes from the blocker map.
Page dates
- Published is the day a page first went online.
- Updated is the last time the page’s own text changed, or for data pages, the last time one of its figures actually changed. A game page’s date follows that game’s own reports, not the whole site.
- Official data checked appears only on pages that show synced figures and tells you when the sources were last read, even if nothing changed.
What we do not do
- We do not test games, and we do not write our own verdicts about compatibility.
- We do not host, link to or index games, firmware, keys or console dumps, and we do not publish jailbreak, dumping or decryption steps. AnyPS5 needs a copy of a game you legally own; see is AnyPS5 legal?
- We do not show the names of people who filed reports; game pages link to the original report instead.
- Claims from outside these sources (for example, a social media post saying a game runs) are labelled “Third-party report · not verified” and never counted.
- We are not the AnyPS5 developers. Bugs in AnyPS5 belong in the official issue tracker.
Corrections
If a figure here does not match its source, email contact@anyps5.app with the page and a link to the source. If our copy is out of date, the next daily sync usually fixes it. If the source itself is wrong, for example a stage in the blocker map, the fix belongs in the blocker map repository, and the change reaches this site with the next sync.
Methodology FAQ
Does anyps5.app test games itself?
No. We do not run games and we never add, upgrade or downgrade a game result ourselves. Game stages and confidence levels come from the community blocker map that the official AnyPS5 README links to, and every game page links to the original report.
Why does the site count fewer playable games than the games list shows?
Headline counts (the status bar and home page cards) only include games whose stage is checked by hand or reported by at least two different people. Single reports stay visible in the games list and on game pages, marked “1 report on main”, but are not added to totals.
Is 44.78% the share of games that work?
No. It is the share of system functions the AnyPS5 project has declared so far that are implemented. The denominator grows as new functions are declared, so the percentage can go down while the project moves forward. It says nothing direct about which games run.
How quickly do new reports appear here?
The site reads its sources once a day at 02:00 UTC. A report shows up after the blocker map has picked it up and our next daily sync has run, so expect a delay of up to about a day after the blocker map updates.