Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/azahar-emu/azahar/llms.txt

Use this file to discover all available pages before exploring further.

Azahar is an open-source Nintendo 3DS emulator built on the foundation of Citra. Whether you’re getting started for the first time or running into something unexpected, the questions below cover what most users want to know.
Azahar does not provide, host, or link to game ROMs. You must dump games from cartridges or installed titles you legally own using tools such as GodMode9 on a hacked 3DS console.
Downloading ROMs from the internet — even for games you own — is illegal in many countries and is not supported by the Azahar project.
Azahar can load games in the following formats:
FormatDescription
.3dsDecrypted ROM dump (cartridge)
.ciaInstallable archive (eShop / updates / DLC)
.cxiExecutable image (component of a .cia)
.3dsxHomebrew executable
.elfDeveloper / debug executable
For retail games, .3ds is the most common format produced by cartridge-dumping tools.
Save data is stored in Azahar’s user data directory, which varies by platform:
PlatformDefault path
Windows%APPDATA%\Azahar\
macOS~/Library/Application Support/Azahar/
Linux (native)~/.local/share/azahar-emu/
Linux (Flatpak)~/.var/app/org.azahar_emu.Azahar/data/azahar-emu/
AndroidInternal storage, accessible via File Manager in-app
You can open the user data directory directly from Azahar via File → Open Azahar Folder.
Yes. You can transfer save files from a real 3DS to Azahar and vice versa, provided you dump them with a compatible tool.
1

Dump the save from your 3DS

Use Checkpoint or GodMode9 to export the save file from your console.
2

Locate the save directory in Azahar

Open File → Open Azahar Folder, then navigate to sdmc/Nintendo 3DS/.../title/... to find the matching title’s save location.
3

Copy the save file

Place the dumped save file in the correct directory, overwriting the existing one if present.
Save file formats differ between games. Always back up existing saves before replacing them.
Azahar has high compatibility across the 3DS library, but not every title runs perfectly. A small number of games have known graphical glitches, crashes, or are unplayable.Check the Azahar compatibility list before playing a specific title to see community-reported results. You can also contribute your own results after finishing a game.
Compatibility improves with each release. A game that didn’t work in an older version may work in a newer one.
Poor performance is usually caused by one of the following:
  • Your CPU is below the minimum requirement. Azahar requires a CPU with a single-core Passmark score above 1,800 and SSE4.2 support on x86_64.
  • You are using the wrong graphics backend. Try switching between OpenGL and Vulkan in Emulation → Configure → Graphics.
  • Hardware shader compilation is disabled. Enable Use Hardware Shaders in the Graphics settings.
  • Internal resolution is set too high. Reduce it in Emulation → Configure → Enhancements.
See Fix Common Azahar Problems for step-by-step guidance.
Yes. Azahar includes a built-in multiplayer system that lets you play with others over the internet or a local network. It operates through community-hosted rooms and does not connect to Nintendo’s servers.To join or host a room, open Multiplayer from the menu bar. The default port is 24872 — ensure this is open in your firewall if you are hosting.
All players in a room must use the same game version and the same Azahar build for online play to work correctly.
Yes. Azahar supports Android with the following minimum requirements:
  • Android 10.0 or later (64-bit)
  • Snapdragon 835 SoC or equivalent
  • OpenGL ES 3.2 or Vulkan 1.1 support
  • 2 GB RAM (4 GB recommended)
Performance on Android depends heavily on your device’s single-core CPU performance. Not all games that run well on desktop will run at full speed on mobile.
Azahar offers two Android variants:
VanillaGoogle Play
DistributionGitHub / Obtainium APKGoogle Play Store
File managementAlternative method (faster)Play Store–compliant method
Automatic updatesVia ObtainiumVia Play Store
Recommended forAdvanced usersMost users
The Vanilla build uses a faster file management method that is not permitted on the Google Play Store. For most users, the Google Play build is the easier choice. If you want the Vanilla build, install it through Obtainium or directly from the Releases page.
  • Bug reports: Open an issue on the GitHub repository. Include your system configuration, a log file, and reproduction steps. Tech support questions do not belong in the issue tracker.
  • Feature requests: Open a Feature Request issue on GitHub before writing any code, so the team can discuss whether the addition is appropriate.
  • Community help: Join the Discord server for real-time help from the community.
Search existing issues before filing a new one. Duplicate reports slow down the development process.
How you update depends on how you installed Azahar:
Installation methodHow to update
Windows installerDownload and run the new installer from Releases
Windows ZIPExtract the new archive, replacing the old files
macOS universalDownload the new .dmg from Releases
Linux FlatpakRun flatpak update org.azahar_emu.Azahar
Linux AppImageDownload the new AppImage from Releases
Android (Play Store)Update through the Play Store
Android (Obtainium)Obtainium checks for updates automatically
Android (manual APK)Download the new APK from Releases
Your save data and configuration are stored separately from the Azahar application files and are preserved across updates.

Build docs developers (and LLMs) love

Get started for freeTalk to us