PS5 Games on Xbox Series X: What the PS5X Emulator Test Shows
Developer Devran Cosmo Uenal booted the PlayStation 5 version of Quake II on an Xbox Series X and played it with an Xbox controller.
The demonstration appeared in a YouTube video that went live on September 8. PS5X is Uenal's Xbox port of the open-source PS5 emulator KytyPS5, and it runs the PS5 versions of GEX Trilogy, Hellboy: Web of Wyrd, Marvel Cosmic Invasion and Quake II. All four run with Xbox controller inputs. Engadget
PS5X only works in the console's official Developer Mode. Microsoft's documentation caps games at 5GB of memory in Developer Mode. There is no public download for PS5X yet.
That constraint matters. Developer Mode is a sandboxed, officially provisioned environment, not a retail jailbreak. The 5GB ceiling defines which titles can even initialize, which helps explain the current test list of smaller-footprint games rather than large modern releases.
The processor side needs less translation. PS5 games are compiled for the same x86-64 processor architecture used by PCs, which removes one layer of CPU translation from the emulation problem. The graphics side is translation between dialects. KytyPS5 translates the PS5's graphics commands and recompiles its shaders, the small programs that control lighting and effects, for Vulkan, requiring a Vulkan 1.3 graphics card on PC. Xbox Developer Mode only supports DirectX 11 and DirectX 12, not Vulkan, so PS5X must translate graphics to DirectX instead.
Uenal stated in the YouTube video description that AI was involved in the PS5X work. He describes PS5X as a research project for running PS5 homebrew and game backups on a Series X in Developer Mode. He claims PS5X does not include any PS5 firmware or decryption keys.
Separately, developers of SharpEmu, an experimental open-source PS5 emulator, successfully ran six PS5 titles at a playable 60 FPS. Tom's Hardware
The broader context here is the narrow envelope this testing lives in. Four commercial titles plus homebrew, a fixed memory ceiling, no Vulkan path on Xbox, and no public build keep this firmly in lab territory rather than general compatibility. For engineers, the interesting variable is shader translation and DirectX retargeting under constrained memory, not cross-platform play.
In my view, that limitation is also what makes the work worth tracking. If shader translation can be made robust on DirectX without Vulkan, and if input mapping holds across titles, the same techniques feed back into PC emulation and preservation tooling. No download exists yet. The value for now is proof of plumbing.
Looking at what this enables over time, functional homebrew execution across closed consoles tends to extend software lifespan more than it disrupts current hardware. Compatibility remains thin. The direction points toward more interoperable tooling for archival, testing, and small-team development.
