Prod Keys on Android — Where the File Goes
Android emulators read keys from app storage. Since Android 11 that area is not browsable through a normal file manager, so desktop instructions copy the file somewhere the emulator never looks.
Use the in-app import
- Download the current keys release from the prod keys download page to your device.
- Open the emulator’s settings and find its key or system information screen.
- Use its import or install keys option and pick the downloaded file.
- Restart the emulator so the new file is read at startup.
Paths, if your file manager can reach them
| Emulator | Android path |
|---|---|
| Suyu | Internal/SuYu/keys/ |
| Yuzu | Internal/yuzu/keys/ |
| Eden | Internal/eden/keys/ |
| Citron | Internal/Citron/keys/ |
| Sudachi | Internal/Sudachi/keys/ |
When access is blocked
On Android 13 and later the path may be unreachable from a file manager even when it exists. The import option in the emulator bypasses the restriction entirely and is the reliable route. If your build has no import option, it predates scoped storage and expects the folder in shared storage instead — in that case the desktop instructions apply.
Related: install prod keys for desktop paths, and keys not found if the emulator still reports nothing.
Frequently asked questions
Where is the keys folder on Android?
Inside app storage, for example Internal/SuYu/keys/ for Suyu. Recent Android versions hide this from file managers.<br />
Why can I not see the emulator folder on Android 13?
Scoped storage restricts access to app directories. Use the emulator’s in-app import instead.<br />
Can I import keys from the emulator settings?
Yes on current builds. It is the recommended route because it avoids the storage restriction completely.<br />