How to uninstall Gifox on Mac
Save your recordings before removing Gifox. Its documentation provides Output Folder in the library popover to reveal exported files, while the editor can re-export media. Copy wanted exports outside every sync root and removal folder, then open them before deleting any local data. This guide covers the direct-download app and Homebrew cask gifox, not the App Store or Setapp edition.
Save media and quit
Stop any recording and wait for exports to finish. Open Output Folder and copy the GIFs or other exports you want to keep; exporting a GIF is not a backup of editable original media. If transferring a direct-download license, use the documented Activate/Deactivate entry before quitting.
Open Gifox's main menu from its library popover, or Option-click its menu-bar icon, then choose Quit Gifox. With Gifox quit, copy the existing support folders below if you want to retain local state, and verify the copies. In Finder, move Gifox.app from Applications to the Trash, and check System Settings › General › Login Items & Extensions for an unwanted Gifox entry.
Review local files
Use Finder's Go › Go to Folder to inspect these exact locations. The support folders were recorded locally; the other entries below are in the current cask.
| Location | What to keep or remove |
|---|---|
~/Library/Application Support/Gifox |
Recorded Gifox support data. Copy wanted contents before removal. |
~/Library/Application Support/Gifox 2 |
Gifox 2 local support data. Back up the whole folder if you want to retain local state. |
~/Library/Caches/com.gifox.gifox2 |
Per-app cache, removable after quitting. |
~/Library/Cookies/com.gifox.gifox2.binarycookies |
App cookies, removable for a reset. |
~/Library/Preferences/com.gifox.gifox2.plist |
Preferences; back up if wanted. |
Keep your export destination and shared cloud folders. Missing paths need no action.
If you installed it with Homebrew
Ordinary uninstall also asks Gifox to quit and unloads com.gifox.gifox2.agent; those actions are separate from zap.
brew uninstall --cask gifox
Zap additionally removes Application Support/Gifox 2, the cache, cookies and preferences above. Running brew uninstall --cask --zap gifox yourself ignores Mole's checkboxes. Mole uses zap only when every target passes its selection, ownership and safety checks, otherwise it removes selected remnants through its own Trash flow.
Check the result
pgrep -ifl Gifox
ls -ld "$HOME/Library/Application Support/Gifox" "$HOME/Library/Application Support/Gifox 2"
No pgrep output means the pattern matched no running process; inspect and quit an attributed match before deleting data. A printed folder still exists, as expected if retained. A missing-path error means that exact folder is absent; permission or command errors leave the result unknown.
What Mole lists
The two support folders start unchecked with Remove data and settings with apps off. Turning it on can preselect eligible unshared app data, so uncheck wanted local state. Exact Gifox 2 cache, cookie and preference rows are selected by default. Exported media outside these locations is not part of those rows.
What this test covered
On September 21, 2026, the official-download Gifox 2.10.0 app was copied into Applications, opened and removed without selecting review rows. Both support folders remained unchecked. Recording, populated-library recovery, license activation and the Homebrew removal route were not tested.