How to uninstall macshot on Mac

macshot is a free, open-source screenshot and screen recording app for the Mac, from its GitHub project. Its bundle ID is com.sw33tlie.macshot.macshot. It is sandboxed, and its screenshot history, which the README says keeps editable annotations, lives inside its container. In the test that container held a history folder under Library/Application Support/com.sw33tlie.macshot. So the container is your capture history: save what you want from it before you remove it, and note that the Homebrew cask's zap deletes the same container. Screenshots and recordings you saved to a folder of your own are not in it. This guide covers the disk image from the project's GitHub release and the Homebrew cask macshot.

Save your captures, quit and remove the app

1. Open the history panel (the README lists Shift + Command + H) and save or drag out the captures you want to keep. A capture you sent to Google Drive, imgbb or an S3-compatible bucket stays there; delete it at the provider if you want it gone.
2. Quit macshot from its menu bar icon.
3. Open Finder, go to Applications and drag macshot to the Trash.

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.

Check the result

pgrep -il macshot
ls -d "$HOME/Library/Containers/com.sw33tlie.macshot.macshot" "$HOME/Library/Application Scripts/com.sw33tlie.macshot.macshot"
ls -d "$(getconf DARWIN_USER_CACHE_DIR)com.sw33tlie.macshot.macshot"

• No output from pgrep means macshot is not running. A printed line is a process still alive; quit it.
• A path printed by ls still exists. No such file or directory means that path is gone. The container is the one most likely to survive, see the test record below.

If the container survives, quit the app first. In Finder press Shift + Command + G, open ~/Library/Containers, and drag the folder to the Trash. macOS can refuse to move sandboxed data; if it does, give Mole Full Disk Access in System Settings › Privacy & Security › Full Disk Access and let it move the row, or remove the folder yourself later. The Screen Recording entry for macshot stays in System Settings › Privacy & Security until you remove it with the minus button.

If you installed it with Homebrew

brew uninstall --cask macshot

The cask quits the app and removes it. Its zap list has only two paths, ~/Library/Application Scripts/com.sw33tlie.macshot.macshot and the container, so brew uninstall --cask --zap macshot deletes your screenshot history and does not read Mole's checkboxes. Both paths are inside ~/Library, but Mole adds --zap only when its whole removal scope passes its zap gate; an unchecked row, a path the scan never listed or a path another installed app claims keeps it off, and Mole then removes the rows you selected itself. Untick the container first if you want to keep your history.

Account and subscription

macshot has no account, no subscription and takes no donations (README). Google Drive sign-in and S3 settings are yours at the provider; removing the app does not revoke them. They were not tested.

What Mole lists

Mole selects the app, the Application Scripts folder, the container and the temporary cache row. The container is selected by default, so untick it to keep your history. Before removing, Mole asks the app to quit. A container needs Full Disk Access to move; without it Mole's report names Full Disk Access and offers a retry.

What this test covered

On November 9, 2026, the test downloaded the macshot 4.4.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, the Application Scripts folder and the temporary cache row to the Trash. The container stayed because the test build ran without Full Disk Access; macOS refused the move, and its history folder was still there afterwards. Status showed one macshot row with 2 processes, and Mole detected a Sparkle feed for the app; no update was run. Captures, uploads, the Homebrew uninstall and Mole's notarized release build were not tested.