How to uninstall Snapzy on Mac

Snapzy is a free, open-source menu bar app for screenshots, screen recording, annotation and editing, from snapzy.app and its GitHub project. Its bundle ID is com.trongduong.snapzy. It is not sandboxed. Per its history doc, the capture history is a database in ~/Library/Application Support/Snapzy with thumbnails and temporary captures beside it, and screenshots and recordings you saved go to your export folder, which Snapzy only records by path. The README says the same folder can hold temporary captures and recordings, so look inside before you remove it. This guide covers the disk image from the project's GitHub release and the Homebrew cask snapzy.

Back up, quit and remove the app

  1. Save anything you only have as a temporary capture. Open Snapzy's History (the README lists Shift + Command + H) and save or drag out what you want, or copy files out of ~/Library/Application Support/Snapzy. Files in your export folder are yours and stay.
  2. If you want to keep your settings, use Settings › Advanced › Backup to export config.toml, or copy ~/.config/snapzy/config.toml (docs).
  3. If you used Cloud Upload, files you uploaded to your own S3, R2 or Google Drive bucket stay there. Delete them at the provider if you want them gone.
  4. If you installed the snapzy command, open Settings › Command Line and choose Uninstall. It removes only a link to this app's helper from /usr/local/bin/snapzy (docs).
  5. Quit Snapzy from its menu bar icon, then open Finder, go to Applications and drag Snapzy to the Trash.

The project also offers an uninstall.sh that you run through curl. This guide does not use it. It deletes the Application Support folder only after asking, and it resets screen recording, microphone and accessibility permissions for Snapzy.

The app registered no login item or launch agent in the test.

Where the data lives

Press Shift + Command + G in Finder to open each path. Skip any path that is not on your Mac.

Location What it holds What to do
~/Library/Application Support/Snapzy Capture history database, thumbnails and temporary captures; 127 KB in the test Copy captures you want first, then remove. Mole lists it for review and selects it by default.
~/.config/snapzy config.toml, your exported settings; 8 KB in the test Keep it if it lives in a dotfiles repository, otherwise remove. Mole lists it for review but does not select it; tick it to remove it.
~/Library/Preferences/com.trongduong.snapzy.plist Preferences Remove. Selected by default.
~/Library/Logs/Snapzy Logs Remove. Selected by default.
The folder getconf DARWIN_USER_CACHE_DIR prints, plus com.trongduong.snapzy Mole's temporary cache row; empty in the test Remove. Selected by default.
Your export folder Screenshots and recordings you saved Keep. Mole does not touch it.
Login Keychain Cloud credentials, OAuth tokens and OCR API keys, per the README Delete the entries in Keychain Access if you want them gone.

Check the result

pgrep -il snapzy
ls -l /usr/local/bin/snapzy
ls -d "$HOME/Library/Application Support/Snapzy" "$HOME/.config/snapzy" "$HOME/Library/Preferences/com.trongduong.snapzy.plist" "$HOME/Library/Logs/Snapzy"
  • No output from pgrep means Snapzy is not running. A printed line is a process still alive; quit it.
  • No such file or directory from the first ls means no command link is left. A printed link whose target is gone is a dead link to Snapzy.app; remove it with rm /usr/local/bin/snapzy after checking that it points into a Snapzy.app bundle.
  • A path printed by the second ls still exists. No such file or directory means it is gone. A surviving Application Support folder is expected if you kept captures there.

Screen Recording, Microphone and Accessibility entries for Snapzy stay in System Settings › Privacy & Security until you remove them with the minus button.

If you installed it with Homebrew

brew uninstall --cask snapzy

The cask only removes the app; it has no quit step and creates no command link, so use Settings › Command Line first if you installed the snapzy command. Its zap list deletes ~/.config/snapzy, ~/Library/Application Support/Snapzy, ~/Library/HTTPStorages/com.trongduong.snapzy, ~/Library/Logs/Snapzy and the preferences file. Running brew uninstall --cask --zap snapzy therefore deletes your history database and temporary captures and does not read Mole's checkboxes. ~/.config/snapzy is outside ~/Library, so Mole never runs this cask's zap and removes the rows you selected itself.

Account and subscription

Snapzy has no account. Cloud uploads go straight from the app to the provider you configured, so removing the app does not delete uploaded files or revoke the keys; do that at the provider.

What Mole lists

Mole selects the app, the preferences file, ~/Library/Logs/Snapzy and the temporary cache row. It lists ~/Library/Application Support/Snapzy and ~/.config/snapzy for review. The Application Support folder is selected by default, so untick it to keep your history and temporary captures; ~/.config/snapzy is outside ~/Library and stays unticked unless you tick it. Before removing, Mole asks Snapzy to quit and removes the preferences file a second time after the app has settled. Mole does not touch your export folder or Keychain.

What this test covered

On November 9, 2026, the test downloaded the Snapzy 2.1.0 disk image (Universal) from the project's GitHub release, whose checksum matched the Homebrew cask, copied the app to Applications without running brew install, launched it once, quit it and removed it with a source-built Mole with every review row ticked. Mole moved the app and 5 rows to the Trash, and nothing it attributed to Snapzy was left on disk afterwards. Status showed one Snapzy row with 1 process, and Mole detected a Sparkle feed for the app; no update was run. Captures, History, Cloud Upload, the snapzy command, the project's uninstall.sh, the Homebrew uninstall and Mole's notarized release build were not tested.