SharpEmu is an experimental C# PS5 emulator. Start at its official GitHub repository and read results in the context of a specific release, rather than treating selected game images as a supported-game list.
Source snapshot checked on October 14, 2026. Releases and the default branch are recorded separately; upstream development may have moved on.
Which SharpEmu sources are official?
The verified repository is sharpemu/sharpemu. Its pinned README identifies sharpemu.app and repository-listed links as affiliated channels. A similar-looking domain or a download carrying the name is not enough to establish affiliation.
Release and commit record
- Latest checked release
- v0.0.5-nexus-release.2 — October 8, 2026, 22:58:53 UTC
- Release commit
47d4c07a8d3035a269ce404b74ffdc71c962b019- Latest checked main commit
d113a3722de2029cd99cc007d320208bdf36aa40— October 14, 2026, 23:22:41 UTC
The release has Windows x64, Linux x64, and macOS x64 assets. The later main commit is a development snapshot; its changes should not be attributed to the October 8 binary automatically.
What the release evidence actually says
ASTRO’s PLAYROOM: rendering work, with performance limits
The release notes include merged PR #1030. The developer lists a test of ASTRO’s PLAYROOM, corrections for incomplete or black-region rendering, and continuing heavy performance. The report gives no hardware configuration, numeric FPS, test duration, or completed-playthrough result.
Demon Slayer 2: unresolved black output
The same release includes merged PR #1069, whose developer report says “Demon Slayer 2” still produces black output after reaching an in-game state. We retain the upstream’s title wording and do not infer a precise game revision or a playable rating.
These observations are first-party developer reports linked by release notes. They are not tests performed by PS5 PC Desk. The comparison page shows their evidence type separately from direct release-note checkpoints.
Before downloading or building
SharpEmu documents x64 hosts, Vulkan output on Windows and Linux, and MoltenVK on macOS. Apple Silicon can use the macOS x64 build through Rosetta 2. Check current graphics drivers and the platform instructions before selecting an asset. Source builds require the .NET SDK version named in that build’s global.json.
- Open the verified release and select an asset matching your operating system and architecture.
- Read the instructions accompanying the same build; use only game files you are entitled to use.
- If the publisher provides a SHA-256 checksum, compare it with the local download checker.
- For a problem report, record your exact build, hardware, driver, game revision, and the stage reached. Use the upstream’s current reporting template.
What not to infer from the changelog
A shader fix may repair one rendering path while another part of the game remains broken. A listed revert can remove an earlier change. The reviewed release includes reverted changes, so counting individual commit titles as a tally of working games would be misleading.
Compare Kyty and its derivative, the identifiable PCSX5 source project, and AnyPS5 by their own sources and implementation.