Ryujinx Folder: New
The Ultimate Guide to Ryujinx Folder: A New Era for Nintendo Switch Emulation
Ryujinx/
├── portable/ (if used)
│ ├── Config.json
│ ├── bis/ (system partitions)
│ ├── firmware/ (extracted Switch system archives)
│ ├── system/ (contains prod.keys, title.keys)
│ ├── sdmc/ (emulated SD card: saves, screenshots, mods)
│ ├── games/ (linked game directories)
│ └── shaderCache/
Q5: Does Ryujinx automatically create a new folder after an update?
No. Updates only replace the emulator executable. Your existing data folder remains untouched unless you explicitly delete it. ryujinx folder new
- Portability: You can now put Ryujinx on a USB stick and take your games, saves, and settings to a friend's house or a different PC without needing to reinstall anything.
- Permissions Issues: In the past, Ryujinx often needed Administrator privileges to write save files to system folders like
Program Files. Now, it writes to its own folder, eliminating the need to run the emulator as an Admin.
- Easy Backups: To backup your entire Switch experience, you just need to zip the one Ryujinx folder. No more hunting through hidden AppData folders.
- Create a new directory:
C:\Ryujinx-New.
- Copy only
Ryujinx.exe into it (or the whole app if preferred).
- Run
ryujinx --portable from that directory.
macOS
~/Library/Application Support/Ryujinx
11) Updating Ryujinx and rollback
- Keep a copy of the previous working Ryujinx binary in /updates before applying a new release.
- Test new builds with a small set of games first.
How to Migrate Your Data (Don't Lose Your Saves!)
If you used Ryujinx before and updated to a new version that uses this structure, you might be staring at a blank library. Here is how to fix it: The Ultimate Guide to Ryujinx Folder: A New
4. Moving or duplicating your folder (multiple profiles)
- To create a second profile, copy the entire Ryujinx folder to a new location and launch the executable from that folder — each folder acts independently.
- Edit config.json or use the GUI to change directories for shaders, saves, and ROM paths if you want shared caches or separate ones.
- Be careful with identical prod.keys: they can be reused across copies, but do not mix NAND folders if you want separate user save states.