Where Does CHIRP Store Logs and Images?
CHIRP writes debug.log to AppData CHIRP on Windows and home .chirp elsewhere. Radio images are .img files you save yourself.
Last updated
CHIRP keeps almost no persistent state of its own. Settings reset each launch, and the debug log clears too, which is why bug reports demand a fresh reproduction. Radio memory lives in .img image files you explicitly save after downloading.
The log paths are documented per OS in the issue guide. Windows uses a Roaming AppData folder, Linux and macOS use a dot folder in home. A config dir flag overrides the location when running portable or test setups. Stock and CSV imports land wherever you save them, outside CHIRP state.
Where CHIRP stores this, by platform
C:\Users\<username>\AppData\Roaming\CHIRP\debug.log
Debug log on Windows. Type the percent wrapped path into Run to open it. Attach it to every bug report.
/home/<username>/.chirp/debug.log
Debug log on Linux and Mac. Copy it out before relaunching, since startup wipes it.
C:\Users\<username>\Documents\my-radio.img
Your radio backup, saved by hand after each download. Keep one pristine copy per radio before editing memories.
Frequently asked questions
Where is the CHIRP debug.log?
On Windows open percent AppData percent CHIRP. On Linux and Mac copy home chirp debug.log to the Desktop. Always reproduce the bug first, since the log clears on launch.
How should I back up my radio?
Download from the radio, then File, Save As to an img file before editing. Keep that pristine copy so a bad upload can be reversed.
Notice an outdated path? Let us know.