When you launch a game on Citra, the emulator engages a complex chain of processes that hinge entirely on the files it reads and writes. Understanding what files Citra uses is essential for troubleshooting performance issues, managing your library, and ensuring your progress remains safe. The software relies on a structured ecosystem of configuration files, cache data, firmware dumps, and state records to function smoothly.
Core Configuration and Initialization Files
At the heart of Citra’s operation are the core configuration files that define how the emulator behaves the moment it starts. These files store user preferences, controller mappings, and logging settings that persist between sessions. If these files are corrupted or missing, Citra will revert to default settings, which can lead to confusion if specific configurations feel lost.
INIs and INI Directories
Citra primarily uses INI-style text files to store readable configuration data. The main qt.ini file handles the layout of the main window, while input.ini stores your specific keybindings and controller profiles. These files are located in the sdmc directory if you are using a portable installation, or within the user’s application data folder on Windows and the config directory on Linux and macOS.
The Cache and Temporary Data Ecosystem
To maintain high frame rates and reduce load times, Citra generates substantial cache files during operation. These files are not strictly necessary for the emulator to run, but they significantly enhance the user experience by storing pre-rendered data and system information.
Shader Cache and Preloading
One of the most resource-intensive aspects of emulation is the real-time translation of GPU shaders. Citra mitigates this by creating a shader cache , which stores the compiled versions of these programs. This cache is usually stored in a folder dedicated to temporary data and is specific to your CPU architecture. By reusing this cache, Citra avoids the stutter that occurs when shaders are recompiled on every launch.
Firmware and BIOS Requirements
Unlike many modern emulators, Citra cannot operate entirely out of the box because it requires the original proprietary firmware from Nintendo consoles. These files are copyrighted, and users must extract them from their own hardware. The specific files Citra looks for depend on the game being played.
Required Firmware Files
3DS BIOS (ciasa) : Required for initializing the 3DS environment.
DSi BIOS (769f797590689658) : Needed for DSi-specific titles.
DSP1/2 Firmware : Handles audio processing for legacy games.
If Citra detects that the correct firmware is missing, it will prompt the user to locate the file manually, usually with a clear error message indicating the exact hash or filename it is searching for.
Game Storage and the SDMC
Citra uses a concept called the SDMC (Secure Device Memory Card) to represent the file system of a Nintendo 3DS. This means that games are mounted into a directory structure that mimics a physical SD card. Depending on the title, Citra will look for specific files within this structure to load the correct assets.
File Format Variations
For .3ds files, Citra looks for a singular binary blob that contains the entire game. For .cia files, which are archives used for digital distribution, Citra extracts the necessary binaries on the fly. When dealing with .sav files, which are raw memory dumps, Citra treats them as the equivalent of a physical cartridge’s battery-backed RAM, loading the exact state of the game’s memory.
