How to add prod.keys to Ryujinx
| Quick answer: Place prod.keys (and optionally title.keys) in the system folder inside Ryujinx’s app data directory, then restart the emulator. Windows: %appdata%\Ryujinx\system\ Linux / Steam Deck: ~/.config/Ryujinx/system/ macOS: ~/Library/Application Support/Ryujinx/system/ |
Ryujinx requires a prod.keys file to decrypt and run Nintendo Switch games. Without it, the emulator will launch but refuse to load any game or firmware. This guide shows you exactly where to place the file, how to get it from your own Switch, and how to fix the most common key-related errors.
Contents
What you need before you start
Before placing any files, make sure you have the following:
- A Nintendo Switch console — needed to legally dump your own keys. Unpatched (V1) units and OLED/Lite models with a compatible modchip both work.
- Atmosphere CFW installed and running on your Switch.
- Lockpick_RCM — the tool used to extract keys from your console. Download it from the official GitHub repository.
- Ryujinx already installed on your PC, Mac, or Steam Deck.
| Note This guide only covers dumping keys from your own hardware, which is the legal method. Do not source prod.keys files from third-party websites. |
Step 1 — dump prod.keys from your Switch
Lockpick_RCM is a homebrew payload that reads your Switch’s encryption keys at boot and saves them to a file on your SD card.
- Power off your Switch completely.
- Enter RCM mode (hold Vol+ and press Power while holding the home button jig in the right Joy-Con slot on unpatched units; or use your modchip’s RCM shortcut on patched/OLED/Lite).
- Inject the Lockpick_RCM payload using your PC and a tool like TegraRcmGUI or fusee-launcher.
- On the Lockpick_RCM menu, select Dump from SysNAND to dump keys from your main system.
- Keys will be saved to /switch/prod.keys on your SD card. A title.keys file will also appear alongside it.
- Copy both files to your PC.
| Steam Deck / Linux note The process of dumping keys from your Switch is identical regardless of which platform you run Ryujinx on. The files are copied from your Switch SD card and placed on your Linux filesystem — the steps are the same. |
Step 2 — find the Ryujinx keys folder
Ryujinx stores its keys in a system subfolder inside its app data directory. The exact path depends on your operating system.
| OS | Keys folder path |
| Windows | %appdata%\Ryujinx\system\ |
| Linux | ~/.config/Ryujinx/system/ |
| Steam Deck | ~/.config/Ryujinx/system/ |
| macOS | ~/Library/Application Support/Ryujinx/system/ |
Shortcut: Inside Ryujinx, go to File > Open Ryujinx Folder. This opens the parent app data directory directly in your file manager. From there, navigate into the system folder.
| The system folder may not exist yet On a fresh Ryujinx installation, the system folder is not created automatically. If it is missing, create it manually inside the Ryujinx app data directory before placing your keys files. |
Step 3 — place prod.keys and title.keys
Copy prod.keys (and title.keys if you have it) directly into the system folder. Do not place them in a subfolder.
After copying, your system folder should contain:
- prod.keys — required for all games and firmware decryption
- title.keys — required for encrypted NSP files and DLC (not needed for XCI format games)
If you only play XCI format games, prod.keys alone is sufficient. If you install NSP files or DLC, you need title.keys as well.
Step 4 — verify keys are loaded
Restart Ryujinx completely after placing your keys files — the emulator reads them at startup, not dynamically.
To confirm the keys loaded correctly, go to Help > About. The dialog will show key status. You can also go to File > Open Ryujinx Folder and verify the files are present in system\.
If keys loaded successfully, games in your library will now show their title image and metadata instead of a blank entry. Attempting to launch a game will no longer show a keys-related error.
Common errors and fixes
| Error message | Fix |
| Keys not found | The prod.keys file is missing or in the wrong folder. Confirm it is placed directly inside the system\ folder, not in a subfolder or the root Ryujinx directory. |
| Key generation X missing | Your prod.keys file is from an older firmware dump than the firmware version installed in Ryujinx. Re-dump your keys after updating your Switch to the matching firmware version. |
| Keys are out of date | Same as above — the installed firmware requires a newer set of keys. Update your Switch firmware, then re-run Lockpick_RCM to get a fresh prod.keys. |
| Title key not found for NCA | The NSP or DLC you are trying to install requires an entry in title.keys that is missing. Re-dump title.keys from your Switch — it may have been updated after new games or DLC were purchased. |
| Could not load game — decryption failed | Usually caused by a mismatched prod.keys version. Match your firmware version to your keys version and restart Ryujinx. |
Frequently asked questions
Do I need to update prod.keys after a firmware update?
Yes. Nintendo’s firmware updates introduce new key generations. If you update Ryujinx’s firmware but your prod.keys file is from an older dump, you will see a “key generation missing” error. Re-run Lockpick_RCM after updating your Switch to generate a fresh prod.keys that includes the new key generation.
Do I need title.keys to play XCI files?
No. XCI files are raw cartridge dumps and are decrypted using prod.keys alone. title.keys is only required for NSP files (eShop format) and their associated DLC and updates.
Can I use the same prod.keys for Yuzu, Suyu, or Sudachi?
Yes. prod.keys and title.keys are the same files regardless of which Switch emulator you use. The keys are tied to your console’s firmware, not to any specific emulator. Copy the same files into the equivalent keys folder for whichever emulator you are setting up.
Where does Ryujinx store firmware separately from keys?
Ryujinx firmware files are stored in system\ alongside your keys, but installed through the emulator’s own interface via Tools > Install Firmware. Firmware and keys must be from the same version — mismatches are the most common cause of key generation errors.