How to uninstall DevToys on Mac
DevToys offers local developer utilities. Before clearing preferences, note any customized settings or snippets you rely on and copy files you created with its tools to a folder you control. The cask zap names only app-specific caches, preferences and WebKit state, not your projects.
The recorded test used the official Mac package; the Homebrew route below is separate.
Remove the app
Quit DevToys, then move DevToys.app from Applications to Trash. If a WebKit or preview process still belongs to the app, let it exit before inspecting residual files. Do not delete a broad WebKit parent directory: other apps use it too.
Review local data
The path below is documented in the current Homebrew cask. In Finder, use Go › Go to Folder to inspect it. Do not remove its parent directory or another product’s data.
| Location | Decision |
|---|---|
~/Library/Caches/com.devtoys |
App-specific cache in the cask zap list and recorded test. It can be cleared after checking the app is closed. |
The tested package uses bundle ID com.devtoys. Review only files that actually appear on this Mac. A missing path needs no cleanup.
Check what remains
Run these read-only commands after quitting the app:
pgrep -il 'DevToys'
ls -d "$HOME/Library/Caches/com.devtoys"
No process output means there is no matching process running now; it does not prove every helper is gone. A listed process needs its owner checked. If ls prints the path, that item remains and needs review. “No such file or directory” means this path is absent; a permission error means its state was not established.
If you installed it with Homebrew
The current devtoys cask has a zap list covering the com.devtoys caches, preferences and WebKit data. A direct brew command with --zap applies the cask list without consulting Mole’s checkboxes. After backing up, use this command without --zap:
brew uninstall --cask devtoys
Mole checks each zap path against your selections, other installed apps, and protected locations. An unchecked, shared, or unverifiable path suppresses --zap; selected remnants can still use Mole’s own removal flow. This cask was not the recorded installation channel.
What Mole lists
Mole selects exact com.devtoys cache, preference and WebKit rows by default when present. A failed Trash move remains an incomplete item; it is not evidence the data was removed. Mole does not claim every WebKit temporary file under a shared parent directory.
What this test covered
The official DevToys.app 2.0.9 was removed on September 21, 2026. Its app-specific caches, WebKit data and preferences were selected. Three temporary WebKit leaves returned Trash error 513. Their exact paths are in Mole’s failed-item result; inspect those paths individually before treating this as complete, and leave the shared WebKit parent alone.