TotK Recomp Cheats (1.4.3 & 1.2.1)
Since version 0.3.1, TotK Recomp reads standard Atmosphère cheat files (<build id>.txt) from your mods folder and lets you toggle individual cheats on the Cheats tab of the in-game F1 menu. This page summarises docs/cheats.md from the repository as checked on November 16, 2026.
Read docs/cheats.md on GitHub Mods & HD texture packs
No cheat files are included. Neither TotK Recomp nor this site hosts or links to cheat packs. A cheat file must match the exact game update you installed (1.4.3, 1.2.1 or 1.1.0); files for other updates are ignored.
1. Where to place the cheat file
Press F1 in game and click Open mods folder on the Mods or Cheats tab (or open the mods folder next to totk.exe). Each mod lives in its own folder under mods and can carry a cheat file in either of two standard paths:
mods\<mod name>\cheats\<build id>.txt
mods\<mod name>\atmosphere\contents\0100F2C0115B6000\cheats\<build id>.txt
Folder and file names are case-insensitive. The file name must be the 16-character hexadecimal build ID of the game update you installed:
| Installed game update | Required cheat file name | Notes |
|---|---|---|
| 1.4.3 | 277178B7DBA1B6D4.txt | Most common update for recent cheat packs |
| 1.2.1 | 9B4E43650501A4D4.txt | Matches 1.2.1 emulator cheat files |
| 1.1.0 | Shown at the top of F1 > Cheats | Added in 0.2.8 / 0.3.1; check the Cheats tab header for the exact build ID |
If a mod folder contains cheat files for other game updates alongside yours, TotK Recomp ignores the other files without raising an error.
2. Cheat file format
An Atmosphère cheat file is plain UTF-8 text made of named blocks:
{Master Code}
040E0000 ...
[Section Name]
[Infinite Stamina]
040E0000 0219C8B4 D503201F
[Cheat Name]— a switchable cheat shown on the Cheats tab in F1.{Master Code}— shared setup code in curly braces. It is built in whenever the file has cheats, runs automatically when any cheat in that file is switched on, and does not appear as a separate switch.[Section Name]— a bracketed header with no hex lines underneath it is displayed as a section divider on the Cheats tab.
3. Code cheats vs memory cheats
Because TotK Recomp translates the Switch game’s ARM64 code into C ahead of time instead of interpreting it in an emulator, it handles memory writes and instruction patches differently:
| Cheat type | What the hex lines do | When it takes effect in TotK Recomp |
|---|---|---|
| Data (memory) cheats | Write values to game variables in RAM (run 60 times a second while enabled) | Immediately when ticked on the Cheats tab; no rebuild or restart needed |
| Key (button) cheats | Run lines inside an 8... block only while you hold a controller button (for example hold B to run faster or R to moon jump) | Immediately if they only write data, or after the one-time rebuild if they patch code |
| Code cheats | Replace an ARM64 instruction inside the game executable (most TotK cheats work this way) | Needs a one-time automatic rebuild (~4 s on a fast PC since 0.4.1, #996). Once compiled into totk.exe inside an if check, you can switch them on and off live during play |
| Restore / Default / Off cheats | Write the game’s original instruction back over a code cheat on a Switch or emulator | Not needed: unticking a code cheat on the Cheats tab already goes back to the original instruction immediately |
| Code-cave subroutines | Write a brand-new ARM64 subroutine into unused executable space and branch to it | Not supported: marked grey on the Cheats tab with the reason |
4. Automatic rebuild for code cheats
When you add a mod or cheat file that contains code cheats not yet compiled into your totk.exe, starting the game opens the installer’s rebuild window automatically:
- Since 0.4.1 (#996), the recompiler uses a lift cache to re-lift only the game functions your code cheats touch and recompiles the changed C files — about 4 seconds on a fast desktop CPU instead of one to two minutes (
TOTK_LIFT_CACHE=0forces a full lift; shaders are not rebuilt). - When the rebuild finishes, the game starts automatically and every code cheat in that file can be switched on and off live in F1 > Cheats.
- Until a new code cheat has been built in, it appears greyed out on the Cheats tab with the note after the rebuild.
Keep your unpacked setup folder (or Linux AppImage). The automatic rebuild runs the compiler from the unpacked TotK-Setup-0.4.1-windows folder or TotK-Setup-0.4.1-x86_64.AppImage you installed from. On Linux, 0.4.1 fixed Rebuild the game now (#560, #403) so the game launches the setup AppImage directly — run the 0.4.1 setup once on your install folder and leave the AppImage in place.
5. Saving cheats in totk.ini
Every cheat you switch on is saved in totk.ini next to totk.exe under the [cheats] section, keyed by a 16-hex-digit hash of its lines so the setting survives even if you rename the cheat or move it to another file:
[mods]
mods_rebuild = auto
[cheats]
cheat_0123456789abcdef = 1
| File or key | Purpose |
|---|---|
[cheats] cheat_<hash> = 1 | Keeps that specific cheat enabled across restarts |
[mods] mods_rebuild = auto | Default. Set to off if you only use memory cheats and never want totk.exe to open the rebuild window at start |
build-cache\cheats.status | Written by the rebuild step; tells the Cheats tab which code cheats are compiled into the current totk.exe and which ones were skipped |
For RomFS mods, HD texture packs (HeapDef) and ExeFS patches, see the main TotK Recomp mods & cheats guide. If the game crashes after enabling a cheat, untick it in F1 > Cheats or remove that cheat line from the configuration file; see troubleshooting.
FAQ
What cheat format does TotK Recomp use?
TotK Recomp reads standard Atmosphère cheat files (<build id>.txt), the same text format used on a modded Nintendo Switch and in Ryujinx or yuzu. No cheats are included with the port.
What is the TotK 1.4.3 and 1.2.1 build ID for cheat files?
For game version 1.4.3 the cheat file must be named 277178B7DBA1B6D4.txt. For game version 1.2.1 it must be named 9B4E43650501A4D4.txt. If you installed 1.1.0, open the F1 menu and check the top of the Cheats tab for the exact file name your installed build reads.
Where do I put cheat files in TotK Recomp?
Inside any enabled mod folder under mods\<mod name>\cheats\<build id>.txt, or in the Switch SD card layout mods\<mod name>\atmosphere\contents\0100F2C0115B6000\cheats\<build id>.txt. Both uppercase and lowercase file names work.
Why does a cheat say “after the rebuild” on the Cheats tab?
Most Tears of the Kingdom cheats modify game instructions rather than data variables. Because TotK Recomp compiles the game’s ARM64 instructions to C ahead of time, code cheats must be compiled into totk.exe once (wrapped in an if check) before you can toggle them live. Keep your unpacked TotK-Setup folder so the automatic rebuild can run.
Do I need “Restore” or “Off” cheats in TotK Recomp?
No. On a Switch or emulator, a code cheat overwrites an instruction in memory, so a separate “Restore” cheat is needed to write the original instruction back. In TotK Recomp, unticking a code cheat on the Cheats tab immediately returns to the original instruction.
Why is a cheat greyed out as unsupported?
Cheats that write a custom ARM64 subroutine into an unused code cave cannot be lifted by the static recompiler and are skipped. In the 0.3.1 release notes, 1 out of 73 cheats in a common 1.4.3 cheat pack used an unsupported opcode and 4 were restore-only.