Suyu, one of the three emulators that inherited the Nintendo Switch emulation crown after Yuzu’s court-ordered shutdown, went dark on September 13, 2026. Its GitHub organization now carries a single administrative note: archived, no longer maintained. That leaves two names carrying the bulk of Switch emulation traffic this week, Ryujinx (through its active fork, Ryubing) and Citron, and a lot of displaced users typing “suyu alternative” into search bars. This comparison breaks down what each project actually offers right now, what changed in the last month, and which one makes sense depending on your hardware and your risk tolerance.
None of this is speculative catalog-shopping. Ryujinx alone pulls over 40,000 monthly searches in the US, Citron trails at roughly 9,900, and Suyu still draws close to 1,900 searches a month even after its archive notice went up, according to keyword tracking pulled this week. People are actively deciding what to install today, not next year, so this piece sticks to verified facts, dated events, and specs pulled from official project pages rather than vague “best of” filler.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Suyu Just Went Dark: What Changed on September 13, 2026
The suyu-emu organization on GitHub was marked “archived by an administrator” on September 13, 2026, with a plain notice that the project is no longer maintained. That timing is not a coincidence. Nintendo’s legal team sent seven fresh copyright infringement notices to GitHub in late August 2026, and the resulting sweep removed 401 Switch-emulator repositories in a single wave. Of those 401 repos, 311 contained Suyu code in some form, making it by far the most heavily targeted codebase in that particular purge.
What makes the shutdown sting more is the timing of Suyu’s last technical milestone. Just one day before the archive notice, coverage on September 14, 2026 detailed Suyu v0.04, a build that added a static AArch64-to-x86-64 recompilation system, effectively repositioning Suyu as both an emulator and a native code recompiler for supported 64-bit ARM titles. That approach, which converts Switch game code to run more directly on PC hardware rather than translating instructions on the fly, is a meaningfully different technical bet than the dynamic recompilation used by Ryujinx and Citron. It also means Suyu’s most interesting work landed the same week the project got wiped from its primary distribution channel.
For anyone who had Suyu installed before September 13, the existing build still runs. Nothing about an archived GitHub organization reaches into your PC and disables software already on disk. What changes is future support: no more commits, no more compatibility patches for new game updates, and no official channel to grab v0.04 or later builds unless you already have a copy or find it through a third-party mirror, which carries its own trust and malware risk.
The Post-Yuzu Emulation War, Explained
To understand why three separate projects are now fighting over the same user base, you have to go back to February 2024, when Nintendo filed a US federal lawsuit against the developers behind Yuzu, alleging DMCA violations and arguing that Yuzu’s core function was bypassing Switch encryption to enable piracy. The suit ended in a settlement and Yuzu’s shutdown the following month. That single legal action didn’t just kill one emulator, it created a vacuum that half a dozen forks and rewrites rushed to fill, each one trying to distance its branding and codebase from Yuzu closely enough to avoid the same fate.
Suyu was one of the direct successors, built from Yuzu-derived code and marketed early on as one of the most prominent projects to emerge after Yuzu’s development ceased. Its collapse this month, less than 18 months after Yuzu’s own end, tells you that rebranding a codebase is not the same as escaping the legal exposure baked into it. Eden, another Yuzu-descended fork, had its own GitHub repository pulled in March 2026 and now distributes through its own project site, Git backups, and itch.io bundles instead, a shift we covered in our Eden 4.2 vs Ryubing 4.0 comparison. Citron, by contrast, has positioned itself around original engineering work and Android-first performance, which appears to have bought it more room to operate, though “more room” in emulator law is a relative and untested phrase, not a legal guarantee.
Ryujinx sits apart from this entire chain. It predates Yuzu’s shutdown, was never named in Nintendo’s 2024 litigation, and has an independent development history stretching back to 2017, as detailed on its Wikipedia entry. That distinction matters for anyone trying to gauge risk, and it is a big part of why Ryujinx-derived builds still dominate search volume even though the core team’s release cadence slowed dramatically after October 2024, with builds distributed through Ryujinx.io and Ryujinx.dev now listing v1.3.3, released in May 2026, as the latest stable version for Windows, macOS, and Linux, alongside a separate Canary 1.3.295 branch also listed in May 2026 and an even higher-numbered 1.4.1 build that Release Monitoring had already recorded on December 19, 2025, a confusing version trail that reflects just how many independent hands are now patching the same frozen codebase.
This Isn’t the First Time: The 3DS Precedent
If the Yuzu-to-Suyu-to-archive pipeline feels familiar, that’s because Nintendo ran a nearly identical playbook against 3DS emulation a year earlier. Citra, the dominant 3DS emulator for close to a decade, shut down in March 2024 after Nintendo pursued its lead developer directly and reached a $2.4 million settlement. What followed was the same fork-and-scatter pattern now playing out on Switch: successor projects like Azahar and Lime3DS picked up Citra’s codebase and kept 3DS emulation alive, a transition we covered in detail in our Azahar vs Citra vs Lime3DS comparison.
The parallel matters because it tells you this isn’t a one-off legal aggressiveness spike aimed specifically at Switch software. It’s a repeatable enforcement strategy: target the highest-profile project with direct litigation or a coordinated takedown campaign, let the resulting settlement or shutdown create a chilling effect, then use routine DMCA notices to keep pressure on whatever forks emerge afterward. Suyu’s archive notice this month is simply the Switch-emulation version of what already happened to Citra’s ecosystem in 2024. If that pattern holds, expect continued, periodic takedown waves against Eden, Citron, and Ryubing rather than a single decisive legal action against any one of them.
Ryujinx and Ryubing: The Legacy Standard That Refuses to Die
Ryujinx’s core development slowed sharply after October 2024, but it never fully went dark: incremental point releases have kept trickling out through mirrors like Uptodown, with v1.3.259 logging 567,610 downloads by March 6, 2026, followed by v1.3.340 on July 31, 2026, and v1.3.351 in August 2026. Anyone installing “Ryujinx” today is really installing one of those patched builds or a fork of that codebase, and the most actively maintained of those forks is Ryubing, which markets itself directly as the Ryujinx successor. Ryubing ships from a self-hosted domain plus mirrors rather than a single GitHub repo, a distribution choice that looks deliberately designed to reduce single-point takedown risk after watching what happened to Suyu and Eden.
Community sentiment through 2026 still leans heavily toward Ryujinx-based builds for stability, and the numbers back it up: Ryujinx’s own compatibility tracker listed more than 4,050 tested titles as of May 2026, with roughly 3,400 of them rated playable. A January 2026 Reddit discussion asking which Switch emulator to use in 2026 saw the top response describe Ryujinx as the most consistent performer among everything tried, and multiple 2026 emulator roundups continue to call Ryujinx the most stable and widely recommended option, largely riding on a compatibility record built up over years of pre-lawsuit development. That reputation is a real asset: Ryujinx has had more time to iron out edge cases in games released between 2017 and 2024 than any of the newer forks.
The tradeoff is that Ryujinx’s underlying architecture wasn’t built with 2026-era CPUs in mind, and forks patching an already-frozen codebase have less room to introduce structural performance changes than a project like Citron that keeps iterating on core emulation logic. If you already run a Ryujinx or Ryubing setup for a title library assembled over the past few years, including save states, custom mods, and controller profiles, there’s little reason to rebuild that from scratch just because Suyu made headlines this month. If you’re starting fresh in late 2026, it’s worth weighing that legacy-strength-versus-modern-performance tradeoff before committing.
Citron: The Performance-First Emulator Built for Handhelds and Phones
Citron has built its identity around raw frame-rate performance rather than exhaustive accuracy, and that focus shows up clearly in where it gets used. An Android-focused review from February 2025 called Citron the last actively developed Switch emulator on Android at the time, highlighting the Citron v0.5 build as a major stability and compatibility jump for phone-based play. Development kept pace from there, with Citron’s release repository listing a v0.11.0 pre-release on November 11, 2025, ahead of the desktop stable build that followed weeks later. That Android-first lean has stuck through 2026: Uptodown was still listing Citron’s Android build at version 0.4.5 as of September 29, 2026, and Citron remains one of the more practical options for running Switch titles on a mid-range phone rather than a full desktop rig.
On desktop, Citron’s release cadence moved quickly past the 0.12.25 Stable build tagged December 26, 2025: by February 1, 2026, the project had already shipped v2026.02.1, a lightweight 21.6 MB update that marked a shift toward date-stamped versioning, with Citron’s CI continuing to index fresh nightly builds off upstream commit 05e7127 as of May 20, 2026, a pace that indicates the project kept shipping through the same months that claimed Suyu and forced Eden off GitHub. Citron also had its own scare: coverage from August 2026 notes that Citron’s Git services were temporarily disrupted before being restored by mid-2026, a smaller-scale version of the infrastructure instability now common across this entire category of software.
If you’ve tried Citron Neo specifically for a title like Pokémon Legends Z-A, you already know the setup differs slightly from a standard desktop Citron build. Citron Neo shipped its first stable build on April 27, 2026, and development hasn’t slowed since: its GitHub repository logged commit 3527589 on October 10, 2026, the same day a fresh Windows nightly build went live, and we’ve covered that Citron Neo installation process step by step if you need the walkthrough. The short version for this comparison: Citron trades some of Ryujinx’s long-tail accuracy for consistently higher frame rates on lower-power hardware, which is the exact opposite priority from what Ryujinx’s legacy user base tends to value.
Suyu: From DMCA Target to Static Recompiler Experiment
Suyu’s final act is arguably its most technically interesting one. The v0.04 build, detailed just before the archive notice, introduced static AArch64-to-x86-64 recompilation, converting supported 64-bit ARM game code directly into x86-64 instructions rather than interpreting or dynamically recompiling it during runtime. In theory, that approach can get closer to native performance for the specific titles it supports, at the cost of needing per-game compatibility work that dynamic recompilation avoids. Reporting on the build explicitly noted it was based on Eden’s codebase, which itself derives from Yuzu, underlining how tangled the lineage between these projects has become, a lineage we also traced in our Eden vs Citron vs Sudachi Reborn comparison.
Whether that recompiler idea goes anywhere now is an open question. An archived GitHub organization doesn’t erase the code, and static recompilation techniques tend to attract engineers regardless of what happens to the original project’s branding, so don’t be surprised if the underlying concept resurfaces under a different name within another fork. For now, treat Suyu as a project you can still run if you already have it installed, but not one to start fresh with, since there’s no active channel shipping compatibility fixes for newly released or patched games.
Dynamic vs Static Recompilation: The Technical Difference That Actually Matters
Most of the jargon separating these three projects boils down to one core engineering decision: how does the emulator convert Switch game code, written for an ARM-based processor, into instructions an x86-64 PC or Android chip can actually execute? Ryujinx and Citron both rely on dynamic recompilation, sometimes called just-in-time or JIT compilation, which translates chunks of ARM code into x86-64 instructions on the fly, as the game runs. It’s flexible and handles unpredictable code paths well, but it carries a constant translation overhead that eats into the CPU budget available for the game itself.
Static recompilation, the approach Suyu introduced in v0.04, works differently. Instead of translating instructions during gameplay, it analyzes and converts an entire game’s ARM64 code to x86-64 ahead of time, before you ever hit launch. Done well, that can shrink or eliminate the runtime translation tax that JIT-based emulators pay continuously, which is why the technique gets described as a path toward closer-to-native performance. The catch is that static recompilation needs to correctly map every code path in advance, including ones a game might only trigger in rare edge cases, which makes it far more labor-intensive to implement correctly per title than a general-purpose JIT engine. That’s also why Suyu’s implementation only covered “supported” 64-bit ARM titles rather than working universally across its full compatibility list.
For everyday users, the practical takeaway is simple: Ryujinx and Citron’s JIT approach means broader out-of-the-box compatibility across a large game library, while Suyu’s static recompilation experiment traded that breadth for a shot at higher performance on a narrower set of supported titles. Neither approach is strictly superior, they’re optimized for different goals, and it’s worth remembering that Suyu’s recompiler never got the runway to prove itself at scale before the project was archived.
Ryujinx vs Citron vs Suyu: Full Specs Comparison Table
| Category | Ryujinx / Ryubing | Citron | Suyu |
|---|---|---|---|
| Status as of Sept 15, 2026 | Original project frozen (Oct 2024); Ryubing fork actively maintained | Active on desktop and Android | Archived Sept 13, 2026, no longer maintained |
| First released | 2017 (original Ryujinx) | 2024 (post-Yuzu fork era) | 2024 (post-Yuzu fork era) |
| Named in Nintendo’s 2024 lawsuit | No | No | No (targeted via later DMCA takedown wave instead) |
| Windows support | Yes | Yes | Yes (last stable builds only) |
| Linux support | Yes | Yes | Yes |
| Android support | Limited, community-patched builds | Yes, actively developed for Android | Limited, unofficial builds only |
| Emulation approach | Dynamic recompilation (JIT) | Dynamic recompilation (JIT) | Dynamic recompilation, plus static AArch64-to-x86-64 recompiler in v0.04 |
| Primary distribution | Self-hosted domain plus mirrors (Ryubing) | Official site, restored Git hosting | GitHub (now archived); third-party mirrors only |
| Latest confirmed build | Ryubing rolling releases through 2026 | 0.12.25 Stable (Dec 26, 2025), 76+ commits since | v0.04 (mid-September 2026) |
| Community compatibility reputation | Strongest for pre-2024 title library | Strong on Android, mid-range hardware | Untested long-term due to shutdown |
| Update cadence in 2026 | Moderate (fork-dependent) | Active, regular commits | Stopped after Sept 13, 2026 |
| Best suited for | Established libraries, LDN multiplayer, legacy accuracy | Phones, handhelds, frame-rate-sensitive play | Existing installs only; not for new setups |
Benchmark Data: Compatibility, Frame Rate, and Stability
Direct, apples-to-apples benchmark suites comparing Ryujinx, Citron, and Suyu on identical hardware are hard to find in public form right now, partly because Suyu’s shutdown happened days before this article, and partly because none of these projects publish standardized FPS charts the way GPU makers do. What exists instead is a mix of community testing, official release notes, and independent tech coverage, and treating all three the same way would overstate how directly comparable they are. Here’s what’s actually documented.
On the Reddit thread from January 2026 mentioned earlier, the most upvoted response specifically credited Ryujinx with the best overall performance among everything the poster had tried, framing it as both stable and fast rather than one or the other. That kind of anecdotal but widely-endorsed feedback lines up with multiple 2026 emulator guides that keep naming Ryujinx-derived builds as the most stable and widely recommended choice for desktop play, a reputation built on years of pre-lawsuit compatibility work rather than any single 2026 patch.
Citron’s performance story is documented differently, through its own release cadence rather than third-party benchmark charts. The jump from Citron v0.5 in February 2025, described at the time as delivering major stability and compatibility improvements for Android, through to the 0.12.25 Stable desktop release in December 2025 and the 76 additional commits logged since, shows a project iterating quickly on both platforms rather than converging on one. Independent coverage from August 2026 specifically frames Citron as prioritizing raw frame-rate over broader accuracy, which tracks with why it’s become the go-to choice for phone and lower-power handheld emulation rather than desktop purists chasing perfect audio sync or niche title support.
Suyu’s late push into static recompilation with v0.04 is the most performance-relevant technical claim of the three, since converting ARM instructions directly to x86-64 ahead of runtime can, for supported titles, reduce the overhead that dynamic JIT recompilation introduces. But that claim arrived the same week as the shutdown, meaning there’s no independent third-party benchmark yet confirming real-world frame-rate gains across a meaningful game list. Treat it as a promising but unverified technical direction rather than a proven performance win.
Cost to Run Each Emulator: Hardware and Software Pricing
All three projects are free, open-source software, so there’s no license fee comparison to make in the traditional sense. What actually drives cost differences is the hardware each one expects you to already own, and the historical monetization baggage that shaped Nintendo’s legal arguments against this entire category of software.
| Cost Factor | Ryujinx / Ryubing | Citron | Suyu |
|---|---|---|---|
| Software license cost | $0 (open source) | $0 (open source) | $0 (open source, archived) |
| Minimum practical desktop PC | Mid-range CPU, dedicated GPU recommended (roughly $700-900 build) | Similar mid-range desktop spec (roughly $700-900 build) | Similar spec, no longer receives new-title patches |
| Mobile hardware needed | Not the primary use case; limited unofficial ports | Mid-to-high-end Android phone with a modern Snapdragon or Dimensity chip | Not officially supported on mobile |
| Historical monetization model | None documented for Ryujinx itself | None documented | Inherited Yuzu-era codebase; Nintendo’s 2024 suit against Yuzu specifically cited paid early-access Patreon tiers as part of its argument |
| Ongoing cost after shutdown risk | Low, since Ryubing distributes independently of a single GitHub org | Low, active official hosting | None to pay, but zero future patch support |
That Patreon detail matters more than it might look. Nintendo’s original case against Yuzu leaned partly on the argument that the project profited directly from enabling piracy through paid early-access builds, which is a materially different legal posture than a purely volunteer-run, donation-optional project. None of Ryujinx, Citron, or the last iteration of Suyu operated a comparable paywalled early-access model, which is worth knowing if you’re trying to gauge how each project’s business model might factor into future legal exposure.
Real-World Use Cases: Who Is Actually Using Each Emulator
The abstract comparison only tells half the story. Here’s how these three tools actually get used in practice, based on documented community behavior through 2026.
- The archived-library holdout. Someone who built a Ryujinx setup years ago, with custom controller mappings, save states for a 40-plus game library, and LDN multiplayer configured for local co-op, has little incentive to migrate. Ryubing lets that setup keep receiving patches without starting over.
- The phone-first portable player. A commuter running Switch titles on a mid-range Android phone during a train ride is squarely Citron’s target user, given its Android-specific optimization work dating back to the v0.5 build in early 2025.
- The Steam Deck and handheld PC owner. Someone running a Linux-based handheld and comparing setups against a Steam Deck, ROG Ally, or Legion Go configuration is likely testing both Ryujinx-based forks and Citron side by side, since both run on Linux and neither locks a handheld owner into one ecosystem.
- The displaced Suyu user scouting alternatives. Anyone who had Suyu installed before September 13, 2026 and is now searching for where to go next fits directly into this article’s core audience, choosing between Ryubing’s stability and Citron’s frame-rate focus.
- The engineer curious about static recompilation. Developers and technically-minded users interested in Suyu’s AArch64-to-x86-64 recompiler concept represent a smaller but real group studying the last builds before the archive, independent of whether they plan to use Suyu day to day.
- The Pokémon-specific emulation user. Players focused narrowly on specific titles often end up testing multiple emulators back to back until one runs their specific game cleanly, since compatibility varies title by title rather than emulator by emulator uniformly.
Where Each Project’s Community Actually Lives Now
Documentation and community support matter as much as raw performance when you’re troubleshooting a black screen or a broken save file at 11pm, and this is another area where the three projects have diverged sharply since Nintendo’s enforcement campaign intensified. Ryubing maintains its own documentation independent of the frozen original Ryujinx wiki, and because it inherited years of accumulated Ryujinx troubleshooting threads, compatibility notes, and per-game configuration tips, new users benefit from a much deeper existing knowledge base than either Citron or Suyu can offer.
Citron’s community skews younger and more mobile-focused, which shows up in the kind of support content available: setup guides tend to center on Android APK installation, performance tuning for specific phone chipsets, and APK-based nightly builds rather than the desktop-first configuration deep dives common in Ryujinx communities. That’s a reasonable reflection of where Citron’s actual user base sits, but it can make troubleshooting a desktop-specific issue slightly harder to find answers for.
Suyu’s community support is now effectively frozen in place. Existing forum threads, Discord history, and cached documentation remain useful for anyone still running an installed copy, but there’s no one actively answering new questions about compatibility with games patched after September 13, 2026. If you hit an issue with a title that received a post-shutdown update, Suyu’s community simply isn’t positioned to help anymore, which is one more practical reason to treat it as a legacy tool rather than an ongoing platform.
Migration Guide: Moving From Suyu to Ryujinx or Citron
If Suyu’s shutdown left you needing a new emulator without losing your existing game library, save data, or configuration, the migration is mostly manageable, but a few steps are easy to skip and cause headaches later.
- Back up your save data first. Locate Suyu’s user data folder (typically under your user profile’s AppData or home directory on Linux) and copy the entire saves and nand directories before touching anything else.
- Export your keys and firmware files separately. Both Ryujinx-based forks and Citron require the same Switch prod.keys and firmware dump you were already using with Suyu; these files are emulator-agnostic and can be reused directly.
- Choose based on your priority, not habit. If you value stability and have an established game list, install Ryubing. If you’re on a phone or lower-power handheld and frame rate matters more than perfect accuracy, install Citron instead.
- Import save files into the new emulator’s expected directory structure. Directory layouts differ slightly between projects, so check each emulator’s documentation for where save data and firmware need to live rather than assuming a direct drag-and-drop will work.
- Reconfigure controller bindings and graphics settings from scratch. Configuration files are not cross-compatible between Suyu, Ryubing, and Citron, so budget 10 to 15 minutes to redo input mapping and resolution scaling settings.
- Test a save-heavy title first before committing. Load your most save-critical game first to confirm the imported save data works correctly before assuming the migration is complete.
- Keep your old Suyu installer archived locally. Since the GitHub org is archived, don’t rely on being able to redownload Suyu later if you decide you need to reference it or roll back.
For a broader walkthrough of getting any Switch emulator running from zero on a Windows PC, including the firmware and key extraction process shared across all three projects, our Nintendo Switch PC emulator setup guide covers the prerequisites step by step.
On Windows, the folders you’re moving files between typically look like this, though exact paths vary slightly by version:
Suyu save/firmware location (example):
%APPDATA%\suyu\nand\user\save\
Ryubing save/firmware location (example):
%APPDATA%\Ryujinx\bis\user\save\
Citron save/firmware location (example):
%APPDATA%\citron\nand\user\save\Copy the contents of the save subfolder for each game title individually rather than merging entire directories, since folder structures for firmware and system files differ enough between projects that a blind copy-paste can leave you with a broken install rather than a working migration.
Legal Risk: Nintendo’s DMCA Campaign and What It Means for You
The legal backdrop here isn’t static, and it directly explains why three separate emulators exist to fill Yuzu’s gap in the first place. Nintendo’s February 2024 lawsuit against Yuzu’s developers argued the emulator’s primary function was bypassing Switch encryption to enable piracy, a case strong enough that it ended in a settlement and shutdown within roughly a month of filing, according to court filings covered at the time by outlets including TorrentFreak. That set a precedent Nintendo has continued to use: rather than filing individual lawsuits against every successor project, the company has leaned on mass DMCA takedown notices sent directly to GitHub, which is exactly the mechanism that pulled 401 repositories, 311 of them containing Suyu code, in the August 2026 wave.
Ryujinx occupies a genuinely different legal position, since it predates the Yuzu case and was never named in that 2024 litigation. That doesn’t make it immune to a future takedown campaign, but it does mean its risk profile is based on a different, longer, and so far less legally-tested history than Suyu’s or Eden’s. Citron’s position is less clear-cut simply because it’s newer and hasn’t faced a comparable large-scale test yet, though the restoration of its Git services by mid-2026 after a temporary disruption suggests it has, at minimum, survived scrutiny so far.
None of this constitutes legal advice, and emulation law varies by jurisdiction. What’s verifiable is the pattern: Nintendo has demonstrated it will pursue both direct litigation and mass platform takedowns against Switch emulation projects, and no fork’s marketing distance from Yuzu has proven to be a reliable shield. Suyu’s archive notice this month is the clearest evidence yet that rebranding a codebase does not neutralize the underlying legal exposure.
Pros and Cons: Ryujinx vs Citron vs Suyu
Ryujinx / Ryubing
- Pro: Longest development history and strongest reputation for pre-2024 title compatibility
- Pro: Never named in Nintendo’s 2024 lawsuit, giving it a distinct legal history from Yuzu-derived forks
- Pro: Distributed independently of a single GitHub org through Ryubing’s self-hosted domain and mirrors
- Con: Original codebase frozen since October 2024, limiting how much structural performance work can happen
- Con: Relies on fork maintainers rather than an original development team
Citron
- Pro: Most actively developed option for Android and mobile play
- Pro: Consistent commit activity through 2026, including 76-plus commits since its December 2025 stable release
- Pro: Prioritizes frame rate, making it a practical pick for lower-power handhelds
- Con: Less time-tested for accuracy compared to Ryujinx’s longer compatibility history
- Con: Already experienced one Git infrastructure disruption in 2026, even though service was restored
Suyu
- Pro: Introduced a technically ambitious static recompilation approach in its final v0.04 build
- Con: Archived on GitHub as of September 13, 2026, with no maintained future path
- Con: Was the single most heavily targeted codebase in Nintendo’s August 2026 DMCA wave, with 311 of 401 removed repos containing Suyu code
- Con: No official channel remains to safely download new builds going forward
Which Switch Emulator Should You Use? 5 Scenarios
- You already have a large, working Ryujinx library: switch to Ryubing rather than rebuilding elsewhere. It’s the same codebase with active patching, and your existing saves and configs carry over directly.
- You’re gaming primarily on a phone: Citron is the more purpose-built option, given its Android-first development focus since early 2025.
- You’re setting up a Linux handheld from scratch: test both Ryubing and Citron, since both run on Linux and the better choice often comes down to which specific games you play rather than a universal winner.
- You had Suyu installed before September 13, 2026: keep your existing install for now if it still runs your games, but plan a migration to Ryubing or Citron since Suyu will not receive compatibility fixes for future game updates.
- You’re risk-averse about legal exposure: Ryujinx’s pre-lawsuit history and independence from Yuzu’s codebase make it the option with the longest track record, though no Switch emulator carries a guarantee against future enforcement action.
The Verdict: Which Emulator Wins in Late 2026
There isn’t a single winner here, because Ryujinx, Citron, and Suyu were never really solving the same problem in the same way. Ryujinx-based builds through Ryubing remain the safest default for desktop users with an established game library, backed by a development history that predates the entire Yuzu-fork ecosystem and a distribution model built to survive the kind of GitHub sweep that just ended Suyu. Citron earns its place as the practical choice for phone and handheld play, with a commit history through 2025 and 2026 that shows it kept shipping while two of its closest competitors, Eden and Suyu, got knocked off GitHub entirely.
Suyu, meanwhile, is the clearest cautionary tale in this comparison. It shipped its most technically interesting feature, a static AArch64-to-x86-64 recompiler, in the same week Nintendo’s DMCA campaign caught up with it, and the project is now archived with 311 of the 401 repositories removed in that August 2026 sweep tied directly to its code. If you’re choosing where to invest your setup time today, that data points toward Ryubing for stability and legacy compatibility, and Citron for mobile and frame-rate-sensitive play, while treating Suyu strictly as a legacy install rather than a forward-looking option.
Frequently Asked Questions
Is it legal to use Ryujinx, Citron, or Suyu?
Emulator software itself generally isn’t illegal, but how you obtain game files and firmware matters a great deal, and laws vary by country. Nintendo has pursued both direct lawsuits, as with Yuzu in 2024, and mass DMCA takedowns, as with the 401 repositories removed in August 2026, against projects it views as piracy-enabling. None of this article constitutes legal advice.
What happened to Suyu emulator in September 2026?
The suyu-emu GitHub organization was archived by an administrator on September 13, 2026, one day after coverage of its final v0.04 build. The archive followed an August 2026 DMCA campaign in which Nintendo’s notices led to 401 Switch-emulator repositories being removed from GitHub, 311 of which contained Suyu code.
Is Citron better than Ryujinx in 2026?
It depends on your priority. Citron has a stronger, more active development history for Android and lower-power hardware, while Ryujinx-based forks like Ryubing carry a longer, more established compatibility record for desktop play built up since 2017. Neither is objectively better across every use case.
Can I still download Suyu after the GitHub archive?
The official GitHub organization is archived and no longer distributes new builds. Existing installs continue to function, but there is no official channel for new downloads, and third-party mirrors carry additional trust and security risk that this article does not endorse.
Do I need a Switch console to use these emulators?
You need legally obtained firmware and encryption keys typically extracted from a console you own, along with game files you legally possess. None of the three projects covered here bundle Nintendo’s copyrighted firmware or games.
Which emulator works best on Android phones?
Citron has the strongest, most consistently maintained Android development history among the three, dating back to its v0.5 build in February 2025 and continuing through 2026. Ryujinx-based forks have more limited, community-patched Android support by comparison.
What is Ryubing and how is it different from Ryujinx?
Ryubing is a community fork of the original Ryujinx codebase, created after Ryujinx’s own development effectively stopped in October 2024. It carries forward Ryujinx’s compatibility work while continuing to ship patches, distributed through a self-hosted domain and mirrors rather than a single centralized GitHub repository.
Will Nintendo shut down Citron and Ryujinx too?
There’s no way to predict future legal action with certainty. Ryujinx’s history predates the 2024 Yuzu case and it was not named in that lawsuit, which sets it apart from Yuzu-derived forks like Suyu. Citron has not faced a comparable large-scale legal test as of this writing. Nintendo’s pattern through 2026 shows a willingness to pursue both lawsuits and mass DMCA takedowns against this entire category of software, so ongoing risk applies broadly rather than to any single project.
