How to uninstall iMazing on Mac

iMazing is DigiDNA's iPhone and iPad manager, and the one thing on your Mac you are likely to want from it is your device backups. By default iMazing saves them inside its own data folder, ~/Library/Application Support/iMazing/Backups, one folder per device, and that whole folder goes when you remove iMazing's data, so move or export any backup you want to keep before you start. iMazing's own install and uninstall guide notes that removing the app does not delete backups and does not remove the pairing between your devices and this Mac; Find the location of your backups explains how to see where each device's backups are stored. Backups you pointed at an external drive or another folder stay where they are. This guide covers the official disk image from imazing.com and the Homebrew cask imazing.

Save your backups first

1. Open iMazing, select each device and check its backup location under the device's settings. If it is the default location above, use iMazing's export or move action to put the backups somewhere outside ~/Library/Application Support/iMazing.
2. Leave ~/Library/Application Support/MobileSync/Backup alone. That is where Finder and Apple Devices keep their own backups, and only an iMazing.Versions folder inside it, if you have one, belongs to iMazing's backup history.

Quit iMazing and iMazing Mini

1. Optionally, follow iMazing's own first step: choose iMazing › Preferences… and click Clear iMazing Cache.
2. Quit iMazing with Command + Q.
3. If you use iMazing Mini, the menu bar helper that runs scheduled backups, quit it from its menu bar icon. It starts from a launch agent in your user Library, com.DigiDNA.iMazing2Mac.Mini.plist, which keeps the iMazing 2 name even in iMazing 3.
4. Open Activity Monitor and search for iMazing. Nothing should be left. While it ran in the test, iMazing showed one main process plus iMazingSyncHelper and two Sparkle update helpers.

Remove the app

1. Move iMazing.app from Applications to the Trash, as described in Apple's Delete or uninstall apps on Mac.
2. Open each path below with Shift + Command + G in Finder and move the ones you no longer need to the Trash.

Where iMazing keeps its data

Device pairing records are kept by macOS for Finder as well, so leave them unless you no longer want this Mac to be trusted by the device; iMazing's guide links to its own steps for removing them.

Check the result

pgrep -il imazing
launchctl list | grep -i imazing
ls -d /Applications/iMazing.app ~/Library/Application\ Support/iMazing ~/Library/Caches/iMazing ~/Library/LaunchAgents/com.DigiDNA.iMazing2Mac.Mini.plist

• No output from pgrep means neither iMazing nor iMazing Mini is running. A printed line names a process that is still alive; quit it, or restart the Mac once.
• No output from launchctl means the iMazing Mini launch agent is not loaded. A line with com.DigiDNA.iMazing2Mac.Mini means it is still registered; it disappears after you remove the plist and log out or restart.
• For ls -d, "No such file or directory" means that path is gone. A printed path is still on disk.

If you installed it with Homebrew

brew uninstall --cask imazing

The cask quits iMazing and removes the iMazing Mini login item as part of this ordinary command, then removes the app. brew uninstall --cask --zap imazing also deletes everything in its zap list, including ~/Library/Application Support/iMazing with the default Backups folder and ~/Library/Application Support/MobileSync/Backup/iMazing.Versions, and it does not read Mole's checkboxes, so only run it after your backups are safe elsewhere. Mole adds --zap only when every zap path is inside ~/Library and matches rows you reviewed; iMazing's list names /Users/Shared folders and backup snapshots Mole never lists, so Mole leaves --zap off and removes the rows you selected itself.

What Mole lists

Mole selects the app, ~/Library/Caches/iMazing, the preferences file, the iMazing Mini launch agent, the two crash-report records and the app's temporary cache. It recognises the launch agent by the iMazing Mini program it starts, so the older iMazing2Mac label does not hide it. ~/Library/Application Support/iMazing is listed for review and starts checked, since it is the app's own folder; it holds your default backups, so uncheck that row, or move the backups out first, if you want them. Mole does not list ~/Library/Application Support/MobileSync/Backup or anything inside it, or backups you stored on another drive. Status shows iMazing as one row while it runs, and the update page reads iMazing's own Sparkle feed.

What this test covered

On October 31, 2026, iMazing 3.6.5 from the official disk image was opened and then uninstalled with a source-built Mole. No device backup had been made, and the Backups folder was empty. While it ran, Status showed one iMazing row with six processes, and its update channel was iMazing's Sparkle feed, already at the latest version. Mole asked iMazing to quit, then moved the app, about 715 MB, and seven listed rows to the Trash: the iMazing Mini launch agent, ~/Library/Caches/iMazing (224 MB), ~/Library/Application Support/iMazing (106 MB), the preferences file, two crash-report records and the temporary cache. Afterwards no process, launch agent or file with iMazing's name was left in ~/Library. The /Users/Shared folders and iMazing.Versions named in the cask did not exist on the test Mac, so the test does not show how Mole handles them. No device was paired during the test, no license was activated, and a Homebrew install was not tested.