Guide

AnyPS5 Turns PS5 Games Into Native PC Binaries. It Just Shipped Its First Release.

Cole StubblefieldBy Cole Stubblefield 2026-09-23 Updated 2026-10-05
AnyPS5 Turns PS5 Games Into Native PC Binaries. It Just Shipped Its First Release. — News guide for retro handhelds | Held Games

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 · Updated 2026-09-30

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.

When we first published this on 23 September, it had never launched a game to completion and there was nothing to download. Five days later both of those changed. There are two releases and one named game that runs start to finish.

So this is what AnyPS5 actually does, how far it has got, and what would still 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: an independent developer, working in the open on GitHub since 3 August 2026
  • Licence: GNU GPL version 2 only
  • How far it gets: one verified game, the 2D platformer Dreaming Sarah, is playable start to finish on Windows
  • Releases: v0.1.0 and v0.1.1, both published 28 September 2026, for Linux and Windows
  • Graphics: Vulkan, with a shader recompiler that emits validated SPIR-V
  • Interest: roughly 2,500 stars, up from 279 a week earlier

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.

One generation back, the same approach now has a working build. In October 2026 a project called bbport did this for a single PS4 game, converting Bloodborne's executable ahead of time and pairing it with a runtime that implements only the PS4 libraries that one game calls. It is playable and downloadable, which is the thing AnyPS5 still is not. It is also narrower by design: one game, one game version, Linux only. Read it as evidence that the relinking idea works in practice rather than as a preview of AnyPS5, since a PS4 is a far simpler target than a PS5. Our write-up is here.

How Far It Got in September, and Why That Mattered

This section describes the state of the project when we first published, on 23 September. The update that follows it supersedes it, but the sequence is worth keeping, because it shows how fast the last step came.

The README kept a running status, and it was 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.

Update, 30 September: The Three Things We Said to Watch For All Happened

When we published this on 23 September, we closed by naming three signals that would mean something had changed. A named game, a first release, and a second contributor. All three landed within five days, so this section replaces the state of play described above.

There is a release now. Two, in fact. v0.1.0 and v0.1.1 both went out on 28 September 2026, with actual binaries attached: a relinker for Linux and Windows, and the reimplemented PRX libraries for both. The README section promising releases only after a full successful launch is gone, because that bar was met.

The game is named, and it finishes. The project's compatibility list has one entry: Dreaming Sarah, a 2D platformer, title ID PPSA02929. It is marked "In game, playable" on Windows, with Linux still listed as unknown. The project reports it at 60 FPS on a GTX 1050 Ti with an i5-7500, and 36 FPS on Intel HD Graphics 620 with an i5-7200. That second figure is an integrated GPU from 2017, which is the more interesting of the two.

The save data wall is gone. The exception at frame 71 was a missing save data implementation. v0.1.1's changelog includes a general save data core covering mounts, directories and memory slots. The same release added a FreeType based font implementation ported from shadPS4, a real message dialog state machine, an offline socket and resolver stack, and a full AvPlayer state machine.

And it is no longer a solo project. The two releases credit contributions from at least seven people other than the maintainer, across more than a hundred pull requests. Star count went from 279 to roughly 2,500 in a week.

Set expectations properly, though. One verified game, a 2D indie platformer, is not the PS5 library. The compatibility list has a single row on it. What changed is that the approach has now carried a commercial PS5 title all the way from relinking to a playable end state, which is the thing nobody had demonstrated a week ago.

Downloads Now Exist, So Know Where They Come From

This section used to say there was no download at all. That is no longer true, which changes the advice rather than removing the need for it.

Official builds come from the project's own GitHub releases page and nowhere else. Everything we have written about PS5 emulation search results being full of scams still applies, and it applies more now, because a real release gives fake sites something plausible to imitate. A site offering an AnyPS5 installer, a bundled game, a "full version" or anything that asks for payment or a survey is not the project.

The other thing worth knowing is what a release does not include. There is no copyrighted Sony code, no firmware and no keys, and the project's own disclaimer says so. You supply the executable, and it has to come from a game you own.

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

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

The three signals we originally listed here, a named game, a first release and a second contributor, have all happened. See the 30 September update above. Here is what replaces them.

A second game on the compatibility list. One verified title is a proof that the pipeline can complete. Two or three, especially anything 3D, would start to say something about how general the approach is.

A Linux confirmation. The compatibility table marks Windows as playable and leaves Linux as a question mark, which matters a lot for Steam Deck and handheld readers.

Something demanding. Dreaming Sarah is a 2D platformer that runs on a 2017 integrated GPU. The interesting test is a title that actually uses the PS5's GPU features, because that is where the shader recompiler gets stressed.

A slowdown. Seven contributors in a week is a burst, not a trend. Reimplementing a console's system libraries is enormous, and the thing to watch is whether the pace holds past the first release.

Questions People Ask

Can I download AnyPS5?

Yes, as of 28 September 2026. The project published v0.1.0 and v0.1.1 that day, with relinker and library builds for Linux and Windows. Get them from the project's own GitHub releases page only. Any other site offering an installer, a bundled game or a paid "full version" is not the 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?

One game is verified playable end to end. The project's compatibility list has a single entry, the 2D platformer Dreaming Sarah, marked "In game, playable" on Windows and reported at 60 FPS on a GTX 1050 Ti and 36 FPS on Intel HD Graphics 620. Linux status for it is listed as unknown. Earlier reporting, including ours, described an unnamed game dying at around frame 71 on missing save data; that was fixed by the save data work in v0.1.1.

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 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.

Related reading