Nintendo has launched another major crackdown on Nintendo Switch emulators, with more than 400 related repositories reportedly removed from GitHub in a single coordinated takedown campaign. The action targeted a wide range of projects, including the Yuzu successor Suyu, several Yuzu forks, and the Android-focused emulator Skyline, even though some of these projects had already been discontinued.
The latest development was reported by TorrentFreak, which found that Nintendo submitted seven DMCA anti-circumvention notices to GitHub on the same day. The notices collectively affected more than 400 repositories, demonstrating the scale of Nintendo’s continuing effort to remove Switch emulation projects and their surviving forks from the platform. The biggest target was Suyu, whose network alone accounted for 311 repositories.
Nintendo Targets Suyu, Yuzu Forks, and Skyline
Suyu was the most heavily affected project in the latest GitHub sweep. The emulator emerged as one of the prominent successors to Yuzu after Nintendo’s legal action against the original emulator project in 2024, and GitHub processed the notice across a network containing 311 repositories.
The other takedowns affected 29 repositories connected to Skyline, an independent Nintendo Switch emulator designed for Android, along with multiple Yuzu forks and related projects. These included a Yuzu fork network containing 14 repositories, an Android port with eight repositories, an Early Access build with 21 listed forks, and 17 forks connected to MonoNX.
Skyline is particularly notable because its original developers had already discontinued the project in 2023. However, the open-source code continued to exist through mirrors and forks, making it a target in Nintendo’s broader campaign against Switch emulation repositories.
Most of the affected repositories are now offline, with some GitHub pages displaying removal notices while others return errors indicating that the repository may have been voluntarily removed after receiving a complaint.
Nintendo’s DMCA Argument Centers on Switch Encryption
Nintendo’s legal argument across the notices is based on alleged circumvention of the technological protection measures used to secure Nintendo Switch games. The company argues that the emulators require unauthorized copies of proprietary cryptographic keys to decrypt Switch games.
The notice states that
“the emulators at the reported repositories necessarily use unauthorized copies of these cryptographic keys to decrypt unauthorized copies of Nintendo Switch games, or ROMs.”
Nintendo therefore maintains that distributing such software violates the DMCA’s anti-circumvention provisions.
The company has used similar arguments in previous actions against Switch emulators and emulator forks. GitHub’s published DMCA records show Nintendo repeatedly describing Switch game encryption and the use of proprietary keys as the basis for its anti-circumvention complaints.
The latest sweep also follows a broader escalation earlier in 2026, when Nintendo reportedly went after a much wider range of Switch emulator projects hosted on GitHub. That campaign included both active projects and discontinued emulators, suggesting Nintendo’s focus extends beyond stopping ongoing development.
Removing the Repositories Does Not End the Problem
While Nintendo has succeeded in getting hundreds of repositories removed, the latest action highlights the difficulty of permanently eliminating open-source code from the internet. Projects that disappear from GitHub can survive through forks, mirrors, archives, and hosting platforms outside the company’s control.
That pattern has already defined Nintendo’s fight against Switch emulation. Yuzu shut down following its 2024 legal settlement with Nintendo, while Ryujinx later ceased operations. Yet forks and successor projects continued to emerge, prompting repeated takedown efforts.
Nintendo’s latest GitHub sweep may have removed a major collection of public repositories in a single day, but it is unlikely to be the final chapter in its battle against Switch emulators. As long as archived code and new forks continue to surface online, the company may face the same challenge again: removing a repository is relatively straightforward, but preventing the code from reappearing elsewhere is much harder.
