Unofficial archive — not affiliated with Nintendo, Tropic Haze or the Yuzu team.
Read all of it once, then install

Yuzu setup guide

Yuzu needs two things that don't ship with it: encryption keys and system firmware. This is the yuzu setup, from hardware you own — where to put both, and how to make games actually run at a playable speed.

Keys and firmware are Nintendo's copyrighted data. That's why no archive hosts them. Dumping them from your own console is the clean path and takes about ten minutes with a modded Switch.

Requirements

Hardware

Windows 10 or 11, x86-64, a Vulkan-capable GPU from ~2017 or later. 8 GB RAM minimum, 16 GB sensible.

A Switch

For keys and firmware. Either modded (homebrew launcher), or borrow already-dumped files from someone who is.

Your games

Dumped .nsp / .xci files. Base game, updates and DLC are separate files — Yuzu loads them onto the same title.

No GPU? Integrated Intel HD from before ~2018 will technically boot games. Technically.

1. Install Yuzu

Get the archive

Download the Windows zip. Verify the hash, then extract where you have write access. Avoid Program Files — Yuzu keeps its data next to the binary by default and the folder is read-only.

Launch once

Run yuzu.exe. It will open to an empty game list. Close it again — the folders it needs now exist.

Windows SmartScreen will flag the unsigned binary. "More info → Run anyway" is correct for the hashes listed on this site.

2. Keys

Yuzu decrypts games with prod.keys. Without it, every title fails with "keys not found".

Dump keys from your Switch

Boot a modded console into the homebrew menu and run Lockpick_RCM (payload) — it writes prod.keys and title.keys to sd:/switch/. On firmware 15.0.0+ use a current Lockpick_RCM build; older builds fail on newer keys.

Copy prod.keys into Yuzu's key folder

Only prod.keys is required. title.keys is optional and helps with some DLC.

Windows: %APPDATA%\yuzu\keys

The folder may not exist yet — create it. The file goes inside as a plain prod.keys, not a zip.

Check it

Restart Yuzu. The bottom status bar should stop saying "Keys missing" and list your firmware version instead. Key and firmware versions must match — if the game still complains, redo the firmware step with the same source console.

3. Firmware

Firmware is the Switch's system software. Some games refuse to boot without it, and key/firmware mismatches cause most "corrupted data" errors.

Dump it

On the modded console, use nxdumptool (TegraExplorer script) to dump the firmware to your SD card. This produces a folder or zip of NCA files tied to your key set.

Install it in Yuzu

File → Install Files to NAND, then pick the firmware zip or the folder you dumped. Yuzu unpacks it into its NAND directory and asks for confirmation — accept.

Manual path, if you prefer: %APPDATA%\yuzu\nand\system\contents\registered (Windows).

Restart

Close Yuzu fully and reopen. The status bar should show the firmware version. If it shows "unknown", the dump is incomplete — do it again rather than hunting for a random zip.

4. Add games

Put files in one folder

Keep .nsp/.xci files in a dedicated directory. Don't scatter them across drives.

Add the directory

In the game list, right-click → Add New Game Directory (or File → same), point it at the folder. Yuzu scans and lists titles. Add updates and DLC the same way, then right-click a title → Properties to confirm they attached.

5. Settings that matter

Graphics

API: Vulkan. Accuracy: Normal. Enable ASTC recompression only if VRAM is tight. Resolution 1× on a mid GPU; FSR helps more than raising resolution. Turn on asynchronous shaders — the first minutes will stutter regardless, async just hides it.

CPU

Accuracy: Normal. "Unsafe" buys FPS on some titles and breaks others. Leave multicore on except for games that crash on boot without it off.

Controller

Input → Configure → your pad. Use "Pro Controller" emulation for native layout. GameCube adapters need Zadig/WinUSB first.

Saves

Right-click a title → Open Save Data Location. Back it up before switching between Yuzu and a fork — the formats are usually compatible but not guaranteed.

Troubleshooting

"Keys not found" / games won't boot

Keys are missing, in the wrong folder, or don't match the firmware. Confirm prod.keys sits directly in the keys directory, not inside another folder, and that key version ≥ firmware version.

Black screen, then crash

Nine times out of ten it's a GPU driver or an incomplete game dump. Update the driver, try OpenGL once to isolate, and re-dump the title including its update.

Vulkan not detected

Pre-2017 GPU, missing driver, or a laptop running on integrated graphics. Update the GPU driver from the vendor's site, and force the discrete GPU in Windows graphics settings.

Constant stutter

Shader compilation. Enable async shaders, and accept that the first minutes of a new area stutter. It settles.

Corrupted data errors

Key/firmware mismatch or a bad NSP. Re-dump firmware from the same console as the keys. If it's one title only, re-dump that title.

"The game requires a system update"

Firmware is older than the game. Dump the console firmware after updating it, and update your keys with it.

Still stuck? The FAQ covers the rest, including why some games simply never worked well on 1734.