Where Does JS8Call Store Config and Logs?
JS8Call keeps INI config per OS with ADIF logs beside it, plus rig-name variants for multi-radio setups. Versions break compat.
Last updated
JS8Call stores config per OS in INI files with logs beside them. Rig names fork the layout per radio for multi-rig shacks. Version compatibility breaks across jumps, so match builds when migrating.
Contact logs follow ADIF spec from the log directory with mode toggles in settings. Viewer tools parse explicit paths on every platform. Improved forks share the layout with audio backend caveats.
Where JS8Call stores this, by platform
~/.config/JS8Call.ini
Per-OS INI config with log directory beside it. Rig-name flags fork per-radio trees. Version compat breaks across jumps, so match builds.
%LOCALAPPDATA%\JS8Call
Windows twin under LocalAppData with same rig-name forking. Viewer tools accept explicit paths on every platform. Audio backends vary by fork.
~/Library/Preferences/JS8Call.ini
Mac INI under Preferences with identical rig-name behavior. Log directories open from the File menu. Same ADIF contact format throughout.
Frequently asked questions
How do I back up JS8Call?
Copy the per-OS INI file with log directory contents while the app is closed. Rig-name variants branch per radio with viewer tools reading any path. Version jumps break backward compat, so match builds on restore.
How do I run two JS8Call radios?
Launch with the rig-name flag per radio for separate config and log trees. Shortcuts encode the flag per instance on Windows. Logs follow ADIF spec with mode options in settings.
Where are JS8Call contact logs?
Open the log directory from the File menu for contact logs in ADIF format with per-contact entries. Mode logging toggles between submode detail and generic data. Settings viewers parse any INI path given explicitly.
Notice an outdated path? Let us know.