Yuzu's Shutdown Reshapes Switch Emulation, Forks, and Preservation Efforts

The $2.4 million settlement that forced Tropic Haze LLC to shut down Yuzu and Citra in March 2024 did not end Nintendo's campaign against Switch emulation. It opened one. Two years later, the landscape looks fundamentally different: Ryujinx is gone, at least five named Yuzu forks including Suyu, Sudachi, Torzu, Uzuy, and Nuzu have been hit with DMCA takedowns on GitHub, Lockpick_RCM has been scrubbed from public repositories, and every remaining active project has had to make explicit decisions about where to host code and how visibly to operate.

Nintendo sued Tropic Haze LLC on February 26, 2024. Lead developer Bunnei settled within a week, agreeing to a permanent injunction that shut down Yuzu's website, Discord, Patreon, and GitHub repositories effective immediately. Citra followed despite not being named in the original lawsuit. Within hours of the announcement, forks appeared: Suyu went live the next day, Sudachi shortly after, with several others quickly following. Nintendo's legal team responded systematically, issuing DMCA notices that removed Suyu from GitLab, killed its Discord presence, and eventually pushed the project to a self-hosted Forgejo instance before Suyu announced its own cessation of development on February 13, 2025. Ryujinx, the other major Switch emulator and the one most openly focused on accuracy, was removed from public repositories after lead developer gdkchan was contacted directly by Nintendo's lawyers. No settlement amount was made public, but the outcome was the same.

The 2026 DMCA wave then swept up the remaining named forks in one coordinated pass. The only Yuzu derivative to avoid sustained takedowns is Torzu, which moved its primary repository to a Tor-based hidden service. Because Nintendo's DMCA notices depend on hosting providers acting on copyright claims, a .onion address largely sidesteps that mechanism, at the cost of discoverability, contributor friction, and any presence on mainstream platforms.

That leaves two emulators with real development momentum in 2026: Eden and Citron. Eden, a Yuzu derivative that launched in pre-alpha in May 2025, became the first Switch emulator accepted onto the Google Play Store, giving it a degree of institutional legitimacy that earlier forks never achieved. Its January 2026 release added macOS and Android/x86_64 support alongside game-specific fixes. Citron developed its own identity through cross-collaboration with both Eden contributors and former Ryujinx developers, with its v0.10.0 update explicitly crediting contributions from both teams. Neither project is legally risk-free, but both are operating with more caution than Suyu did.

The impact on day-to-day users varies sharply. For players who just want to run owned games, workable options exist, though the landscape narrowed and got noisier. For compatibility researchers and documentation contributors, losing Ryujinx hurt worst: that project's work was methodical, well-attributed, and accuracy-oriented in ways most Yuzu forks never fully replicated. That compatibility data is now scattered across community wikis and partially lost.

For preservationists, the situation is genuinely harder. The key-dumping workflow most people relied on ran through Lockpick_RCM, now absent from centralized repositories. A legal path to your own prod.keys and title.keys currently requires an unpatched V1 Switch, a RCM jig, Hekate as bootloader, Atmosphère as custom firmware, and Lockpick_RCM sourced through community channels rather than GitHub. If you have a patched Switch model, CFW is not an option, which means legal key dumping is not possible on that hardware. That limitation predates all of this, but it matters more now that the documentation and tooling around it is more dispersed and harder to find.

Here is what a defensible preservation workflow currently looks like. Start with an unpatched V1 Switch running Atmosphère. Lockpick_RCM produces your prod.keys and title.keys, which go into the appropriate directory of your emulator. NXDumpTool handles game dumps, exporting cartridge or eShop titles as XCI or NSP files. The critical habit, and the one the preservation community is increasingly pushing, is dumping base game, update, and each DLC as separate verified files with correct hashes rather than merging them at dump time. Merged containers are harder to verify later and easier to corrupt. Store everything with checksums.

That last point reflects the broader shift in how serious preservation work is now understood. The community conversation accelerating through the 2026 DMCA actions has pushed archivists toward provenance-aware practice: complete metadata, firmware version documentation at dump time, hash verification, and clear separation of base title from updates and DLC. Raw file dumps without that context are significantly less useful for institutional archiving, and institutions, including universities and digital libraries, are increasingly the realistic long-term homes for software preservation work. Evidence-grade archiving is not just more defensible legally; it is more durable across the decades that preservation actually requires.

What you should not do is source prod.keys or game files from sites that bundle them together for download. Keys derived from a specific Switch console are not transferable in any legal sense, and sites offering them are using keys extracted from someone else's hardware. Using keys from your own device to run your own purchased games is the only workflow with any legal defensibility, and conflating that with site-distributed keys is the fastest way to put yourself and any preservation project you contribute to in legally precarious territory.

For emulator choice right now, Eden is the pragmatic option for most users on Windows, Linux, and Android, given active development and wide hardware compatibility. Citron is worth tracking for anyone specifically interested in accuracy improvements and the cross-project collaboration between its team and contributors carrying forward Ryujinx's work. Torzu remains functional via its Tor repository but is a maintenance project rather than an actively developed one. Neither Suyu nor Sudachi should be considered viable for new setups.

The post-Yuzu ecosystem's real problem is not a shortage of emulators. It is the fragmentation of the infrastructure that made Switch emulation coherent: centralized compatibility tracking, shared documentation, stable tooling, and accessible key-dumping workflows. The forks that survived 2024 and 2025 kept the bytes running. Rebuilding the institutional layer around them is the slower, less glamorous work, and it is where the preservation community's attention needs to go now.