SoVis Games
EN /

Nintendo Switch Emulator Ecosystem After the August 17, 2026 DMCA Sweep: 401 Repositories Removed, What Still Works

Nintendo filed seven DMCA anti-circumvention notices with GitHub on 2026-08-17, removing 401 Nintendo Switch emulator repositories including Suyu (311), Skyline (29), MonoNX (17), and multiple Yuzu forks. This guide explains what is still legal, what is still available (Ryujinx, Eden, Sudachi, Citron, Kenji-NX, MeloNX), the legal landscape under DMCA Section 1201, and what to expect next.

Freshness Verified 2026-08-27 against GitHub's official DMCA repository (filings 2026-08-17-nintendo.md through 2026-08-17-nintendo-7.md), VGC reporting on the sweep, and Nintendo of America v. Tropic Haze (2024 settlement) + Keighin default judgment (October 2025). Ryujinx status confirmed against the project's own release channels.

On 2026-08-17, Nintendo filed seven DMCA anti-circumvention notices with GitHub in a single day, removing 401 repositories. This guide explains what was removed, what survived, what the law actually says, and what is still legal to use.

TL;DR — what you need to know

If you are wondering…The answer
Is the Switch emulator ecosystem dead?No. Ryujinx is still operational. Eden, Sudachi, Citron, Kenji-NX, MeloNX were not in the August 17 sweep and remain available off-GitHub.
Are emulators illegal?The software is legal (Sony v. Connectix, 1998). Distributing emulators that decrypt Switch games using unauthorized prod.keys is what Nintendo targets under DMCA Section 1201.
Will Nintendo sue me for personal use?There is no public case of Nintendo suing an end user. Enforcement focuses on developers and distributors (Tropic Haze $2.4M, Keighin $17,500).
Can I still play my Switch library on PC?Yes — if you own the games, dump your own keys, and live in a jurisdiction with a Section 1201 exemption. The US has one through 2028.
What about Switch 2 emulation?No consumer-grade Switch 2 emulator exists as of August 2026. The Switch 2’s stricter encryption (per-game keys, secure boot, LPDDR5X) makes it harder to emulate than Switch 1.

1. What happened on 2026-08-17

The seven DMCA notices

Nintendo filed seven DMCA anti-circumvention notices with GitHub on a single day — 2026-08-17. GitHub processed them within hours. The notices are publicly archived in GitHub’s DMCA repository under the filenames 2026-08-17-nintendo.md through 2026-08-17-nintendo-7.md. By the end of the day, 401 repositories had been disabled.

The breakdown by target repository:

