Where Does ReVanced Manager Store Patches and Keystores?
ReVanced Manager works in app-private storage with exports to Downloads. Package names, keystore and APK flow.
Last updated
ReVanced Manager keeps working files where you cannot browse them. Patching scratch, input APKs and the signing keystore all live in private app storage under its package name. Root access aside, the file manager never shows that tree.
What you do see are the exports. Finished APKs leave through the export action into a folder you pick, usually Downloads. The signing keystore travels through Settings import and export. There is no ReVanced folder at storage root; guides naming one describe hopes rather than the app.
Where ReVanced Manager stores this, by platform
App-private storage (exports to Downloads)
Package app.revanced.manager.flutter for v1, app.revanced.manager for the Kotlin rewrite. Scratch in files/patcher, keystore in signing storage. Export patched APKs and the keystore to Downloads; old keystore paths under Android/data fail on modern scoped storage.
Frequently asked questions
Where are patched APKs saved?
Only where you export them. The Install button applies directly, while the export action writes the APK to your chosen folder, usually Downloads. Source APKs come from Downloads or installed apps the same way.
How do I back up my ReVanced keystore?
Use Manager Settings, Import or Export Keystore and keep the file somewhere safe. Updates signed with a different key install as a second app instead of an upgrade. Old keystore copies under Android/data hit permission errors on Android 11 and later.
Can I copy ReVanced working files by hand?
No. Patching scratch and input APKs sit in private storage that needs root to open. Treat exports as the only portable artifacts. Re-patch from sources on the new phone instead of migrating scratch dirs.
Notice an outdated path? Let us know.