Moving from Yuzu to Eden: bring your keys, games and saves across (without re-dumping)

Your Yuzu prod.keys and firmware work in Eden unchanged — copy them across as-is. This is the step that gets games booting again and the single biggest "do I have to re-dump?" relief: no, you don't.

1. Find your existing keys. In your old Yuzu install they live in the keys folder (open it from Yuzu's File → Open Yuzu Folder → keys if Yuzu still launches, or browse to %APPDATA%\yuzu\keys). You're looking for prod.keys and, if present, title.keys.
2. Drop them into Eden's keys folder. Open Eden's user folder from its own menu (File → Open … folder) and place prod.keys (and title.keys if you have it) into the keys subfolder — create it if it isn't there. The filename must stay exactly prod.keys, all lowercase, no extra extension.
3. Firmware carries over too. The Switch system firmware you dumped for Yuzu is the same firmware Eden needs. If you kept the firmware dump, install it through Eden's own menu (Tools → Install Firmware) rather than copying files by hand. Keep firmware and keys from the same console state — a mismatch is a common cause of "moved over but games still fail."
4. Reload keys / restart Eden. Your installed games should stop being greyed out. If keys still show as missing, the file is almost certainly misnamed (prod.keys.txt with a hidden extension) or in the wrong folder — see our prod.keys / firmware fix guide.

Eden shows an empty game list because it doesn't inherit Yuzu's library path — just point it at the folder your games already live in. The game files themselves are untouched; nothing needs re-dumping.

1. Your dumps haven't moved. The .nsp / .xci files you dumped for Yuzu are still sitting in whatever folder you kept them in. Migration doesn't touch them.
2. Add that folder in Eden. Use Eden's Add New Game Directory (double-click the empty list, or File → Add Game Directory) and select the same folder Yuzu was reading. Eden scans it and your library reappears.
3. Multiple folders are fine. If your games were spread across more than one directory in Yuzu, add each one — Eden supports multiple game paths just like Yuzu did.

This is the one step where "copy everything" goes wrong. Your save data can come across, but the shader / pipeline cache must NOT — copying it from an old Yuzu build into Eden is a frequent cause of crashes, graphical glitches, and shader-compile errors. Leave it behind and let Eden rebuild it.

1. Why the cache is different. Eden's Vulkan pipeline parameters have changed from old Yuzu builds, so a shader cache compiled by Yuzu can be incompatible. Eden even added menu options to clear OpenGL / Vulkan caches per-game precisely because stale caches cause problems. The safe move is to start with a clean cache.
2. What this costs you: the first time you run each game in Eden it may stutter briefly while shaders recompile, then smooths out. That's normal and one-time per game — far better than chasing crashes from a transplanted cache.
3. Saves can migrate. Your game save data lives in Eden's/Yuzu's save directory (under the emulator's nand user data, reachable from Open … folder). If you want your progress, copy the save folder structure across; if anything behaves oddly afterwards, the cleanest fallback is to use the game's own in-emulator save rather than forcing the old files. Back up before you copy either way.
4. If a game misbehaves after migrating, clear that title's shader cache in Eden first (right-click the game → Remove → shader caches) before assuming the save or the dump is at fault.

Don't wait for a one-click config import — Eden starts on its own defaults. Re-setting the handful of settings that actually affect you is a two-minute job, not a re-dump.

1. Why nothing imported. Eden's separate data folder means it doesn't read Yuzu's config. That's by design, not a fault — your settings simply start at Eden's defaults.
2. Set graphics first. Re-pick your graphics API (Vulkan for most NVIDIA/AMD setups; OpenGL where Vulkan is unstable), your resolution scale, and docked vs handheld mode. These have the biggest visible impact and are where most people notice "it looked better in Yuzu" until they match the settings.
3. Re-map your controller. Input bindings don't carry over — set your controller up once in Controls. If a pad isn't detected at all, that's a separate input issue, not a migration problem.
4. Leave the rest on defaults. Eden's defaults are sensible; only change CPU/advanced graphics toggles if a specific game needs it. Resist copying every Yuzu tweak blindly — some old workarounds are unnecessary or counterproductive on Eden.

Not sure Eden is the right successor to be on in the first place, or coming from Citron/Sudachi instead? Read the 2026 Switch-emulator guide for which actively-maintained build is the safe choice this year.