TotK Recomp

PC port of The Legend of Zelda: Tears of the Kingdom

  • RecompilationPort Type
  • Valiantsin DzerakhDeveloper
  • 15 Nov 2026Page Updated

Details

Developer
Valiantsin Dzerakh
Port Type
RecompilationA tool translated the game's original machine code into C automatically, which was then built as a native PC program.
AI Use
Mostly AI-builtThe project says: “Most of the code and documentation is written by AI coding agents (Claude Code) under the maintainer's direction; the maintainer plays every build and decides what is merged.” Source
Logo
AI-made fan logo, free to use · Full size
Source Code
GitHub
Page Updated

Platform Support

Screenshots

What you need: Your own Tears of the Kingdom dumped from your own Switch: the base game and the 1.1.0, 1.2.1 or 1.4.3 update. Windows 10 or later, or Linux 6.7+ with glibc 2.34+ (Ubuntu 22.04, Debian 12, Fedora 35, SteamOS 3); an x86-64 processor with SSE4.2, a Vulkan 1.3 graphics card with VK_EXT_external_memory_host, and about 36 GB free during setup (20 GB after).

Overview

WidescreenHigh Frame RateHDRMod Support

TotK Recomp turns The Legend of Zelda: Tears of the Kingdom into a native x86-64 program for Windows and Linux by static recompilation. The setup builds the game from the player’s own dumped files on their own computer, so the result contains the game and is meant only for that player. It is in early development: the game can be played, but visual bugs and crashes are still expected.

It runs at 60 fps by default, or experimentally up to 144 fps or the monitor’s refresh rate, at custom resolutions with supersampling and FSR 1 upscaling, and in 16:10, 21:9 and 32:9 with the camera and interface reshaped to fit. HDR10 output, 16x anisotropic filtering and shaders prepared during setup rather than during play are included, and updates 1.1.0, 1.2.1 and 1.4.3 are supported, with saves carried between the last two.

Keyboard, mouse and gamepads can be remapped, with rumble, gyro and Xbox button prompts. An in-game menu (F1) holds the settings and F10 a performance overlay. Mods made for emulators work from a mods folder, including RomFS mods and ExeFS code patches, and Atmosphère cheats can be switched on in the menu.

How to Set It Up

  1. Download the setup zip for Windows and extract it, or download the AppImage for Linux and make it executable (on a Steam Deck, in Desktop Mode).
  2. Start TotK-Setup.exe (or the AppImage). If SmartScreen warns about an unsigned app, choose More info, then Run anyway.
  3. Pick your game files, the language and an install folder, and press Start. The setup builds the game once on your PC.
  4. Play totk.exe (on Linux, totk) from the install folder. To update, run a newer setup on the same folder; saves and settings are kept.
Go to Downloads

Advertisement

Download TotK Recomp

What's new in v0.4.1

To update, run the new installer on your existing install folder. It keeps your game files, saves and totk.ini, and rebuilds totk.exe and the shaders.

Watch out

I have not tested the Linux build myself. DLSS is tested by the community only: I don’t have the hardware for it.

Note

If something got worse. Change one at a time (the settings menu, F1, or totk.ini), restart the game and check the same place. Then open an issue with logs/totk.log attached and say which switch helped.

  • FPS falls after 5-10 minutes of play and a restart brings it back (#1174). Add addr_report = 0 under [diagnostics] in totk.ini.
  • Graphics artifacts, wrong textures or colours: memx = 0.
  • AMD on Windows, new holes or noisy edges on foliage, fences or hair: start the game with the environment variable TOTK_DEMOTE=0.
  • HDR colours look wrong: hdr_hue = 0.
  • Objects, Recall or Ultrahand behave oddly: optref_guard = 0, ability_guard = 0 or report_guard = 0. Each turns off a crash guard, so the crash it stops can come back.

Experimental: the Linux PGO build and settings that are off by default.

Experimental Linux build with PGO. TotK-Setup-0.4.1-x86_64-pgo.AppImage is built with profile-guided optimisation, as the Windows installer is. On Windows PGO gives 6-12% more FPS, and the Linux build should gain about as much, but nobody has measured it on Linux yet. If it misbehaves, use TotK-Setup-0.4.1-x86_64.AppImage. Please report your FPS with both builds in an issue.

Settings. These switches can give more FPS on some PCs and do nothing or harm on others. Set them in the Advanced tab of the settings menu (F1) or in totk.ini under [performance]; they take effect at the next start unless noted. Try one at a time and compare the FPS at the same place. If one breaks something, set it back to its default and tell us in an issue with logs/totk.log attached.

  • replay_workers = 4: record the GPU commands on several threads. Each large submission is recorded in chunks on this many threads (0 to 16). In a town at 4K on an RTX 5070 the replay went from 8.2 to 4.5 ms a frame (71 to 79 fps); more than 4 threads add little. Needs 8 or more logical processors. No gain where the game’s own threads limit the frame (a Ryzen 7900X at 1080p). This release fixes the freeze and the chunk_record crash it caused (#1104).
  • sync_ahead = 1 with shadow = 1: one frame ahead of the GPU. The game builds the next frame while the GPU still draws the previous one. On Great Sky Island (Linux, RX 9070 XT) this took about 73 to 100 fps. Costs one more frame of input delay, frame times vary more, and GPU results the game reads back (occlusion queries) can be a frame old, so an object can pop in a frame late. On native Windows it needs shadow = 1 (on by default on Linux and Wine): a copy of the game’s GPU-visible memory, about 0.2 ms a frame and 1.1 GB more memory. Helps most where the game waits for the GPU. Works on 1.2.1 and 1.4.3.
  • replay_async = 1: the GPU replay on its own thread. Runs the replay at most one frame behind the game. Helped a GTX 1650 in the Depths, where the game waits for the GPU; on a GTX 1660 Ti at the 60 fps limit it made motion uneven (#659). Up to one frame more input delay.
  • bind_inc = 1: rebuild only what changed between draws (#381). The draw thread rebuilds only the bindings, shaders and pipeline state whose inputs changed since the previous draw: about 3% less time on that thread in a town (Ryzen 7900X limited to 4 cores). One GTX 1050 Ti lost the GPU (“device lost”, -4) with it at one place in the world, and the cause is not found yet. If you get -4 with it, please attach logs/totk.log.

…

Setup for Windows v0.4.1 · Download
SHA-256 5b1ebd4285167e80ec0a7ee2a5c0ec85540cbeea8c83234067a76f83f7a33ee8
Setup for Linux (AppImage) v0.4.1 · Download
SHA-256 5edc6c9623419fbfde83c7e7fd7b9e00bb604c5291a27b200faedfd3581e68c1
Source code for v0.4.1 (.zip)
SHA-256 85da77b3651415e1534dda90174fc0065d11406049826de6b19baa3afd86da55

Follow new builds by RSS

TotK Recomp Archive

Show all 14 older builds