AnyPS5 Turns PS5 Games Into Native PC Binaries. It Cannot Finish One Yet.

Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.

2026-09-23 · News and analysis

Affiliate disclosure: This guide contains affiliate links. As an Amazon Associate, we earn from qualifying purchases at no extra cost to you. Learn more.

A project called AnyPS5 has been getting written up as the biggest step yet toward PlayStation 5 games running on PC, and the technical claim behind that is real. It is not an emulator. It takes a PS5 executable and rewrites it into a binary your operating system runs directly, with no emulation and no separate runtime process.

It has also never launched a game to completion, and there is nothing to download. Both of those facts are stated plainly by the developer, and both get lost in the coverage.

So this is what AnyPS5 actually does, how far it has actually got, and what would have to happen before it means anything for a handheld.

The Short Version

What it is: a relinker that converts PS5 executables into native Linux ELF or Windows PE binaries, plus reimplemented PlayStation system libraries
What it is not: an emulator. Nothing is being emulated at runtime
Developer: boykopovar, working in the open on GitHub since 3 August 2026
Licence: GNU GPL version 2 only
How far it gets: a real game reaches the render loop and presents its first frames, then throws an exception around frame 71
Releases: none, deliberately. The developer will publish after the first full successful launch of one game
Graphics: Vulkan, with a shader recompiler that emits validated SPIR-V
Interest: around 279 stars, which is attention rather than progress

Relinking, Not Emulating

The distinction here is the whole point, and it puts AnyPS5 much closer to the recomp family than to the PS5 emulators people usually compare it to.

An emulator recreates the console at runtime. It pretends to be the CPU, the GPU and the operating system while your game runs, and it pays a translation cost on every frame forever.

AnyPS5 does the work once, ahead of time. A relinker takes the guest PS5 ELF executable and rewrites it into the target system's native format, either a Linux ELF or a Windows PE file. The rewritten binary is then a normal program as far as your OS is concerned.

That alone would not be enough, because the game still calls PlayStation system functions that do not exist on your PC. So the project also reimplements Sony's system PRX libraries, including libc, libkernel and a set of libSce* service modules, as things the rewritten binary can dynamically link against. Those bridge the game's calls to native OS and graphics primitives.

The graphics side is handled by a shader recompiler that decodes the game's AMD RDNA shader binaries into an intermediate representation and emits SPIR-V, which is what Vulkan consumes. Shader dispatch goes through a reimplementation of libSceAgcDriver.

If the general idea is unfamiliar, our decomp vs recomp explainer covers ahead of time translation, and what translation layers actually do covers the runtime alternative that Proton and Box64 represent. AnyPS5 is doing something closer to the former.

How Far It Actually Gets

The README keeps a running status, and it is refreshingly specific. Execution reaches _start and then main. Stack unwinding and exception handling tables are built. The shader recompiler produces SPIR-V that validates against SPIRV-Tools.

Then this:

The real game reaches the render loop and successfully presents its first frames (logo).

Current exception: Could not open file /_sd/SAVEDATA00/-saveindex on ~71 frame.

That is the state of the art for this approach right now. A commercial PS5 game, unnamed in every source we could find, gets far enough to draw its logo and then dies about 71 frames in because save data handling is not implemented. Anything the project does not support throws an error and terminates the process rather than limping on.

Drawing a logo is genuinely further than it sounds. It means the relinked executable started, the reimplemented kernel library answered enough calls to get through initialisation, the shader path produced working Vulkan shaders and something reached the screen. It is also nowhere near a playable game.

There Is No Download

This is the part to be clear about, because it is where people get scammed.

The README says it directly: "Releases will be published after the first full successful launch of at least one game." The releases page is empty. There is no build, no installer, no early access and no Discord with a secret link. The 279 stars are people watching, not people playing.

That matters because PS5 emulation is one of the most actively faked categories on the internet. We have already written about how most of what you find searching for a PS5 emulator is not real, and a project with real technical credibility and no release is exactly the bait those sites want. If you find an "AnyPS5 download" anywhere, it did not come from this project.

How It Compares to shadPS4 and fpPS4

The comparison people reach for is shadPS4, which is fair as a reference point and misleading as a category.

shadPS4 and fpPS4 are emulators, and they target the PS4 rather than the PS5. shadPS4 in particular has reached a genuinely useful state, to the point where we maintain a shadPS4 setup guide and a running PS4 emulation status page for handhelds. It runs real games today.

