Skip to content
Prod Keys Hub
Download v22.1.0

How to Install Prod Keys — Every Emulator, Every OS

Last updated

Installing prod keys means placing one file in one folder. Everything that goes wrong is a variation on that: the wrong folder, the wrong file name, or an emulator that was already running when you copied it.

Where the file goes

Each emulator has its own expected directory. Expand your emulator below for the path on each platform.

Where Suyu reads prod keys

  • Windows%APPDATA%/suyu/keys/
  • Linux~/.local/share/suyu/keys/
  • AndroidInternal/SuYu/keys/

Fork of Yuzu kept in development. Reads prod.keys from the keys folder and started requiring a current firmware dump for newer titles.


Where Ryujinx reads prod keys

  • Windows%APPDATA%/Ryujinx/system/
  • macOS~/.config/Ryujinx/system/
  • Linux~/.config/Ryujinx/system/

Uses the system folder rather than a keys folder. Both prod.keys and title.keys go into the same directory.


Where Yuzu reads prod keys

  • Windows%APPDATA%/yuzu/keys/
  • Linux~/.local/share/yuzu/keys/
  • AndroidInternal/yuzu/keys/

Discontinued, but still widely used. Older builds work with older key generations, which is why the archived versions remain listed.


Where Eden reads prod keys

  • Windows%APPDATA%/eden/keys/
  • Linux~/.config/eden/keys/
  • AndroidInternal/eden/keys/

Recent Yuzu-lineage build. Ships without keys, so it expects a current prod.keys before it will boot any game.


Where Citron reads prod keys

  • Windows%APPDATA%/citron/keys/
  • Linux~/.local/share/citron/keys/
  • AndroidInternal/Citron/keys/

Yuzu-based fork. Same keys folder layout as Suyu, different application data directory.


Where Sudachi reads prod keys

  • Windows%APPDATA%/sudachi/keys/
  • Linux~/.local/share/sudachi/keys/
  • AndroidInternal/Sudachi/keys/

Also Yuzu-lineage. Key requirement depends on the build date; very old builds pair with the keys release from the same month.

Step by step

  1. Get the file. Download the current release from the prod keys download page and extract it if needed.
  2. Create the folder if it does not exist. Emulators do not always create their keys directory on first run. Missing folder is the most common reason a copy appears to do nothing.
  3. Copy, do not rename. The file must be called prod.keys. On Windows, extensions are hidden by default, so a file named prod.keys.txt looks correct in Explorer and is wrong to the emulator.
  4. Restart the emulator. Close it fully rather than reopening a window.
  5. Confirm it loaded. Open the emulator’s key or system information screen. It should list the key generation it is using.

Title keys as well

Some builds also look for title.keys. In current versions the title key block is already derived from prod.keys, so the second file is usually redundant. See prod keys vs title keys if a game specifically asks for it.

Android

Phones and tablets do not expose these folders directly. Use the emulator’s own import option, described in prod keys on Android.

If it still does not work

Check the exact error text: keys not found means the emulator cannot see the file at all, while a decryption error means the file was found and rejected — a different problem with a different fix. The full breakdown is in prod keys not working.

Frequently asked questions

Where exactly do I put prod.keys?

In your emulator’s keys folder, or in its system folder for Ryujinx. The exact path for each platform is listed above.<br />

Do I need title.keys as well?

Usually not. Current builds derive title keys from prod.keys; older ones may still look for the file.<br />

Why does the emulator still say keys are missing after I copied them?

The folder may not have existed, the file may really be named prod.keys.txt, or the emulator was running and read the old state at startup.<br />