Quick Answer: TotK PC recomp is a fan project that statically recompiles The Legend of Zelda: Tears of the Kingdom into a native Windows x86-64 app with a Vulkan renderer. It ships no game files. You supply your own legally obtained copy, and the setup builds the game on your machine. Expect about 36 GiB of free space during setup.
Most people who hear "Zelda running natively on PC" assume an emulator is involved. TotK PC recomp takes a different route. It converts the game's machine code ahead of time into native Windows code, then packages that as an application. That changes what you get at runtime, and it changes what you pay at install time. This guide walks through both before you commit a weekend to a build.
What TotK PC Recomp Changes Under the Hood
The core idea is static recompilation. An emulator like Ryujinx translates the Switch's instructions while the game runs, so every frame carries some translation overhead. A static recompiler does that translation once, during the build, and the output is ordinary native code the CPU runs directly.
The graphics side is a different problem. The Switch uses its own GPU stack, and the project credits deko3d, the open-source Switch graphics library, among the work it builds on. On Windows, the renderer targets Vulkan instead, so the game's draw calls get rewritten for a different API.
Here's the counter-intuitive part. Most people assume "native" means lighter and simpler. For this project, the runtime is lighter, but the install is heavier than most games. The build step is where the work happens.
Choosing between the two approaches is a trade-off. Emulators cover a wide range of games and have mature compatibility layers. A recompilation is narrower: it targets one game, and it asks you to accept a long build in exchange for a native binary. If you only want to play this one title on a capable PC, the recomp model is worth the trade. If you want a library of games, it isn't.
Why the Setup Is the Expensive Part
The README lists about 36 GiB of free space during setup, dropping to about 20 GiB once installed. That gap is the build's working space. The setup builds the game once, and it prepares shaders at install instead of while you play.
Here's the cause and effect. Shaders compiled during play are a common source of stutter the first time a new effect appears. Compiling them at install moves that cost out of your play session. The project states this as a design goal. The README doesn't publish stutter measurements, so treat it as the intent and verify it on your own hardware.
Practical tip: if you have a second drive with room, install there rather than on a nearly full system drive. A build that runs out of space partway through wastes the hours it already spent.
Hardware Requirements and Where People Get Stuck
The project lists these requirements:
| Requirement | Listed value | Why it matters |
|---|---|---|
| Operating system | Windows 10 or later | Native Windows x86-64 build; Linux and Steam Deck are planned, not available |
| CPU | x86-64 with AVX2 | Intel Haswell and newer, and AMD Zen and newer, include AVX2 |
| GPU | Vulkan 1.3 and VK_EXT_external_memory_host | The renderer depends on both; missing either blocks the renderer |
| Disk | About 36 GiB during setup, 20 GiB after | Setup needs temporary build space before the install settles |
| Frame rate | 60 fps default; up to 144 fps (experimental) | Higher rates depend on your hardware and are not guaranteed |
The GPU line is the one to verify first. It's easy to skip, and it's the most expensive to discover after a long build. Check your driver's Vulkan support before you start, and update the driver if needed. You don't want to find out after hours of setup.
Installing: The Short Version
The project README describes this sequence:
- Download the
TotK-Setup-<version>-windows.zipfile from the project's Releases page and unpack it. - Run
TotK-Setup.exe. If SmartScreen warns about an unsigned app, choose More info, then Run anyway. - Point the setup at your own game files, choose a language and an install folder, and start the build.
- Launch
totk.exefrom the install folder.
Updating works the same way. Run a newer setup against the same folder, and saves and settings carry over. The project supports the base game with the 1.2.1 or 1.4.3 update. Back up your save data before a major update anyway. It costs you nothing, and this project is still in early development.
Controls, Menus, and Upscaling
The features most players will touch first are:
- In-game settings menu on F1 and a performance overlay on F10
- Keyboard, mouse, and gamepad support with remapping, rumble, and gyro
- Custom resolutions such as 1080p and 2K
- Supersampling, which renders above your display resolution and costs GPU time
- AMD FSR 1 upscaling, which is a spatial upscaler rather than a temporal one
FSR 1 is the cheaper option, and it doesn't use motion data from previous frames. That means it can look sharper than a simple stretch but still softer than native rendering at the same output size. Supersampling looks better on paper but costs more GPU time. The choice depends on whether your GPU has headroom or is already the bottleneck.
Known Limits, Planned Features, and Risks
Here's where most guides go wrong: they describe a project's goals as if they were its current state. The README is direct that the game is playable on Windows, but visual bugs and crashes are still expected. Treat the first few sessions as testing, not as finished play.
Several features are planned but not available: Linux and Steam Deck support, mods made for emulators through a mods folder, custom aspect ratios including ultrawide, and variable refresh rate. The 144 fps mode is experimental.
The README also says most of the code and documentation was written by AI coding agents under the maintainer's direction, and the maintainer plays every build and decides what gets merged. That's a fact you should weigh. The practical response is to test it yourself and report problems through the project's CONTRIBUTING.md process rather than trusting the codebase on reputation.
Legal Boundaries You Need to Respect
This section matters more than the rest, so read it carefully. The project includes no game files. The README says you need your own legally obtained copy of the base game and the 1.2.1 or 1.4.3 update, dumped from your own console. The project won't provide instructions for obtaining those files, and neither will this article.
Does an open-source license make the game free to use? It doesn't. The project's MIT license covers its own code, and the README states that the license grants nothing for Nintendo's game. Because the build contains the game, the output is for your personal use, and the README asks you not to share it. The project is an independent fan effort, not affiliated with or endorsed by Nintendo.
Frequently Asked Questions
What is TotK PC recomp and is it an emulator?
TotK PC recomp is a fan project that statically recompiles Tears of the Kingdom into a native Windows x86-64 application. It isn't an emulator. Instead of translating instructions while the game runs, it translates the game's code once during the build. You still need your own legally obtained copy of the game to run it.
How do I install TotK PC recomp on Windows?
Download the setup zip from the project's Releases page, run TotK-Setup.exe, and point it at your own game files. Choose a language and install folder, then start the build. Make sure you have about 36 GiB free during setup, and launch totk.exe when the build finishes.
Why does the TotK PC recomp setup need so much disk space?
The setup needs temporary build space before the game settles at about 20 GiB. It builds the game once and prepares shaders during installation. That trades a long, heavy setup for less shader compilation during play, which is the design goal the project describes.
Is TotK PC recomp legal to use?
The project includes no game files, and its MIT license covers only its own code. You need your own legally obtained copy of the game. The README asks you to use the result for personal purposes only and not to share it. This article can't give legal advice, so check your local rules if you're unsure.
Try This Before You Commit
If you're weighing TotK PC recomp, start with the GPU check: confirm Vulkan 1.3 and VK_EXT_external_memory_host support. Then free up about 36 GiB on a drive you're happy to use for the build. Once it runs, note your frame rate on the F10 overlay and log any crashes as issues, following the project's CONTRIBUTING.md. That feedback is what moves a project like this from early development toward a stable release.