Where Does RetroShare Store Profiles?
RetroShare profile folders with PGP keys and node config on desktop, and what the export omits.
Last updated
RetroShare keeps the whole identity in one profile root: ~/.retroshare on Linux, %APPDATA%\RetroShare on Windows, with PGP keyrings under pgp/, node certificates under keys/, and per device config and cache under location folders. Copying that root migrates everything.
The in app export is narrower than it looks: the .asc file carries only the PGP identity, and you still create a fresh SSL node on the new device. The Mac equivalent path is the weak spot in documentation, so confirm under Application Support if ~/.retroshare is absent. No mobile app offers a user reachable path.
Where RetroShare stores this, by platform
~/.retroshare/
Full profile: pgp/ keyrings, keys/ certificates, per location config/ and cache/ folders. Copy the whole root to migrate; skip Downloads/Partials to save space.
%APPDATA%\RetroShare\
Same profile layout as Linux under Roaming (show hidden AppData first). Portable builds use a DATA/ folder next to the exe when a file named portable sits beside it.
~/.retroshare/
Unix default reported for Mac builds, but official docs are thin here: check ~/Library/Application Support/ if absent. Back up whatever profile dir you find before upgrading. Exact location may vary by build.
Frequently asked questions
How do I move RetroShare to a new computer?
Copy the entire profile root (location folders included) to the same path on the new machine. The Manage profiles export alone moves only the PGP identity and leaves chats, forums and caches behind.
What does the RetroShare .asc export contain?
Only your PGP identity in ASCII armor. After importing it you still create a new SSL node/location on the new device, then rejoin your circles from there.
Notice an outdated path? Let us know.