AnyPS5 is a different technique aimed at a newer console. Comparing them on maturity is not close. Comparing them on approach is where it gets interesting.

The promise of static translation is that it removes the per frame cost. An emulator keeps paying for translation on every frame; a relinked binary paid once at build time. On paper that is how you get a demanding game onto weaker hardware, and it is the same reasoning behind the whole recomp scene.

The catch is that removing CPU translation overhead does not remove the GPU work. Which brings us to handhelds.

What This Would Mean for Handhelds

Two things point in opposite directions here, and it is worth being honest about both.

The encouraging part. AnyPS5 targets Linux as a first class output, not an afterthought. It emits native Linux ELF binaries and the Linux build path is the one that works cleanly with GCC, while Windows currently needs a specific MinGW-w64 toolchain. A project whose primary output is a native Linux binary on Vulkan is unusually well aimed at SteamOS. Most things in this space produce Windows executables and leave Deck owners reaching for Proton.

The discouraging part. PS5 games were built for RDNA 2 hardware drawing a couple of hundred watts. A

Steam Deck OLED

has a fraction of that GPU budget. Static recompilation removes the cost of pretending to be a PS5 CPU. It does not make the GPU work smaller, and on current generation titles the GPU work is the problem.

So the realistic read is that a working AnyPS5 would be a desktop thing first, and a handheld thing only for whichever PS5 titles happen to be light. That is reasoning from the hardware rather than from any measurement, because there is nothing to measure yet.

The Executable Problem

There is one more practical obstacle, and it is bigger than the code.

A relinker needs a PS5 executable in a form it can read. That is not something a PS5 owner has lying around, and it is not something the project provides. AnyPS5 distributes no firmware, no cryptographic keys, no proprietary Sony libraries and no games, and its disclaimer puts the responsibility for whatever binaries you feed it on you.

We are going to leave it there. The point worth taking away is that even a finished relinker would not turn your game library into PC games, because the input side is a separate and much harder problem for an ordinary owner. Our emulation legal status guide covers the general shape of the law here.

What to Watch For

Three specific signals, in order of how much they would tell you.

A named game. Right now the title reaching the render loop is anonymous in every source. When the project names it, you will be able to judge how representative it is.

The first release. The developer has tied releases to one full successful launch, which is a high and clearly stated bar. If a release appears, something substantial changed.

A second contributor. This is essentially a solo project with five forks and no open pull requests. Reimplementing a console's system libraries is enormous. Sustained progress usually needs more than one person.

Questions People Ask

Can I download AnyPS5?

No. The project has no releases and the developer says builds will only be published after the first complete successful launch of a game. Anything advertising itself as an AnyPS5 download is not from this project.

Is AnyPS5 a PS5 emulator?

No, and the difference is the point. An emulator recreates the console while your game runs. AnyPS5 rewrites a PS5 executable into a native Linux or Windows binary ahead of time, then supplies reimplemented system libraries for it to link against. Nothing is emulated at runtime.

How far can AnyPS5 actually run a game?

A real game reaches the render loop and presents its first frames, which is the logo, then throws an exception at roughly frame 71 because it cannot open a save data file. That is the current documented ceiling.

Is AnyPS5 better than shadPS4?

They are not comparable yet. shadPS4 is a PS4 emulator that runs real games today. AnyPS5 targets the PS5 with a different technique and cannot complete a launch. The approach has long term advantages, the current state does not.

Would AnyPS5 run PS5 games on a Steam Deck?

Nothing runs on anything yet. Even working, the approach removes CPU translation overhead rather than GPU load, and PS5 titles were built for far more GPU power than a handheld has. Expect any eventual benefit to land on desktops first.

Do I need a PS5 to use it?

You would need a PS5 executable in a form the relinker can read, which is not something the project supplies and not something an ordinary console owner has. The project ships no firmware, keys, libraries or games.

Written 23 September 2026. All technical description, the status quotes, the frame 71 exception, the build requirements and the release policy come from the boykopovar/AnyPS5 README. Star count, licence, creation date and release count come from the GitHub API. Both retrieved 23 September 2026 and both are a snapshot of an actively changing project. No build of AnyPS5 exists, so nothing in this article was tested and no performance figures are given.