- Top Pick: Valve Steam Deck OLED 512GB
- Runner-up: 8BitDo Ultimate 2 Bluetooth Controller
- Also consider: Samsung T9 Portable SSD 2TB
Anyone who last checked in a couple of years ago remembers a different landscape. Citra was the default answer for Nintendo 3DS emulation on every desktop platform, Linux included, and then it simply stopped. Readers still ask whether 3DS emulation on Linux died with it, or whether something credible picked up the work.
Something did. The Citra codebase now lives on in Azahar, an open-source fork built from the two most serious post-Citra projects, and it ships official Linux builds that are maintained today. This status report covers where the emulator came from, what state the Linux version is in, what hardware the project itself asks for, and how the two-screen design is handled on a single Linux display.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Yes, 3DS emulation on Linux is in good health. Citra was discontinued in March 2024, but its code lives on in Azahar, the actively maintained fork formed from Lime3DS and PabloMK7’s Citra fork. Azahar ships official Linux builds as a Flathub Flatpak and AppImage, and plays decrypted dumps of games from your own 3DS.
What actually happened to Citra
The facts are short and well documented. Citra was developed by the same team responsible for Yuzu, the Nintendo Switch emulator. When that team shut Yuzu down in early March 2024 under a legal settlement, Citra was discontinued at the same time, on 4 March 2024. Its website, downloads and development all stopped together.
That left Linux users in an odd position. Old Citra builds still circulate on the internet, and many still run, but they are frozen software: no bug fixes, no compatibility work and no official place to get them. For a while the practical question was which community fork, if any, would consolidate enough developers to become the real successor.
The successor: how Azahar came together
Two forks carried the codebase through 2024. Lime3DS focused on stability and platform support, while a fork maintained by PabloMK7, a former Citra developer, concentrated on performance and online play. Rather than compete, the two projects merged in late 2024 into a single emulator named Azahar, and the first public releases followed in early 2025.
The Azahar project describes itself as a free and open-source high-level Nintendo 3DS emulator, and its stated goal is to be the de facto platform for future 3DS emulation development. Development is public, releases are regular, and the version line has continued advancing through 2026. In practical terms, the succession question that hung over the scene in 2024 is settled: Azahar is where the developers, the releases and the documentation now live.
The Linux build, as it stands
Linux is a first-class platform for Azahar, with two official routes. The project recommends the Flatpak published on Flathub, which covers both x86-64 and ARM64 machines and updates through the normal Flatpak channel. For readers who avoid Flatpak, the releases page offers an AppImage in two variants, a default build and a native Wayland build. The project’s own guidance is to use the default AppImage unless you specifically need native Wayland without Xwayland, because of upstream Wayland issues that can affect the emulator. The Flatpak likewise ships with native Wayland support disabled by default, and it can be switched on with Flatseal if your setup requires it.
Azahar also exists as a Libretro core, so readers who run their emulation through RetroArch on Linux can use the same emulator inside that frontend, with the core’s own documented layout and input options. Either way, Linux builds are published by the project itself on the same release cycle as the Windows and macOS builds, not ported afterwards by third parties.
What your hardware needs to do
The project publishes its own minimum requirements, and they are modest by current standards. It asks for a modern 64-bit Linux system, an x86-64 or ARM64 processor, a graphics card supporting OpenGL 4.3 or Vulkan 1.1, and 2 GB of RAM, with 4 GB recommended. The one figure worth reading carefully is the CPU guidance: the project lists a single-core PassMark score above 1,800 as its baseline, because 3DS emulation leans heavily on one fast thread for its recompiled code.
Translated into shopping terms, almost any desktop or laptop built in the last several years clears the bar, and handheld PCs in the Steam Deck class run the emulator from the same Flathub package. Where older hardware struggles, it is usually the single-core figure, not the graphics card, that decides it.
The two-screen problem
Every 3DS emulator has to answer the same design question: the original hardware has two screens of different sizes, the lower one is a touchscreen, and your Linux display is one rectangle. Azahar’s documented layout options give you the main answers. The default top-bottom layout stacks both screens in the familiar arrangement. A large-screen layout shows both with one emphasised and an adjustable size ratio. Side-by-side suits wide monitors, and a single-screen mode shows one screen at a time with a configured way to swap. On the desktop builds, the two screens can also be placed in separate windows, which is the cleanest route for a genuine two-monitor setup: top screen on the main display, touch screen on the second.
Touch input is handled by the mouse in the standard configuration, and the Libretro core documents a mouse touchscreen mode for the bottom screen. A pen tablet is the closer match for stylus-driven games, since the original lower screen was designed around a stylus rather than a fingertip. Stereoscopic 3D is an output option rather than a requirement: the documented modes include side-by-side, red-cyan anaglyph and interlaced presentations for suitable displays, and ordinary flat play needs none of them.
Your games: dumps from your own hardware
Azahar follows the rule that defines legitimate emulation: it plays decrypted dumps of games you own, produced from your own 3DS hardware. The project’s documentation covers the dumping process for cartridges and installed titles using homebrew tools on a modified console, and the emulator works with the decrypted files that process produces. Azahar does not include games, and it does not ship the console’s encryption keys; support for loading encrypted content was removed, which is why the own-hardware dump is the supported path.
Nothing in this article points you at game downloads, and no emulator in this space legitimately can. The practical consequence is a one-time job: dump your own cartridges once, keep the files with the rest of your game library, and Azahar will treat them like any other local collection.
How to choose
Pick the install route first. The Flathub Flatpak is the project’s recommendation and the easiest to keep updated on any distribution, including SteamOS on a Steam Deck. Choose the AppImage if you want a portable file you control, and take the default variant unless you already know you need native Wayland. Choose the RetroArch core only if your whole library already lives in RetroArch and you accept its menus following the core documentation rather than the standalone app.
Pick the layout second, per game rather than globally. Top-bottom is the honest default; large-screen suits titles where the lower panel is mostly a map or inventory; separate windows are worth it if you have a second monitor and a game that lives on its touch screen. Finally, decide your touch input: a mouse is fine for menu-driven games, while a pen tablet earns its place for stylus-heavy ones.
Gear that shapes the setup
Valve Steam Deck OLED 512GB
The handheld route to Azahar: install the Flathub build in desktop mode, and the Deck’s touchscreen gives the lower 3DS screen a touch surface.
Specs:
– 7.4-inch HDR OLED display, 1280 by 800, touchscreen
– AMD Zen 2 quad-core APU with RDNA 2 graphics, 16 GB LPDDR5 memory
– 512 GB NVMe internal storage, microSD expansion slot
– Runs SteamOS, with the Azahar Flatpak available through Flathub in desktop mode
8BitDo Ultimate 2 Bluetooth Controller
A conventional pad for the many 3DS titles that barely use the touch screen, pairing over Bluetooth as a standard gamepad on Linux.
Specs:
– Bluetooth, 2.4 GHz wireless and wired USB-C connection modes
– TMR electromagnetic joysticks and tactile bumpers, per the maker
– Extra shoulder buttons and back buttons, programmable in the maker’s software
– Charging dock included in the box
Samsung T9 Portable SSD 2TB
Room for a dumped cartridge library plus the rest of a retro collection, on a drive that moves between a desktop and a handheld dock.
Specs:
– 2 TB capacity, USB 3.2 Gen 2×2 interface
– Maker-stated sequential read speeds up to 2,000 MB per second on a Gen 2×2 host; slower host ports run at their own ceiling
– USB-C connection, compact metal enclosure
SanDisk 1TB Extreme microSDXC
The expansion card that turns a handheld’s storage from a limit into an afterthought for a 3DS library.
Specs:
– 1 TB capacity, model SDSQXAV-1T00-GN6MA
– UHS-I microSDXC, A2 app performance class
– Maker-stated read speeds up to 190 MB per second with a compatible reader
One by Wacom Small (CTL-472)
A pen tablet that maps to the emulated touch screen, for stylus-first games a mouse handles clumsily. Wacom tablets work through the Linux kernel’s own input drivers.
Specs:
– Active area 152 by 95 mm, 2540 lines per inch resolution
– Battery-free cordless pen with 2,048 pressure levels
– Wired USB connection, three replacement nibs included
– Tablet body 210 by 146 mm, roughly 250 g
Who should skip this
Skip Azahar if your 3DS library exists only as encrypted files you cannot dump yourself, because the emulator’s supported path starts with your own hardware. Skip it if you expect the stereoscopic 3D effect to be the main event on ordinary monitors; it is an optional output mode, not the standard experience. Skip it if your machine falls short of the project’s stated single-core CPU guidance and you are unwilling to lower your expectations for the most demanding titles. And with a working 3DS and a small library, the original hardware remains the zero-setup option.
FAQ
Is Citra ever coming back?
No. Citra was discontinued on 4 March 2024 and its developers moved on. Its code continues through Azahar, which is the maintained project receiving releases.
Does Azahar run on the Steam Deck?
Yes. The project publishes its Linux build through Flathub, which installs on SteamOS in desktop mode like any other Flatpak, and the Deck’s touchscreen can serve as the lower 3DS screen.
Do I need a BIOS file or keys from the internet?
No. Azahar works with decrypted dumps of your own games, made from your own console using the process the project documents. It does not require, include or point to keys or game files from the internet.
Can I use my old Citra save files?
Saves live with the game data rather than the emulator brand. Point Azahar at the same decrypted game files and the save data stored alongside them on your own machine, and a Citra-era library generally carries across.
Final verdict
The status of 3DS emulation on Linux in late 2026 is better than the headlines of 2024 suggested. Citra is gone for good, but the consolidation into Azahar gave the scene one maintained emulator with official Linux builds, published hardware requirements and documented answers to the platform’s two real problems: the second screen and the touch input. If you own 3DS games and a Linux machine, the path from your cartridges to your screen is documented, supported and current.










