Where Does JuiceSSH Store Connections and Keys?
JuiceSSH keeps connections and keys in app-private storage, moved between devices through its export file.
Last updated
JuiceSSH stores connections, snippets, and identities in its own private database that other apps and file managers cannot see. There is no cloud account syncing them behind the scenes.
The way out is the export function in settings, which writes your connections to a file you place yourself. Import that file on the new device and everything reappears. Keys export the same way, which is convenient and exactly as dangerous as it sounds. Treat the export like a password dump.
Where JuiceSSH stores this, by platform
In-app export (Settings > Export); app-private storage otherwise
Connections, snippets, and identities live here, invisible to file managers. Use the in-app export to produce a portable file, then import it on the new device. Root file browsers can see the raw database, but export is the supported path.
Frequently asked questions
How do I move connections to a new phone?
Run the export again on the old device and import on the new one. There is no account sync, so the file is the whole migration path.
Does the export include my private keys?
Yes, and that is the point. Private keys never leave the app except through an export you trigger yourself, so guard that file like a password.
Notice an outdated path? Let us know.