Repository (parent)ProjectRepos removedNotes
vstyler96/suyuSuyu (Yuzu successor)311Largest single fork-network. The Yuzu maintainers shut down in March 2024; Suyu was the most prominent C++ rewrite that continued Yuzu’s work.
skyline-emu/skylineSkyline (Android)29Android-targeted Switch emulator; original Skyline developers voluntarily stopped active work in 2023, but forks continued for 3 years.
exverge-0/yuzu-EA4176Yuzu Early Access 417621A specific Early Access build variant of Yuzu.
irlbunny-archive/MonoNXMonoNX (C#-based)17C# emulator for Switch.
NicolasArvani/yuzuYuzu fork14Independent fork of Yuzu main branch.
liushuyu/yuzu-androidYuzu Android port8Android-targeted Yuzu build.
IpwnedU/yuzu-masterYuzu master (parent)1The parent repository itself.
Total401

The 401 figure is not 401 different emulators. It is 401 repositories including forks, mirrors, archives, and dormant branches under the affected parent repositories. GitHub processed the Suyu notice against the entire fork network (more than 100 forks → entire tree disabled in one action under GitHub’s fork-network rule). For smaller projects, GitHub disabled the specific forks listed in the notice.

The fork-network rule (GitHub DMCA policy)

GitHub’s DMCA policy has a specific clause that caused the cascading removal: when a parent repository has more than 100 forks and the rightsholder alleges that the forks contain substantially the same infringing content, GitHub disables the entire tree in one action instead of processing each fork individually.

This is the policy that turned Nintendo’s Suyu notice (which would otherwise have hit the parent repo and maybe 5-10 close forks) into a 311-repo wipe. Other rightsholders have used the same clause: Tencent had a 4,195-repo takedown earlier; Nintendo itself used the same clause in February 2026 to remove 218 repos.

What the notices say

Nintendo’s filings repeat the same legal argument across all seven notices. The text (verbatim from GitHub’s public archive):

“The reported repositories offer, link to, or otherwise provide access to Nintendo Switch emulators. Nintendo Switch emulators are primarily designed to play Nintendo Switch games. Specifically, these Nintendo Switch emulators illegally circumvent Nintendo’s TPMs [Technological Protection Measures] in order to run illegal copies of Nintendo Switch games.”

The argument targets the anti-circumvention provisions of DMCA Section 1201, not copyright infringement directly. That distinction matters: a standard copyright dispute can focus on a specific work (one game file). An anti-circumvention claim gives Nintendo a route to challenge the tooling and the fork ecosystem surrounding it — which is why one filing can take down 311 Suyu forks at once.

Why Suyu was the biggest target

Suyu was the most prominent Yuzu successor. After Yuzu shut down in March 2024 (settled out of court for $2.4M), Suyu emerged as a community-driven C++ rewrite that continued Yuzu’s development. By 2026-08, Suyu had 311 forks on GitHub — the largest fork network of any emulator project. Nintendo filed its August 17 notice against the parent repository; GitHub applied the fork-network rule; the entire Suyu ecosystem disappeared from GitHub in one action.

Notably, Suyu’s maintainer had already abandoned the project in April 2026 — the August notice cleaned up an ecosystem that was already in wind-down. But the forks, mirrors, and archives continued to live on, which is why the 311 figure exists.


2. What was not in the sweep

The August 17 notices were narrowly targeted. The following projects were not removed:

ProjectStatus (Aug 27, 2026)Why
Ryujinx✅ OperationalIndependent of Yuzu codebase since 2017. Was not in the August 17 notice list. Has its own legal history (October 2024 temporarily disabled downloads, resumed after risk assessment) but remains available.
Eden✅ Operational (off-GitHub)Named in Nintendo’s February 2026 sweep but not August 17. Has been distributing via project infrastructure since early 2026 after the February sweep.
Sudachi✅ Operational (off-GitHub)Named in February 2026; not in August 17. Source moved to project infrastructure.
Citron✅ Operational (off-GitHub)Same pattern as Eden and Sudachi.
Kenji-NX✅ Operational (off-GitHub)Same pattern.
MeloNX✅ Operational (off-GitHub)Same pattern.
Cemu (Wii U)✅ OperationalWii U emulator; not Switch, not in Nintendo’s recent enforcement focus.
PCSX2 / AetherSX2 (PS2/PSP)✅ OperationalSony’s enforcement has been quieter than Nintendo’s; PCSX2 still active.

The pattern:”: the projects that survived are either (a) independent of Yuzu’s codebase and not named in the notices (Ryujinx), or (b) were named in February 2026 and have moved source-hosting off GitHub (Eden, Sudachi, Citron, Kenji-NX, MeloNX).

If you want one of the off-GitHub emulators, do not look on GitHub for download links. Follow the project’s own site or community channels. Distributing the binaries on GitHub is itself a DMCA target.


In the foundational US case, Sony sued Connectix over the Virtual Game Station (a PlayStation emulator). The Ninth Circuit Court of Appeals ruled that emulator software is legal under US copyright law because intermediate copying of the console’s BIOS for interoperability purposes constitutes fair use. Connectix’s product was a transformative work that competed in a different market.

This precedent still stands in 2026. The act of writing or distributing emulator software is not, by itself, a copyright violation in the US. The DMCA Section 1201 analysis is separate.

DMCA Section 1201 — anti-circumvention

DMCA Section 1201 prohibits trafficking in technology that is primarily designed to circumvent a technological measure that effectively controls access to a copyrighted work. Nintendo’s argument in the August 17 notices rests on Section 1201, not copyright infringement.

The argument: Switch games are encrypted with proprietary keys (commonly called prod.keys). Emulators that decrypt Switch games at runtime using unauthorized copies of prod.keys are trafficking in circumvention technology under Section 1201. The fact that the emulator itself is legal (Sony v. Connectix) does not protect it from a Section 1201 claim when its primary use is to bypass TPMs.

Important nuance: Section 1201 has an exemption process. The US Copyright Office has renewed an exemption for personal use emulation of video game consoles multiple times, most recently in 2024 (effective through 2028). The exemption covers lawful acquisition of games and self-dumping of keys. Outside the US, check your local laws — the EU has similar provisions, but the specifics vary by member state.

The two precedents Nintendo cites

Nintendo’s August 17 notices cite the same two prior cases as the legal basis:

  1. Nintendo of America v. Tropic Haze LLC (settled March 2024) — Tropic Haze developed Yuzu. Nintendo sued in February 2024; the parties settled within weeks. Tropic Haze agreed to pay $2.4 million and shut down Yuzu. The settlement was a consent judgment, not a contested ruling — the broader question of whether emulation is illegal was never adjudicated.

  2. Keighin default judgment (October 2025) — Jesse Keighin, a streamer, broadcasted pre-release Switch games using an emulator. He stopped responding to Nintendo’s lawsuit. The court entered a default judgment ordering him to pay $17,500. This is a default judgment, meaning the court ruled without a contested hearing because the defendant did not appear.

Neither precedent actually ruled on whether emulator distribution is legal. Both are settlements or default judgments. Nintendo’s notices rely on them as evidence of legal exposure, not as binding precedent.

The MonoNX counter-notice

At least one developer pushed back against the August 17 takedown. A user on X identified as Alula argued that one of the targeted MonoNX repositories was a non-functional, barebones emulator that lacked any prod.keys loading or decryption functionality whatsoever:

“this claim is invalid and likely eligible for a counternotice … because the build in question had no key-loading or decryption code at all”

This is the kind of challenge mass DMCA sweeps often generate. Counter-notices are a formal process under DMCA Section 512(g); GitHub forwards them to the rightsholder, who then has 10-14 business days to file a lawsuit to keep the content down. If no lawsuit is filed, the content is restored. The Alula case is ongoing as of this writing.


4. Timeline: Nintendo’s enforcement against emulators (2023 → 2026)

The August 17 sweep is the third major GitHub action in three years. The pattern has been consistent:

DateActionScopeNotes
2023Skyline developers shut down voluntarilyAndroid Switch emulatorPressure from Nintendo, not legal action
March 2024Tropic Haze / Yuzu lawsuit settledYuzu + Citra shut down$2.4M consent judgment
May 20248,535 Yuzu-related repositories removedGitHub fork-network takedownSingle largest emulator enforcement action before August 2026
February 202613 emulator projects namedEden, Citron, Kenji-NX, MeloNX, Sudachi, and others218 repositories affected; many projects moved off GitHub in response
October 2025Keighin default judgmentIndividual streamer$17,500
August 17, 2026401 repositories removedSuyu, Skyline, MonoNX, Yuzu forks7 notices, single day, fork-network rule
August 18-27, 2026Counter-notices and forks respawningOngoingAlula (MonoNX), Yuzu forks respawning on alternative hosts

The pattern: Nintendo runs a coordinated GitHub sweep roughly every 12-18 months. Each sweep hits a different set of projects. Developers respond by forking, mirroring, or moving to self-hosting. The cycle repeats.

Cumulative: Nintendo’s GitHub actions have now removed over 9,000 repositories related to Switch emulation since 2024. The current state is fragmented — projects alive but distributed across many hosts.


5. What you can legally do today

This section covers personal use in the US, where DMCA Section 1201 has an active exemption. Other jurisdictions vary; check your local laws.

Personal use emulation checklist

  • You own a Nintendo Switch console (legally purchased).
  • You own the games you want to emulate (legally purchased, physical or digital).
  • You dump your own prod.keys from your own Switch using homebrew (e.g., Lockpick_RCM).
  • You dump your own game files (XCI for cartridges, NSP for digital).
  • You are running the emulator on hardware you own.

If all five are yes, personal use emulation of games you own is covered by the Section 1201 exemption through 2028. The exemption is renewed periodically; the next review is in 2027 for the 2029-2032 cycle.

What is NOT covered

  • Downloading pre-decrypted ROMs from ROM sites — illegal, regardless of whether you own the game.
  • Downloading prod.keys from someone else’s dump — circumvents the personal-use exemption.
  • Distributing your own dump, emulator build, or prod.keys to others — the exemption covers personal use only.
  • Switch 2 emulation — no consumer-grade emulator exists, and the legal analysis differs because Switch 2 uses per-game keys and secure boot.

Recommendations for US personal users

If you want to emulate Switch 1 games on PC in 2026:

  1. Pick Ryujinx as the default emulator. It has the longest track record, the largest community, and is not currently in Nintendo’s enforcement crosshairs.
  2. Use a real Switch console for the key dump. You need a vulnerable Switch (early firmware) to run Lockpick_RCM. Newer Switch models patched the exploit.
  3. Keep your dumps local. Do not share prod.keys or game files with anyone.
  4. Update your emulator regularly. Ryujinx releases improvements monthly.
  5. Understand the legal gray area. The Section 1201 exemption covers personal use, but Nintendo could still send a takedown notice or test the exemption’s limits.

For developers and distributors

This is a different risk profile. Tropic Haze settled for $2.4M; the Keighin default judgment was $17,500. If you distribute emulator builds or prod.keys publicly, you are a target. The legal precedent for emulator distribution is unfavorable (the Tropic Haze settlement, while not a contested ruling, made Nintendo’s case stronger).


6. Switch 2 emulation: why there is nothing to talk about

You may have noticed there is no “Switch 2 emulator” section. That is intentional — there is no consumer-grade Switch 2 emulator as of August 2026. Reasons:

  1. Per-game encryption keys: Switch 1 uses a single console-wide key (prod.keys) for decryption. Switch 2 uses per-game encryption that requires a unique key per title. This makes the dump workflow more complex and harder to automate.
  2. Secure boot chain: Switch 2’s boot chain is locked down end-to-end. Early Switch (2017-2018) had exploitable bootROM bugs that enabled custom firmware; Switch 2 has not had a public bootROM exploit as of August 2026.
  3. LPDDR5X memory encryption: Switch 2 uses encrypted LPDDR5X, making memory dumps more difficult than the original Switch.
  4. Active anti-piracy: Nintendo has implemented stronger telemetry and anti-cheat systems that detect modified Switch 2 hardware.

Realistic timeline for Switch 2 emulation: no one outside the emulation research community knows. The original Yuzu project took ~2 years from the Switch launch (March 2017) to its first public playable release (2019). Yuzu itself was preceded by 2+ years of research and reverse-engineering. If a Switch 2 emulator emerges publicly, expect 2027-2029 at the earliest. Nintendo has bought itself time by making Switch 2 harder to emulate than Switch 1.


7. FAQ

Q: Will Nintendo go after me for running Ryujinx on my Steam Deck? A: There is no public case of Nintendo suing an individual end user for personal emulation. Nintendo’s enforcement has targeted developers (Tropic Haze), distributors (the August 17 sweep), and commercial streamers (Keighin). Personal use, with games you own and keys you dumped yourself, is the lowest-risk profile.

Q: Is the August 17 sweep the end of Switch emulation? A: No. The sweep removed 401 repositories from GitHub. Ryujinx is not affected. Eden, Sudachi, Citron, Kenji-NX, MeloNX are not affected (they already moved off GitHub after the February 2026 sweep). The ecosystem has been moving toward self-hosting for over a year; the August sweep accelerates that trend rather than ending it.

Q: What should I do if my favorite emulator fork disappeared? A: Check the project’s own site or community channels (Discord, Reddit, etc.) for the new download location. Many projects have moved to self-hosted infrastructure or alternative platforms. Avoid random “alternative download” sites — they often bundle malware.

Q: Can I still buy a Switch and play Switch games legally? A: Yes. This guide is about emulation. Buying a Switch console and games from Nintendo is legal in all jurisdictions. The August 17 sweep affects the emulator ecosystem, not Nintendo’s commercial business.

Q: What about the legal precedent of the Tropic Haze settlement? A: Tropic Haze settled for $2.4M without a contested ruling. The case established that Nintendo can extract significant damages from emulator developers, but did not establish that all emulation is illegal. The settlement’s value as legal precedent is limited — it tells emulator developers that fighting Nintendo in court is expensive, not that they would lose.

Q: Does the Section 1201 exemption cover Switch 2 emulation? A: The current exemption (effective through 2028) covers “video games consoles” generically. Whether Switch 2 falls under the exemption depends on how the Copyright Office interprets it. Given Switch 2’s stronger encryption, even if the exemption covers it technically, dumping keys from a Switch 2 is currently not possible without exploits that have not been published.

Q: Are ROM sites still operating? A: Yes. ROM sites that distribute pirated Switch game files operate outside the law. Do not download from them. If you want to emulate a Switch game, dump your own copy from your own console and your own cartridge.


8. Final takeaway

The August 17 sweep is a coordinated takedown of GitHub-hosted emulator repositories, not the end of Switch emulation. Ryujinx remains operational. Eden, Sudachi, Citron, Kenji-NX, MeloNX remain available via project infrastructure. The legal landscape has not changed — emulators are legal, but distribution of emulators that bypass Switch’s TPMs is targeted under DMCA Section 1201.

For personal users in the US: the path is clear — own a Switch, own the games, dump your own keys, run Ryujinx on hardware you own. The Section 1201 exemption covers this through 2028.

For developers and distributors: the risk is increasing. Nintendo has demonstrated a willingness to extract millions in settlements and pursue legal action against commercial entities. Distributing emulator builds or prod.keys publicly puts you in the same risk category as Tropic Haze.

For Switch 2 emulation: nothing yet. Expect 2027-2029 at the earliest for any consumer-grade option.

The cycle continues — Nintendo enforces, developers fork, projects move to self-hosting, and personal users keep playing their own games on hardware they own. The August 17 sweep is one round in a multi-year enforcement pattern.


What’s next


Last verified: 2026-08-27 against GitHub’s official DMCA repository (filings 2026-08-17-nintendo.md through 2026-08-17-nintendo-7.md), VGC and Kagi News reporting on the August 17 sweep, Nintendo of America v. Tropic Haze LLC settlement (March 2024, $2.4M), Keighin default judgment (October 2025, $17,500), and Ryujinx’s own release channels (still operational). Section 1201 exemption status confirmed against the US Copyright Office 2024 ruling (effective through 2028).