Nintendo Wiped 400+ Switch Emulator Repos in One Day

One Busy Sunday for Nintendo’s Legal Team

On August 17, 2026, Nintendo filed seven DMCA anti-circumvention notices in a single day, and by the time GitHub processed them, more than 400 Switch emulator repositories had been wiped from the platform. It was a sweeping move, the kind that makes headlines. Whether it accomplishes much in the long run is a different question.

According to TorrentFreak, as reported by Dexerto, 401 repositories were removed in total. The biggest casualty by volume was Suyu, an emulator that had filled the vacuum left by Yuzu’s 2024 collapse. Of the 401 removed repos, 311 belonged to Suyu’s fork network alone. The timing adds a layer of irony: Suyu’s own maintainer had already announced in April that they were walking away from the project entirely, so Nintendo essentially swept up a ship that had already been abandoned at sea.

Also caught in the net was Skyline, an Android-focused Switch emulator whose development team voluntarily stopped work back in 2023. Its 29 repositories had sat dormant and untouched for years before they were pulled. MonoNX and several Yuzu forks rounded out the remaining notices.

The Legal Argument Nintendo Is Making

Every notice rests on the same foundation. Nintendo argues that these emulators make use of unauthorized copies of its cryptographic keys, commonly known as prod.keys, to decrypt Switch game files without authorization, which it says constitutes a violation of the DMCA’s anti-circumvention provisions.

To support those claims, Nintendo pointed to two prior legal outcomes. The first is the $2.4 million settlement reached in 2024 with Tropic Haze, the company behind Yuzu. The second is a default judgment issued last October against streamer Jesse Keighin, who was ordered to pay $17,500. Both are real, and both are genuinely useful precedents for Nintendo’s argument on paper.

But there’s a catch. Neither case actually went to trial. Neither resulted in a court weighing the emulator argument on its merits and ruling one way or the other. A settlement and a default judgment, while legally meaningful, are not the same as a judge saying “yes, this technology is inherently illegal.” That distinction matters, and it’s one critics of the notices have been quick to flag.

Pushback Is Already Coming

GitHub has said publicly that it reviews circumvention claims carefully and will, as Dexerto reported the platform’s stated policy, “err on the side of the developer” when the validity of a claim is unclear. That’s relevant context for what happens next.

At least one developer is already pushing back directly. A user on X identified as Alula argued publicly that one of the targeted projects was a non-functional, barebones emulator that lacked any prod.keys loading or decryption functionality whatsoever. The argument is straightforward: if a piece of software doesn’t actually perform the act Nintendo is accusing it of, the circumvention claim may be invalid, and a counternotice could be appropriate.

That kind of challenge is exactly why mass DMCA sweeps of this scale often generate as many legal headaches as they resolve. Nintendo’s notices are broad, they’re numerous, and they hit projects across very different stages of development and activity. Lumping a dormant three-year-old Android project alongside active forks of Yuzu is the kind of approach that invites scrutiny.

The Broader Pattern

None of this is happening in a vacuum. Nintendo has been consistently and aggressively pursuing emulation-related targets since its Yuzu settlement, and the Switch 2 is now out in the world with its own ecosystem to protect. The company has genuine legal tools at its disposal and has shown real willingness to use them.

But the emulation community has also gotten very good at forking, mirroring, and relocating code faster than takedown notices can land. The 401 repositories removed on August 17 almost certainly exist somewhere else by now. Whether any developer actually chooses to fight Nintendo in court over a counternotice is the more interesting question, and the answer to that one will matter a lot more than the raw removal count.