KytyPS5: a GPL-2.0 PlayStation 5 emulator in active development
PlayStation 5 emulator for Windows, Linux and MacOS
At a glance
- What is it?
- KytyPS5 is a C++ PlayStation 5 emulator for Windows, Linux and experimental macOS in active development. The README warns that behavior can change significantly between builds.
- Who is it for?
- Adopt KytyPS5 if you want to build a PS5 emulator from source, file detailed bug reports with full logs, or work on shader recompilation against the RDNA 2 ISA. Do not adopt it as a way to play a PS5 library: the README states compatibility, stability and performance can vary between versions and that you may encounter crashes or graphical glitches.
- Can I use it commercially?
- Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- KytyPS5/KytyPS511,272 ★ · +8,292
| Repository | 2026-09-17 | 2026-11-15 |
|---|---|---|
| KytyPS5/KytyPS5 | 3k | 11.3k |
8,292 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What KytyPS5 solves, and who it is actually for
Running PS5 software on a PC means reimplementing a console whose graphics architecture is based on AMD RDNA 2. KytyPS5 takes that on directly: it is a free and open-source PlayStation 5 emulator written in C++, for Windows and Linux, with experimental macOS support. It is based on a heavily modified version of Kyty, a separate project by InoriRus, so it inherits a codebase rather than starting from an empty repository.
The audience is narrow and the README is honest about it. Under Current Status, the project says development is focused on expanding game compatibility and improving boot reliability, and that external low-level emulation modules are neither required nor planned. The Bugs and Issues section says compatibility, stability and performance can vary between versions and that you may encounter crashes or graphical glitches. If you want a finished way to play PS5 games, this is not it. If you want to watch a young emulator boot commercial titles and you are willing to read logs, the project is aimed at you.
How KytyPS5 works: shader recompilation and a Vulkan host backend
The repository layout shows three cooperating areas. The guest side lives in src/graphics/guest_gpu, which handles PS5 (Prospero) GPU formats and command processing. The host side lives in src/graphics/host_gpu, the Vulkan backend and its resource management. Between them sits src/graphics/shader/recompiler, which the README describes as instruction decoding, intermediate representation, control flow, resource tracking, and SPIR-V emission.
So the data flow is: PS5 GPU commands and shader binaries come in through the guest layer, the recompiler decodes RDNA 2 instructions into an intermediate representation and emits SPIR-V, and the host layer runs that SPIR-V through Vulkan. The renderer targets Vulkan 1.3. The README points developers at AMD's RDNA 2 Instruction Set Architecture Reference Guide (document 70648) as the primary instruction-encoding reference, and warns that shader changes must stay aligned with both RDNA 2 ISA semantics and Vulkan/SPIR-V validation rules. That is the real engineering surface of this project: not a launcher, a translator.
There is a tests directory holding focused memory, shader, and resource-tracking regression tests. The README does not describe a general game-level test suite, so the automated safety net covers components rather than end-to-end titles.
Installing KytyPS5: build requirements and a first run
There is no package manager install documented. The README sends you to the source tree, and Windows and Linux are the primary target platforms. On Windows you need Git, CMake 3.22.1 or newer, Ninja, Visual Studio 2022 or Build Tools 2022 with the Desktop development with C++ workload and C++ Clang tools for Windows, Qt 6 for MSVC 2022 64-bit including Concurrent, Network and Widgets, glslang (glslang or glslangValidator) on PATH, and Python 3 on PATH. The Microsoft C++ compiler (cl.exe) is not supported; use clang-cl.
Open an x64 Native Tools Command Prompt for Visual Studio 2022, change to the repository root, and pull the dependencies:
git submodule update --init --recursiveThen configure. Replace the Qt path with the version installed on your system:
cmake -S . -B _Build/windows -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=clang-cl -DCMAKE_CXX_COMPILER=clang-cl -DCMAKE_PREFIX_PATH="C:/Qt/6.x.x/msvc2022_64"Then build with cmake --build _Build/windows --target launcher and stage a runnable installation with cmake --install _Build/windows --prefix _Build/windows/install. Linux has its own Building on Linux section and macOS its own Building on macOS section. For macOS, the emulator is built for x86-64 and runs on Apple Silicon under Rosetta 2, with Vulkan provided by MoltenVK; a small number of titles have been verified in-game on Apple Silicon hardware. Contributors are asked to install the formatting hook after cloning:
python -m pre_commit install --install-hooksThat hook formats staged .cpp, .h and .inc files in src. Once built, the practical first use is to launch a title you own legally and check the log. The README's bug-report guidance asks for the complete log file attached to a Game Emulation Status Report issue, so treat the log as the primary output of a first run.
Where KytyPS5 falls short, and when it is the wrong tool
The limitations are stated by the project rather than inferred. Behavior can change significantly between builds, and the README says compatibility, stability and performance can vary between versions and that you may encounter crashes or graphical glitches. A release tagged with a same-day commit hash is normal here: three builds dated 2026-11-02 appear in the release list, which tells you the project ships frequently and that any given build is a moving target.
If your goal is to finish a game, this is the wrong tool. The compatibility list is community-maintained, so it reflects other people's hardware and drivers, not yours.
There is also a legal boundary the README draws explicitly: KytyPS5 is not affiliated with Sony Interactive Entertainment or PlayStation, does not distribute games or copyrighted system software, and expects you to use only game files you obtained legally. That is a constraint on use, not a footnote.
KytyPS5 compared with other PS5 emulation projects
ShadPS4 targets PlayStation 4, a different console generation with a different GPU architecture; KytyPS5 targets PS5, whose graphics architecture the README identifies as AMD RDNA 2, and its recompiler is written against that ISA.
KytyPS5 is GPL-2.0, its source is in this repository, and its build produces a local binary rather than requiring a third-party download. If provenance matters to you, that is the verifiable difference.
Within the Kyty lineage, the README states KytyPS5 is based on a heavily modified version of Kyty. It does not enumerate what changed, so treat the two as related but not interchangeable.
Maintenance, licence and the cost of keeping up
The repository is not archived and the last push was on 2026-10-04, and the most recent releases are dated 2026-11-02. Releases are named after the date and a commit hash, for example KytyPS5-2026-11-02-dfec14a, which means there is no semantic version to pin against and no documented upgrade path between builds. Upgrading means rebuilding from a newer commit and re-testing your titles. The README does not document a rollback procedure, so keep the build directory or the commit hash of anything that works for you.
The licence is GPL-2.0. The repository also contains a LICENSES directory alongside the LICENSE file, and it vendors third-party code under 3rdparty, so a redistribution question is a question about the whole tree rather than one file. This is not legal advice; if you plan to ship a binary, read the licence texts in the repository.
Contribution cost is documented. Pull requests should be focused, name the affected game, describe the exact problem and provide evidence of the fix; general fixes, architectural changes or refactoring that do not address a concrete bug or launch problem in a specific game are automatically closed. Windows and Linux are the primary targets, so shared-code changes should not regress either, while platform-specific changes only need to build on that platform. The README suggests opening an issue before starting a large change, because the codebase is still evolving quickly.
Editorial conclusion
Adopt KytyPS5 if you want to build a PS5 emulator from source, file detailed bug reports with full logs, or work on shader recompilation against the RDNA 2 ISA. Do not adopt it as a way to play a PS5 library: the README states compatibility, stability and performance can vary between versions and that you may encounter crashes or graphical glitches. Before anything else, verify that your GPU and driver expose Vulkan 1.3, because that is a hard build and run requirement rather than a recommendation. Then check the KytyPS5 Compatibility List for the specific title you care about, since the project publishes community test results and the README does not promise anything beyond what that list shows.
Frequently asked questions
How do I install KytyPS5?
There is no documented package install. The README describes building from source with CMake and Ninja, using clang-cl on Windows and Qt 6 for MSVC 2022 64-bit, with separate Building on Linux and Building on macOS sections.
What is the best PC emulator for PS5?
The README does not rank emulators. It states that KytyPS5 is in active development, that compatibility, stability and performance can vary between versions, and that community game test results are in the KytyPS5 Compatibility List.
Will there ever be a PS5 emulator?
KytyPS5 already exists as a PS5 emulator in active development, with releases dated 2026-11-02 and a community compatibility list. The README does not make any claim about future compatibility beyond the current status.
Is PCSX5 safe?
The README says nothing about PCSX5, so this repository does not answer that. It does state that KytyPS5 is not affiliated with Sony Interactive Entertainment or PlayStation and does not distribute games or copyrighted system software.
Can RPCS3 run on PS5?
The README does not discuss RPCS3 or running emulators on PS5 hardware. It only states that KytyPS5 is a PlayStation 5 emulator for Windows, Linux and experimental macOS.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/kytyps5-kytyps5)Star history chart for your README
[](https://hysenlabs.com/projects/kytyps5-kytyps5)Was this useful?