Nintendo removed 401 Switch emulator repositories from GitHub in a new DMCA wave targeting Suyu, Skyline, MonoNX, and Yuzu forks. Here is how it fits Nintendo's wider anti-piracy strategy.
Image: gamerant.com
Nintendo’s latest GitHub sweep lands on 401 repositories
Nintendo has filed another wave of DMCA anti-circumvention notices against Switch emulator code on GitHub, and the immediate result is concrete: 401 repositories are now offline, according to TorrentFreak’s August 21 report and follow-up coverage from VGC, Nintendo Everything, and GameSpot.
The notices were not aimed at a single abandoned project page. TorrentFreak reports that Nintendo filed seven separate notices at GitHub on the same day, targeting Switch emulator repositories and their forks. VGC says all 401 removed repositories contained Switch emulators, while Nintendo Everything says most of the affected code repositories are now offline.
That number matters because this is no longer a one-off cleanup after the collapse of Yuzu. It is a recurring enforcement pattern. Nintendo is going after the copies, successors, forks, Android ports, and archived code paths that keep appearing after headline emulator projects shut down. The tension for emulator developers is obvious: even if a flagship project disappears, the code economy around it can remain visible, searchable, and forkable on GitHub, which gives Nintendo a map for the next takedown wave.
Suyu was the main target, but the notices reached wider
The largest single target in this round was Suyu, a Yuzu successor that became popular after Yuzu’s collapse. TorrentFreak reports that because the Suyu network was larger than 100 repositories, GitHub processed Nintendo’s notice against the full network, covering 311 repositories. VGC gives the same core figure: 311 of the 401 removed repositories contained Suyu.
The remaining notices reached several other Switch emulator projects or Yuzu-derived code bases. TorrentFreak identifies Skyline, an independent Android Switch emulator, as a 29-repository full-network target. It also lists a Yuzu fork with 14 repositories, liushuyu/yuzu-android with 8 repositories, exverge-0/yuzu-EA4176 with 21 listed forks, irlbunny-archive/MonoNX with 17 listed forks, and one Yuzu fork where only the parent was listed. Nintendo Everything also names Suyu, Yuzu forks, and Skyline among the impacted projects, while VGC adds MonoNX and numerous forks that used Yuzu as a starting point.
There is a useful distinction here between confirmed scope and broader inference. The confirmed scope is GitHub repositories named or processed through these seven notices. The broader signal is that Nintendo is prioritizing network cleanup, not merely the original parent project. Forks and ports appear to be treated as part of the same risk surface when they preserve Switch emulation functionality that Nintendo argues depends on bypassing its protections.
Nintendo is leaning on anti-circumvention, not ordinary moderation language
Nintendo’s legal theory in these notices is specific. According to the quoted notice text published by VGC, Nintendo Everything, GameSpot, and TorrentFreak, the company says the reported repositories “offer, link to, or otherwise provide access to Nintendo Switch emulators.” Nintendo argues that those emulators are primarily designed to play Switch games and “illegally circumvent Nintendo’s TPMs in order to run illegal copies of Nintendo Switch games.”
The notices focus on the Switch’s encryption system. Nintendo says Switch games are encrypted with proprietary cryptographic keys, identified in the notices as prod.keys, which protect against unauthorized access and copying. The company’s position is that, during operation, the emulators at the reported repositories necessarily use unauthorized copies of those keys to decrypt unauthorized copies of Switch games or ROMs at or immediately before runtime.
That framing is important for anyone following Nintendo Switch emulator takedowns because it moves the argument away from whether a repository directly hosts a Nintendo game. Nintendo is saying distribution of the emulator technology itself constitutes unlawful trafficking when it is primarily designed to circumvent a technological protection measure under the DMCA. That is Nintendo’s claim, not a fresh court ruling on these seven notices. GitHub’s takedown handling shows the notices were effective on the platform, but the source material does not show these 401 repositories litigating Nintendo’s argument in court.
This wave follows the Yuzu collapse and a much larger 2024 GitHub removal
The latest Nintendo GitHub emulator repositories sweep fits a campaign that has been escalating since the Yuzu case. TorrentFreak says Yuzu settled in 2024, while GameSpot describes Yuzu as shutting down in March 2024. The source material does not align perfectly on the month, so the safest reading is that Yuzu’s legal resolution and shutdown happened in that early 2024 window, after Nintendo targeted the project behind one of the best-known Switch emulators.
Nintendo’s campaign then moved to GitHub at large. VGC reports that in May 2024 Nintendo issued a single DMCA notice that led GitHub to remove 8,535 repositories containing versions of Yuzu. GameSpot puts the company’s GitHub removal total at almost 9,000 when combining that larger 2024 wave with this new 401-repository sweep.
VGC also reports a February 2026 Nintendo DMCA notice that asked GitHub to remove repositories still containing Yuzu as well as repositories containing at least 12 other Switch emulators. The new seven-notice wave therefore looks less like a new front and more like another pass through a battlefield Nintendo has already mapped: Yuzu-derived forks, successor projects, Android-focused emulation, and smaller archived or experimental emulators that remain available through GitHub’s public code networks.
The Tears of the Kingdom claim explains Nintendo’s aggressive posture
Nintendo’s public anti-piracy posture around Switch emulation is tied to a specific commercial fear: pre-release and launch-window piracy of first-party games. VGC reports that Nintendo previously claimed The Legend of Zelda: Tears of the Kingdom was pirated over one million times in the 10 days before its May 2023 release. GameSpot also references the Tears of the Kingdom piracy claim in its coverage of Nintendo’s emulator campaign.
That claim does not prove that every repository in this 401-repository sweep was used for piracy, and the source material does not provide repository-by-repository evidence of illegal game distribution. What it does show is Nintendo’s strategic argument. The company is treating Switch emulators as part of the infrastructure that enables unauthorized game access, especially when emulators depend on keys that Nintendo says are unauthorized.
From a strategy angle, this is consistent with protecting both software sales and platform control. The Switch is still a live commercial ecosystem, and the required media for this article reflects a broader market context: the Switch has become Nintendo’s best-selling console ever. A platform that large creates a larger incentive for preservation work, tinkering, modding, and emulation, but it also creates a larger target for piracy enforcement. Nintendo’s approach is to reduce public availability of emulator code before it can become another successor chain.
GitHub removals slow distribution, but they do not erase the code economy
TorrentFreak notes that most affected repositories now point to takedown notices informing visitors that the repositories were removed. In some cases, visitors see a 404 error, which TorrentFreak says may suggest a developer voluntarily removed a repository after being notified. GameSpot similarly reports that users attempting to visit removed pages may receive a 404 error or a takedown notification.
The same TorrentFreak homepage summary for the report adds a key limitation: the takedown effort was successful in taking most repositories offline, but it also shows how quickly the code can resurface. That is the strategic loop Nintendo is trying to break. GitHub’s fork model is useful for open-source collaboration, but it also means a project can splinter into dozens or hundreds of visible copies after the parent is gone.
A public GitHub topic page for “switch-emulator” still listed 16 public repositories matching that topic in the provided source material. That listing should not be read as proof those repositories are functional Switch emulators, lawful, unlawful, or connected to Nintendo’s notices. It does show that public labels and repository discovery remain fluid after a takedown wave. For developers, the practical message is that naming, tags, forks, and archived copies can remain visible signals even after a major project has collapsed.
The signal for emulator projects is legal risk concentration
For emulator projects, the clearest signal is that Switch emulation has become a concentrated enforcement category for Nintendo. The company is no longer only aiming at prominent original teams. In this round, Nintendo targeted a successor to Yuzu, an independent Android emulator, Android ports, Early Access-derived Yuzu code, MonoNX forks, and smaller Yuzu forks. That breadth makes the risk profile difficult for new projects to manage if they inherit code, architecture, or distribution patterns from already-targeted repositories.
For players, the practical takeaway is simpler. If a Switch emulator repository you bookmarked is now unavailable, the source material points to Nintendo’s DMCA notices as the reason for many of those removals. The reports do not announce a new Nintendo policy for legitimate Switch ownership, do not change the availability of games on Nintendo hardware, and do not provide any safe path for downloading ROMs, keys, or emulator builds. Nintendo’s position, as quoted in the notices, is that these repositories circumvent technological protection measures tied to encrypted Switch games.
The unanswered question is whether any future Switch emulator project can operate in public at meaningful scale without becoming part of Nintendo’s takedown cadence. Based on this latest wave, the pressure is not limited to the biggest name in the scene. The meta has shifted toward network enforcement: if a project grows through forks, ports, and successor branding, that same growth can make it easier for Nintendo to target the whole cluster in one coordinated GitHub action.