A real-time modding tool for jailbroken PS5 consoles that runs in a web browser. Load one small payload on the console, open a page on your phone or computer, and switch cheats on, or find and make your own.

Use at your own risk. CheatSpecter changes the memory of a running game, which can crash it or damage a save. It has only been tested on a Jailbroken 13.60 PS5. What you do with it is your responsibility.

Quick start

You need a jailbroken PS5 that can load ELF payloads, with ps5debug-NG running, and any device with a browser on the same network. Prerequisites has the details.

Download cheatspecter-v<version>.elf from the Releases page.
On the PS5, start ps5debug-NG (etaHEN can start it from its toolbox).
Send the ELF to the console the way you load any payload, for example by uploading it in a payload manager.
A notification on the TV shows an address. Open it in a browser on the same network: http://<PS5 IP>:8744
Start a game. Cheats made by the community for that game appear as switches on the Cheats tab. To make your own, press Guide me through my first cheat.

Your cheats are saved on the PS5 by themselves as you make them, and open from there the next time the game runs. Save downloads a copy to the device you browse from. (New in 0.4.3, beta.)

The payload has to be loaded again after each reboot, like any payload. Nothing is installed on the device you browse from. To stop it without a reboot, open the page from the PS5's address, press Settings (the gear at the top) and choose Shut down CheatSpecter on the PS5 (beta).

No console to hand? npm install && npm run demo runs the app against a pretend PS5 so you can click around. See Installation for that and for running the app from a computer instead of the console.

What it does

Use cheats

Community cheat tables for the running game are looked up online and shown as switches. Before a cheat is switched on, the game's memory is compared with what the table expects, so a cheat for the wrong version is left off instead of corrupting the game.
The game's cheat file on the PS5 opens first, without waiting for the internet. A community table made for exactly your version of the game is saved into that file, so next time it opens from the PS5 with no download. Check for updates shows what changed online before anything is replaced. (beta)
Your own cheats are saved on the PS5 as you make them. Save downloads the game's .cspector file to the phone or computer you are using, and Delete from PS5… (in the file's … menu) removes it from the console after asking. (beta)
Cheat files that etaHEN, elf-arsenal or GoldHEN keep on the console are listed as On this PS5 and can be used like the online tables. (beta)
Game patches from the PS4-PS5-Game-Patch collection (frame rate, resolution and the like) as switches, for the exact version they were made for. (beta)
A start set: the cheats to switch on each time the game starts. You can still switch them off as usual. (beta)
Mark a cheat Keep on and the PS5 holds it on the whole time the game runs, with no browser open.
Crash protection: a cheat switched on less than a minute before the game closed is marked, and is not switched on by itself again until you switch it on by hand. (beta)
Restore everything puts back every change in one go.
The TV shows a short notification when a cheat is switched on or off.
Your game library, with a Start button for each game.

Get around

A controller shortcut, off until you switch it on: hold L2 + R3 (or buttons you pick) and the PS5's own browser opens on the game's cheats. (beta)
The address in the browser follows the screen, so Reload, Back and a saved link land where you were (for example #/game/PPSA01234/cheats). (beta)
Settings, from the gear at the top of every screen: the controller shortcut, Diagnostics (a log you can copy or save to send with a bug report), and Shut down CheatSpecter on the PS5. (beta)

Make cheats

Find a value: a number you can see, a bar with no number, text, several values that sit together, or whatever changed between two moments.
Find the code that changes it, and switch that code off: a cheat that lasts across restarts, and can be made to survive game updates.
Code cheats with decisions ("only for the player"), built from a plain rule or written in assembly with labels and variables, and scripts in JavaScript. Scripts can search the game's memory for a value (cs.search) and read text (cs.readText). (beta)
Debug: pause the game, set breakpoints, step, read and change registers, and compare objects field by field.
Engine names: for Unreal, Unity, Godot and GameMaker games, and C++ games that keep class names, objects and fields are shown by name.

Learn

Twelve short lessons with a practice game that runs in the page, so every step can be tried with no console and no risk to a real game.

Documentation

The wiki has the full guide:

To do this	Read
Check what you need	Prerequisites
Install on the PS5 or run from a computer	Installation
Make a first cheat	Your first cheat
Use every kind of search	Finding values
Save, group, share and keep cheats on	Making and managing cheats
Use frame-rate and resolution patches	Game patches
Open CheatSpecter from the controller	Controller shortcut
Send a log, or stop CheatSpecter on the PS5	Settings and diagnostics
Write code cheats and scripts	Code cheats and scripts
Pause, step and inspect	Debugging
See class and field names	Engine helpers
Use it from Claude	MCP server and its tool reference
Read or write `.cspector` files	The .cspector format
Fix a problem, or avoid a crash	Troubleshooting and safety
Understand how it works, or build it	Architecture and Building from source

What has been tested on a real PS5

CheatSpecter is young, and this list is kept honest.

Used on a real console (firmware 13.60, ps5debug-NG 1.3.2), as of 0.3.0: finding the running game with its name and icon, the game library, loading community tables, known-value searches, "what writes to this", byte patches located by offset and by pattern, and saving and auto-loading .cspector files on the console.

Everything new in 0.4.3 has not been tested on the console yet and is beta. That is the cheat file opening from the PS5 first, community tables saved into it, the new Save and Delete from PS5, the start set, cheat files already on the console, game patches, crash protection, the controller shortcut, Settings and Diagnostics, links that survive a reload, and the script and MCP server additions. It passes the automated tests against the simulated console, and is marked (beta) above.

Tested only against the built-in simulated console so far: everything new in 0.4.0 (the Debug and Engine tabs, code cheats, text and grouped search, cheats the PS5 keeps on by itself, section "master code" cheats, the Learn page), and from earlier versions: function calls, scripts, the pointer-path search, unknown-value searches, starting a game from the library and PS4 titles. That is why 0.4.0 is published as a pre-release. CHANGELOG.md has the detail for each version.

Where cheat tables come from

Tables are read at runtime, by your browser, from these community collections in their original location. Nothing from them is copied into this repository.

All three formats they publish are read: JSON, SHN and MC4. A table made for exactly your version of the game is converted and saved into that game's cheat file on your PS5 the first time it is opened, so it keeps working with no internet.

Game patches come from PS4-PS5-Game-Patch, read the same way, by your browser.

Contributing

Bug reports, lessons and code are welcome. Start with CONTRIBUTING.md. To report a security problem privately, see SECURITY.md.

License

GPL-3.0-only, matching ps5debug-NG, whose protocol this implements and whose handler logic the simulated console follows. See LICENSE.