Repository navigation
Settings
The Settings tab in Konserve lets you customize backup and restore behavior.
Settings that are still planned but not yet functional are marked (WIP).
See the Roadmap for implementation status.
Turn on detailed debug output for troubleshooting.
When enabled, a konserve.log file is written next to your config directory.
An Open Log button appears to open the log location directly.
Crash and error logs are always written to
konserve-crash.lognext to the exe, regardless of this setting.
Automatically check for new Konserve versions when the app starts.
Not yet implemented.
Show an estimated total size of your selection before backup starts.
Not yet implemented.
Choose how Konserve handles existing files when restoring a backup.
When disabled, existing files are always overwritten (default behavior).
When enabled, select one of the following modes:
| Mode | Behavior |
|---|---|
| Prompt | Ask for each conflicting file during restore |
| Overwrite | Always overwrite existing files |
| Skip | Leave existing files unchanged, skip the restore for that file |
| Rename | Restore the file with a new name (e.g. file_1.txt) to avoid overwriting |
Set a folder to use as the default destination for new backups.
When set, Konserve pre-selects this directory in the backup dialog.
When enabled, backups are always saved to the folder containing the Konserve executable, skipping the directory picker entirely.
Controls how the backup filename is generated:
-
Timestamp — generates a name like
backup_2025-06-10_12-00-00.tar(default) - Fixed name — use a custom name you set; you'll be prompted before overwriting an existing file
- Settings persist between sessions and are stored in your user config directory.
- See the Roadmap for details on planned vs. implemented features.
Maintained by @konnatoad
Feedback welcome via issues
Konserve GitHub Repo · Latest Release