Azahar is the community successor to Citra, and it is actively maintained. That matters for settings, because fixes and improvements continue to arrive, and the menus in Azahar do not always match older guides written for Citra. These settings are for Azahar, not for the final Citra builds. Use this guide when you have Azahar installed and you want a stable starting point for PC or Android, then adjust one setting at a time for each game.
If you have not installed Azahar yet, start with the Azahar Emulator download page. To check the current version, visit the official Azahar website.
Quick Answer
Azahar is the actively maintained community successor to Citra. As a starting point, use Internal Resolution Native 1x to 3x by device strength, Renderer Vulkan on modern hardware and OpenGL on older hardware, Hardware Shader Enabled, Disk Shader Cache Enabled, Accurate Multiplication Disabled, VSync Disabled, and Texture Filtering Disabled or Low. These settings can improve smoothness, but they do not guarantee a specific result.
| Setting | Recommended value |
|---|---|
| Internal Resolution | Native 1x to 3x by device strength |
| Renderer | Vulkan on modern hardware, OpenGL on older hardware |
| Hardware Shader | Enabled |
| Disk Shader Cache | Enabled |
| Accurate Geometry | Disabled |
| Accurate Multiplication | Disabled. Enable Accurate Multiplication only if a specific game shows shadow or graphic glitches, then test again. |
| VSync | Disabled. With VSync off, screen tearing can appear, especially in fast moving scenes. |
| Texture Filtering | Disabled or Low |
| CPU JIT | Enabled and kept on |
| Audio Stretching | OFF when emulation speed drops below 100 percent, ON when speed is stable |
Audio Stretching is a tradeoff. When speed is stable, keep Audio Stretching ON, because it keeps sound smooth and in sync with the game. When speed drops below 100 percent, turn Audio Stretching OFF, because stretched audio can sound slow and distorted at low speed. With Audio Stretching OFF at low speed, sound may cut out or skip during slow moments, but it will not sound stretched. Use that tradeoff consistently in every section below.
How Azahar Settings Differ From Citra Settings
Azahar builds on the same 3DS emulation approach as Citra, so the main ideas are familiar. Graphics, system, CPU and audio settings still control resolution, rendering, speed and sound. The difference is in the details. Menu names and menu order can differ, some options can move to a different tab, and compatibility fixes continue to arrive because Azahar is actively maintained. That is why a setting that worked in a final Citra build is not always the right choice in Azahar, and why you should test a changed setting in Azahar itself instead of copying an old Citra profile without checking it. For a direct comparison of the two projects, read the Citra vs Azahar comparison.
The table above is written for Azahar. If you switch between the two projects, keep the profiles separate, and check the renderer, resolution and audio settings again after you change projects. For older Citra guidance, see the Best Citra Emulator Settings.
Best Settings for PC
Low End PC
For a low end PC, start with Native 1x internal resolution. Use OpenGL as the renderer, because older hardware is more likely to run it without extra problems. Keep Hardware Shader Enabled and Disk Shader Cache Enabled. Set Accurate Geometry to Disabled and Accurate Multiplication to Disabled. Set VSync to Disabled, and keep in mind that screen tearing can appear with VSync off. Set Texture Filtering to Disabled. Keep CPU JIT Enabled and kept on. For audio, use Audio Stretching OFF when emulation speed drops below 100 percent, and ON when speed is stable.
On a low end PC, resolution is the first setting to lower when a game slows down. Do not raise resolution before you have tested the game at Native 1x, and do not turn CPU JIT off to try to fix a slow game, because CPU JIT should stay on.
Mid Range PC
For a mid range PC, start with 2x internal resolution. Use Vulkan on modern hardware, and OpenGL on older hardware. Keep Hardware Shader Enabled and Disk Shader Cache Enabled. Set Accurate Geometry to Disabled and Accurate Multiplication to Disabled, with the rule that Accurate Multiplication should be enabled only if a specific game shows shadow or graphic glitches, then tested again. Set VSync to Disabled, with the screen tearing note that tearing can appear when VSync is off. Set Texture Filtering to Low. Keep CPU JIT Enabled and kept on. For audio, use Audio Stretching OFF when emulation speed drops below 100 percent, and ON when speed is stable.
A mid range PC can usually hold 2x for most games. If a demanding game slows down, return to Native 1x for that game only, using a per game setting, instead of changing your global settings for every game.
High End PC
For a high end PC, start with 3x internal resolution. Use Vulkan on modern hardware, because modern hardware is the case where Vulkan is the recommended renderer in the table above. Keep Hardware Shader Enabled and Disk Shader Cache Enabled. Set Accurate Geometry to Disabled and Accurate Multiplication to Disabled, with the same rule. Enable Accurate Multiplication only if a specific game shows shadow or graphic glitches, then test again. Set VSync to Disabled, and remember that screen tearing can appear with VSync off. Set Texture Filtering to Low. Keep CPU JIT Enabled and kept on. For audio, use Audio Stretching OFF when emulation speed drops below 100 percent, and ON when speed is stable.
A high end PC does not need a higher starting resolution than 3x in this guide. Start at 3x, test the game, and lower the resolution for a specific game if it slows down, instead of raising resolution and then trying to fix other settings to compensate.
Best Settings for Android
Low End Android
For a low end Android device, start with Native 1x internal resolution. Use OpenGL as the renderer. Keep Hardware Shader Enabled and Disk Shader Cache Enabled. Set Accurate Geometry to Disabled and Accurate Multiplication to Disabled. Set VSync to Disabled, with the screen tearing note that tearing can appear when VSync is off. Set Texture Filtering to Disabled. Keep CPU JIT Enabled and kept on. For audio, use Audio Stretching OFF when emulation speed drops below 100 percent, and ON when speed is stable.
On Android, the screen layout also matters for comfort. Use a layout that keeps the main screen large and the touch screen reachable. Change layout only after the graphics and CPU settings are stable, so you can tell whether a problem comes from resolution, rendering or layout.
Mid Range Android
For a mid range Android device, start with 2x internal resolution. Use Vulkan on modern hardware, and OpenGL on older hardware. Keep Hardware Shader Enabled and Disk Shader Cache Enabled. Set Accurate Geometry to Disabled and Accurate Multiplication to Disabled, with the rule that Accurate Multiplication should be enabled only if a specific game shows shadow or graphic glitches, then tested again. Set VSync to Disabled, with the screen tearing note that tearing can appear when VSync is off. Set Texture Filtering to Low. Keep CPU JIT Enabled and kept on. For audio, use Audio Stretching OFF when emulation speed drops below 100 percent, and ON when speed is stable.
High End Android
For a high end Android device, start with 3x internal resolution. Use Vulkan on modern hardware. Keep Hardware Shader Enabled and Disk Shader Cache Enabled. Set Accurate Geometry to Disabled and Accurate Multiplication to Disabled, with the same rule. Enable Accurate Multiplication only if a specific game shows shadow or graphic glitches, then test again. Set VSync to Disabled, and remember that screen tearing can appear with VSync off. Set Texture Filtering to Low. Keep CPU JIT Enabled and kept on. For audio, use Audio Stretching OFF when emulation speed drops below 100 percent, and ON when speed is stable.
On Android, a high end device still benefits from per game testing. A game that runs well at 3x does not prove that every game will run well at 3x, so lower the resolution for a demanding game instead of changing your global settings.
Graphics Settings Step by Step
- Open Azahar, then open Settings. On PC, open the configuration window. On Android, open Settings from the menu.
- Open the graphics section. This is where the renderer and resolution settings are found.
- Set the Renderer to Vulkan on modern hardware, and to OpenGL on older hardware. If a game shows graphic problems with one renderer, switch to the other renderer and test the same part of the game again.
- Set Internal Resolution to Native 1x to 3x by device strength. Use Native 1x for a low end device, 2x for a mid range device, and 3x for a high end device.
- Set Hardware Shader to Enabled.
- Set Disk Shader Cache to Enabled. This helps Azahar reuse shader work it has already done, instead of repeating it.
- Set Accurate Geometry to Disabled.
- Set Accurate Multiplication to Disabled. Enable Accurate Multiplication only if a specific game shows shadow or graphic glitches, then test again. If the glitches do not improve, return Accurate Multiplication to Disabled and try the other renderer.
- Set VSync to Disabled. With VSync off, screen tearing can appear, especially in fast moving scenes. If tearing is distracting for a specific game, test VSync on for that game, but keep Disabled as your starting point.
- Set Texture Filtering to Disabled or Low. Use Disabled for a low end device, and Low for a mid range or high end device.
- Save the settings, start a game, and test the same area you tested before. Change only one setting at a time after this point.
Graphics settings have the largest effect on both appearance and speed. Resolution changes how sharp the image looks, and the renderer changes how the image is drawn. Hardware Shader and Disk Shader Cache help Azahar handle shader work more smoothly, while Accurate Geometry and Accurate Multiplication are accuracy options that should stay off unless a specific game needs them. Texture Filtering changes how textures are smoothed, so Disabled or Low keeps the load lower than a stronger filter would. For the full installation and setup steps, see the Azahar setup guide.
System and CPU Settings
System settings do not affect speed as much as graphics settings, but they are worth setting once. Set your username and language to the values you want games to use. Some games show your username, and language controls the language games use when they support it. Set the system region to match the games you play when that option is available, because region can affect how a game behaves.
For CPU settings, the rule in this guide is simple. Keep CPU JIT Enabled and kept on. CPU JIT is the setting that allows Azahar to run game code at a usable speed. Turning CPU JIT off will make games run much more slowly, so do not turn it off as a fix for a slow game or a graphic problem. If a game is slow, check Internal Resolution and Renderer first, and check that CPU JIT is still Enabled, before you change any other setting.
Layout settings are also part of the system experience. The 3DS had two screens, a larger top screen and a smaller bottom touch screen. Azahar lets you arrange those screens in different ways. Use a large screen layout on PC, a side by side layout on a wide monitor if you prefer equal screens, and a single screen or large screen layout on a small Android screen. Layout changes appearance and touch control, not the core graphics table above, so set layout after the main settings are stable.
Audio Settings
Audio settings rarely need many changes, but Audio Stretching is the one setting to get right. The rule is consistent with the table above. Use Audio Stretching OFF when emulation speed drops below 100 percent, and ON when speed is stable. That tradeoff is the same on PC and Android, and it is the same for low end, mid range and high end devices.
When speed is stable, Audio Stretching ON keeps sound smooth and in sync with the game. When speed drops below 100 percent, Audio Stretching OFF avoids stretched, slow sounding audio, even though sound may cut out or skip during slow moments. Do not use Audio Stretching ON to hide a speed problem. If speed is often below 100 percent, lower Internal Resolution or switch Renderer first, then set Audio Stretching again using the same rule.
For output, leave the output device on its default value unless sound is coming from the wrong speaker or device. If sound is on the wrong device, change only the output device, test the game again, and leave the other audio settings unchanged.
Testing Settings Per Game
Global settings are your starting point, not your final answer for every game. Test settings per game with a simple method. First, set the global table above. Second, start a game and play the same area for a short time, so you have a clear baseline. Third, change one setting only, for example Internal Resolution from 3x to 2x, or Renderer from Vulkan to OpenGL. Fourth, play the same area again and compare the result. Fifth, keep the change only if the game behaves better, and undo it if the game behaves worse.
Use a per game setting when a change helps one game but would hurt other games. For example, use a lower resolution for a demanding game, use the other renderer for a game with graphic problems, or enable Accurate Multiplication for a game with shadow or graphic glitches, then test again. Keep CPU JIT Enabled for per game settings as well, because CPU JIT should stay on in every case in this guide. Save the per game setting, test it again after you restart the game, and do not stack several changes at once, because stacked changes make it hard to know which setting helped.
Common Settings Problems
Game runs slowly
Lower Internal Resolution by one step, for example from 3x to 2x, or from 2x to Native 1x. Check that CPU JIT is Enabled and kept on. Switch Renderer, from Vulkan to OpenGL, or from OpenGL to Vulkan, depending on your hardware, and test the same area again. Set Texture Filtering to Disabled if it is set higher. Check Audio Stretching using the speed rule. Use Audio Stretching OFF when emulation speed drops below 100 percent, and ON when speed is stable.
Game shows shadow or graphic glitches
Enable Accurate Multiplication only if a specific game shows shadow or graphic glitches, then test again. If the glitches remain, return Accurate Multiplication to Disabled and switch Renderer, because many graphic problems are specific to one renderer. Check that Accurate Geometry is Disabled, and check Texture Filtering, using Disabled or Low. Do not change several graphics settings at once, because you will not know which change fixed the problem.
Screen tearing appears
Screen tearing can appear when VSync is Disabled. That is the expected tradeoff in the table above. If tearing is distracting for a specific game, test VSync on for that game only, and compare the result in the same area. If VSync on makes the game feel less responsive, return VSync to Disabled and accept the tearing as the starting setting in this guide.
Audio sounds stretched, slow, or out of sync
Check emulation speed first, then set Audio Stretching using the same tradeoff. Use Audio Stretching OFF when emulation speed drops below 100 percent, and ON when speed is stable. If speed is stable and sound is still out of sync, check that the output device is correct, and test the game again. Do not change graphics settings to fix an audio problem unless speed is also low, in which case lower Internal Resolution first.
Game looks blurry
Check Internal Resolution first. Use Native 1x to 3x by device strength, with 1x for a low end device, 2x for a mid range device, and 3x for a high end device. If the image is still blurry at the correct resolution for your device, check Texture Filtering, using Disabled or Low, and check Renderer, using Vulkan on modern hardware and OpenGL on older hardware. Raise resolution only if the game still runs at stable speed after the change.
Frequently Asked Questions
What is Azahar?
Azahar is the community successor to Citra, and it is actively maintained. It is a separate project from the final Citra builds, so its settings and compatibility fixes are not identical to Citra.
What renderer should I use in Azahar?
Use Vulkan on modern hardware, and OpenGL on older hardware. If a game shows graphic problems with one renderer, switch to the other renderer and test the same part of the game again.
What internal resolution should I use in Azahar?
Use Native 1x to 3x by device strength. Use Native 1x for a low end device, 2x for a mid range device, and 3x for a high end device.
Should I keep CPU JIT on?
Yes. Keep CPU JIT Enabled and kept on. Turning CPU JIT off will make games run much more slowly.
What should I do if a game shows shadow or graphic glitches?
Enable Accurate Multiplication only if a specific game shows shadow or graphic glitches, then test again. If the glitches remain, return Accurate Multiplication to Disabled and switch Renderer.
Should VSync be on or off?
Use VSync Disabled as your starting point. With VSync off, screen tearing can appear, especially in fast moving scenes. Test VSync on for a specific game only if tearing is distracting.
What is the correct Audio Stretching setting?
Use Audio Stretching OFF when emulation speed drops below 100 percent, and ON when speed is stable. When speed is stable, ON keeps sound smooth and in sync. When speed drops below 100 percent, OFF avoids stretched, slow sounding audio.
How do I test settings for one game?
Change one setting only, play the same area again, and keep the change only if the game behaves better. Use a per game setting when a change helps one game but would hurt other games.
Are these settings for Citra?
No. These settings are for Azahar, not for the final Citra builds. Azahar is the community successor to Citra, and it is actively maintained, so check Azahar settings in Azahar itself.
Conclusion
Start with the Quick Answer table, choose resolution by device strength, use Vulkan on modern hardware and OpenGL on older hardware, keep Hardware Shader Enabled, Disk Shader Cache Enabled, CPU JIT Enabled, and Accurate Geometry and Accurate Multiplication Disabled, except for the glitch rule above. Keep VSync Disabled, with the screen tearing note in mind, and set Texture Filtering to Disabled or Low. Use Audio Stretching OFF when emulation speed drops below 100 percent, and ON when speed is stable. Test one game at a time, change one setting at a time, and use per game settings when a single game needs a different value. That method gives you a stable Azahar setup without changing settings you do not understand.
