Uninstall Flameshot on Mac
Check where Flameshot saved screenshots before uninstalling. Its capture files are user documents, while ~/.config/flameshot holds the app configuration. The September 19, 2026 record covers the app copied from the official package.
Quit and remove the app
Quit Flameshot from the menu bar, then move Flameshot.app to Trash. Review its screen-recording permission and keyboard shortcut in System Settings separately; removing the app does not require resetting all screen-capture permissions. The official page has more product information.
Review the app’s data
The cask lists ~/.config/flameshot, ~/.cache/flameshot and ~/Library/Caches/flameshot. The official docs locate flameshot.ini in the config directory; keep it if you plan to reuse your shortcut or capture settings.
If you installed it with Homebrew
The Homebrew cask has its own --zap list. brew uninstall --cask flameshot removes the cask without that list; brew uninstall --cask --zap flameshot also acts on its listed data without consulting Mole’s checkboxes. Zap includes configuration as well as cache; retain flameshot.ini if wanted. Mole also suppresses zap if its list would cross an unchecked, shared, unknown, or unsupported path; selected remnants still follow Mole’s own deletion path.
brew uninstall --cask flameshot
Check the result
These commands inspect the running process and one relevant location. They do not remove anything:
pgrep -il "Flameshot"
ls -ld "$HOME/.config/flameshot"
No pgrep match means no process with that name is running; a match needs identification before quitting anything. A listed path still exists, while an ls “No such file” error means only that exact path is absent. A permission error is inconclusive.
What Mole lists
Mole can select the display-name ~/Library/Caches/flameshot row when ownership is clear. It does not have a rule for ~/.config/flameshot, so check that configuration separately; screenshot output and macOS permission databases are outside the app-remnant list.
What this test covered
The September 19, 2026 official-package test saw Flameshot running in the menu bar before uninstall. It did not test a custom screenshot destination or confirm removal of a saved flameshot.ini.
