Where Does SatDump Store Config and Output?
SatDump keeps settings in satdump_cfg.json beside the binary, with recordings and decoded products in output folders you choose.
Last updated
SatDump splits config from products. A satdump_cfg.json file beside the program holds devices, pipelines, and UI settings. Recordings and decoded images go to output folders you select per run.
Portable installs keep everything in one tree, which makes the folder the backup unit. Package installs behave the same way with the config beside the binary. On Android the app package holds the same split behind its own storage. Always confirm the output path in the UI before a long pass.
Where SatDump stores this, by platform
<SatDumpFolder>\satdump_cfg.json
Devices, pipelines, and UI state in one JSON beside the program. Edit with SatDump closed. Keep a copy before upgrading, since new releases sometimes migrate the format.
<SatDumpInstall>/satdump_cfg.json
Same layout on Linux: config symlinked beside the build or install tree, outputs wherever each run points. Confirm the exact config spot on your install, since prefix builds and source checkouts differ.
/storage/emulated/0/Android/data/org.satdump.SatDump
Same config plus output split inside app storage. Confirm paths in the app on your build. SDR support varies by device on Android, so verify the receiver works before a scheduled pass.
Frequently asked questions
How do I move SatDump settings to a new PC?
Copy satdump_cfg.json plus your output folders to the new machine, then install fresh and drop them in. Settings travel in the JSON, data travels in the outputs. Recheck SDR driver setup separately.
Where did my SatDump recording go?
Wherever you pointed the pipeline or recorder at run time. SatDump never picks a hidden default, so the output path shown in the UI is authoritative. Check the last used folder first.
Notice an outdated path? Let us know.