Where Does Radicle Store Keys and Data?
Radicle keeps identity, config, and all cloned projects under ~/.radicle (keys, config.json, storage, node), movable with RAD_HOME.
Last updated
Radicle concentrates everything in one home directory, and losing it means losing your identity. The keys folder holds your secret key, config.json holds your handle and peer settings, storage holds every project repo as bare git, and node holds the daemon's socket and logs. Seeding nodes replicate the storage folder, so a second machine with your key restores the working set without manual copying.
One variable relocates the lot. Set RAD_HOME and Radicle nests the same layout there instead. The profile commands (rad self, rad config) always report resolved paths, so ask the tool before assuming.
Where Radicle stores this, by platform
~/.radicle
config.json for handle and peers, keys/ for identity, storage/ for project repos, node/ for socket and logs. RAD_HOME overrides the location. Back up keys with the node stopped.
~/.radicle
Same layout as Linux. The node log sits at node/node.log inside the home. rad self --home prints the effective path when overrides are in play.
Frequently asked questions
How do I print my actual Radicle home?
Run rad self --home (or rad self --config for the file). It prints the resolved path including any RAD_HOME override, which settles it faster than guessing.
How do I back up a Radicle identity?
Copy the whole ~/.radicle tree with Radicle stopped. Keys, config, and every project repo move together. Guard the keys folder: whoever holds it holds your identity.
Notice an outdated path? Let us know.