Where Does Radare2 Store Configs and History?
Where Radare2 keeps configs and history on Linux, plus r2pm database roles. Full paths are listed below.
Last updated
Radare2 is terminal reversing with local state. Your configs, scripts, and history live in its config directory. Projects save where directed per analysis.
Same home folder means same setup. Exact file names shift with stable versus git builds. Keep scripts in version control rather than cloning whole folders. For moves, copy the config directory plus project folders. Partial copies miss r2pm packages that commands depend on. Check the in app storage readout when sizes look wrong on different releases.
Where Radare2 stores this, by platform
~/.config/radare2 (configs plus history, projects per path)
Configs and history live here with r2pm packages beside them. Copy the whole directory for moves. Match releases before importing old scripts.
Frequently asked questions
How do I move Radare2 configs to a new machine?
Copy the radare2 config directory to the new machine over USB, since history and scripts live there. Projects save as R2 project folders where directed. Match the release first, since command syntax shifts between versions and breaks old scripts.
Does Radare2 back up command history?
Yes, in the config directory per profile with command history attached. The install holds a working copy plus r2pm packages. Views rebuild after import. Export rc scripts from settings for records, since the folder alone is working state.
Notice an outdated path? Let us know.