Windows x64
Windows 10 1803 or newer, 64-bit x86 CPU, Vulkan 1.3 GPU
KytyPS5-2026-11-20-a1fc5ae-Windows-x64.zipEvery link below resolves directly to the official the runtime/the runtime repository on GitHub. Also read the source build summary and changelog below.
Windows 10 1803 or newer, 64-bit x86 CPU, Vulkan 1.3 GPU
KytyPS5-2026-11-20-a1fc5ae-Windows-x64.zipCurrent Linux distribution, 64-bit x86 CPU, Vulkan 1.3 GPU
KytyPS5-2026-11-20-a1fc5ae-Linux-x86_64.tar.gzApple Silicon Mac via Rosetta 2 with bundled MoltenVK
KytyPS5-2026-11-20-a1fc5ae-macOS-x86_64.zipgit clone https://github.com/KytyPS5/KytyPS5.git
cd KytyPS5
cmake -B build -G Ninja -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++
cmake --build build --parallelGrab the Windows zip, Linux tar.gz, or macOS zip matching your system. Skip the file named Source code unless you compile C++ from source.
Unpack the runtime into a folder you control such as C:\the runtime\. Avoid C:\Program Files\ because saves, logs, and patches are written next to the binary.
Open launcher.exe on Windows, kyty_launcher on Linux, or KytyPS5.app on macOS. Running kyty_emulator directly without arguments opens nothing.
Open Global settings then Game folders, and add the parent directory holding your self-dumped titles (folders with eboot.bin and sce_sys, or .zar archives).
Right-click a title and open per-title settings. Turn on Windows SysV red zone crash protection on Windows, and try AMD CPU patch if a title crashes on Intel.
For titles like Astro Bot, put the matching regional JSON inside _Patches next to the launcher (such as _Patches\PPSA21567.json). First launch pauses briefly while compiling shaders.
Best suited for lightweight 2D titles, indie games, and menu checks
Experimental SteamOS builds run lighter titles around 30 to 40 FPS, while heavy 3D games crash or drop below playable speeds.
Best suited for pushing heavy 3D titles and testing experimental DLSS upscaling
With community patches or forks, selected 3D areas hit 40 to 60 FPS, though full crash-free playthroughs are not guaranteed.
Decodes Prospero GPU command buffers and recompiles RDNA 2 shaders into Vulkan 1.3 SPIR-V pipelines without requiring external PS5 BIOS modules.
Upscaling pipelines (PRs #1076, #1265, #1553) intercept Sony PSSR requests in PS5 Pro mode and route them to NVIDIA DLSS, AMD FSR, or Intel XeSS.
Software BVH ray-tracing traversal (IMAGE_BVH_INTERSECT_RAY) is integrated on main alongside verified DualSense gyroscope and adaptive trigger support.
Ten tracked community forks accelerate specific titles, while experimental ports bring these concepts to Xbox Series X and PS4 Linux.
No. the runtime implements PlayStation 5 OS translation in C++ and does not require external low-level emulation modules or copyrighted system dumps.
Most titles remain experimental. While 310 out of 499 tested games reach in-game rendering, crashes, missing lighting, and uneven performance are still common.
Yes, experimentally. macOS builds target x86-64 under Rosetta 2 using the bundled libMoltenVK.dylib library. Only 3 games have formal macOS compatibility reports so far.
Unsigned daily C++ binaries that allocate executable memory for translated guest code can trigger heuristic alerts. Only run archives directly from github.com/KytyPS5/KytyPS5/releases whose SHA-256 matches the official release.
No. the runtime targets PlayStation 5 software exclusively. Use shadPS4 for PS4 titles.
No. Neither the runtime nor ps5emulation.com hosts, links to, or distributes games, keys, or copyrighted Sony software. You must use backups dumped from hardware you own.