News report
Dead Cells PS5 Build Runs Natively on Windows Through AnyPS5
An AnyPS5-based project now runs a PS5 build of Dead Cells as a native Windows executable, with gameplay, audio and input working without a PS5 emulator.
On this page
A PS5 build of Dead Cells is now playable as a native Windows program
A new project built on AnyPS5 has moved the experimental PlayStation 5-to-PC relinking approach from partial startup into a playable demonstration. The DeadCells-PS5-Native repository says Dead Cells: Return to Castlevania Edition can run from its PS5 executable as a standalone Windows program, reaching gameplay with music and sound effects while supporting keyboard, mouse and gamepad input.
The distinction from conventional console emulation is central to the project. The original x86-64 game code is relinked into a Windows executable rather than being executed inside a PS5 emulator, while the console libraries the game expects are replaced by compatible DLL implementations. GPU shaders are recompiled for Vulkan. The project still requires users to supply their own legally obtained game files and does not distribute Sony firmware, keys or the game itself.
| Area | Current status | Boundary |
|---|---|---|
| Execution model | PS5 x86-64 executable relinked into a native Windows program | Not conventional full-system or CPU emulation |
| Graphics | PS5 shaders recompiled to SPIR-V and presented through Vulkan | One game and tested configuration do not establish broad PS5 compatibility |
| Gameplay | Repository reports play from menu through gameplay with audio | Only the specified Dead Cells PS5 version is documented as tested |
| Input | Keyboard, mouse and gamepad are reported working | Compatibility with other games and peripherals is not established |
| Distribution | Open-source project code is available | Users must provide their own legally obtained game files |
AnyPS5 replaces console services instead of recreating the whole console
AnyPS5 describes itself as an executable-porting tool for Linux and Windows. Its relinker converts the target executable to the host operating system's native format, and replacement implementations of PlayStation system PRX libraries provide functions the original program expects. That architecture is possible in part because PlayStation 5 software already targets x86-64 CPU code, although console-specific operating-system services and graphics behavior still have to be reproduced.
On the graphics side, the project translates console shaders into SPIR-V for Vulkan. AnyPS5's own status documentation says its standalone SPIR-V test passes GPU readback and presentation checks, while application graphics support remains active development. DeadCells-PS5-Native is therefore a concrete game-specific result built on an incomplete general-purpose compatibility project, not proof that arbitrary PS5 software can already be converted automatically.
The reported performance numbers are project measurements, not a universal AnyPS5 benchmark
The DeadCells-PS5-Native repository reports roughly 55–60 FPS in indoor scenes and 30–35 FPS outdoors at 4K on a Ryzen 7 5800X3D and GeForce RTX 5070 Ti. Those numbers are useful evidence that the demonstrated build can progress through real gameplay, but they are developer-reported results from one machine and one game version rather than independent Core Tech Tips measurements.
They also cannot be used to quantify the overhead saved by relinking versus emulation. A defensible comparison would require the same game content, hardware, settings and workload under a mature emulator or another equivalent execution path. The current milestone is architectural and functional: a real PS5 game build has been adapted into a playable native Windows program using the AnyPS5 approach.
What happens next depends on whether the method generalizes
AnyPS5's broader goal is automatic executable porting rather than maintaining a handcrafted Windows conversion for a single title. Its repository says releases are intended after a first full successful game launch, while many console-library and graphics behaviors remain under implementation. Dead Cells demonstrates that the approach can cross the line into gameplay for at least one comparatively tractable target.
The more important test is now breadth: whether the same relinker, replacement libraries and shader pipeline can handle substantially different PS5 games without large game-specific rewrites. Until multiple titles and hardware configurations are demonstrated, AnyPS5 should be treated as an early open-source compatibility experiment with a notable first playable result, not as a practical replacement for PS5 hardware.
Sources
Primary and technical sources
These sources support the reporting and analysis above. Current stories are updated when later evidence materially changes the facts.
01 OverkillLabs / GitHub
DeadCells-PS5-Native repository and technical status02 boykopovar / GitHub
AnyPS5 repository and project status03 Tom's Hardware
AnyPS5 project coverage
Related
Continue from here
Useful next steps selected from the same technical reference and publication system.
Compatibility & upgrades
Windows 11 Upgrade Compatibility: TPM 2.0, Secure Boot, CPU, RAM, Storage, and Graphics
Check Windows 11 upgrade eligibility using Microsoft’s current CPU, TPM 2.0, UEFI/Secure Boot, RAM, storage, graphics, and PC Health Check requirements.
Compatibility & upgrades
Wi-Fi 5 vs Wi-Fi 6 for PCs
Compare Wi-Fi 5 (802.11ac) and Wi-Fi 6 (802.11ax) for PCs by bands, channel widths, modulation, multi-user efficiency, compatibility, and real upgrade limits.
Tool
DDR Memory Latency Calculator
Convert DDR data rate and CAS latency cycles into CAS timing in nanoseconds.
Technical guide
Windows Page File Explained: Virtual Memory and Commit Limit
Understand what the Windows page file does, how it extends the system commit limit, how paging differs from RAM use, and why crash dumps can depend on it.