Where Is the Satty Config File?
Satty reads config.toml from the user config dir (system fallback in /etc/xdg), with --config and flags beating both.
Last updated
Satty layers three config sources: built-in defaults, the system file under /etc/xdg, then your ~/.config/satty/config.toml. CLI flags sit on top of all of them, so one-off tweaks never touch stored files.
The file holds fullscreen behavior, annotation sizes, fonts, palette and keybinds. Feed it via grim plus slurp (satty --filename - reads stdin) and the output-filename pattern controls where finished shots land.
Where Satty stores this, by platform
~/.config/satty/config.toml
Fullscreen, fonts, palette, actions, output-filename patterns. System fallback at /etc/xdg/satty/config.toml. Flags always beat the file.
Frequently asked questions
How do I test a Satty config without touching the live one?
Pass -c/--config <file>. That file becomes exclusive: system and user configs are ignored entirely, and a missing file is fatal instead of falling back.
Where do annotated screenshots actually save?
Set output-filename in config.toml (strftime patterns allowed, ~ expands home) or pass -o per run. Omit it to disable file saving and go clipboard-only.
Notice an outdated path? Let us know.