Uninstall Adobe Acrobat Reader on Mac

Save PDF annotations, forms, and signatures, close documents, and quit Acrobat Reader. Your PDFs are ordinary files and stay where you saved them. These steps cover Adobe Acrobat Reader installed with Adobe's installer and with the adobe-acrobat-reader Homebrew cask. Reader and Acrobat have different removal instructions: Acrobat uses Acrobat Uninstaller inside its application directory, so do not apply that procedure to Reader by assumption. Acrobat removal instructions

Remove Reader

Quit Acrobat Reader, move Adobe Acrobat Reader from Finder’s Applications folder to the Trash, and restart the Mac, as Adobe's Reader instructions describe. Official Reader removal steps

Where Reader keeps its files

Adobe's update service

Reader’s installer also installs the ARMDC update service used by Acrobat and Reader. The recorded removal left an Acrobat Update Helper and processes named com.adobe.ARMDC.Communicator and com.adobe.ARMDC.SMJobBlessHelper; keep shared update components while Acrobat remains. These process or launch labels are not complete disk paths, so do not use them as instructions to delete files from system folders. Use the official Reader removal steps above and check remaining Adobe components separately.

Check the result

pgrep -il 'acrobat|adobe'
ls /Applications | grep -i acrobat
ls /Library/LaunchAgents /Library/LaunchDaemons /Library/PrivilegedHelperTools | grep -i adobe

No output from pgrep means no Reader or Adobe updater process is running; Acrobat Update Helper or ARMDC there is the update service, not Reader. The second command lists any Acrobat app still installed, which tells you whether the update service still has a job. The last command lists Adobe-named files, including components of other Adobe apps; names alone do not prove ownership or authorize removal. Likewise, the Applications listing does not find every nested or custom installation. Return to the official product-specific removal steps rather than deleting shared system files from these search results.

If you installed it with Homebrew

Mole skips --zap when its list reaches unchecked or shared data, or cannot be fully checked, and still cleans the leftovers you selected.

Running brew uninstall --cask --zap adobe-acrobat-reader yourself applies the data list independently of Mole’s checkboxes. Even without zap, ordinary uninstall unloads ARMDC services and removes files recorded by the Reader/ARMDC installer packages before forgetting their receipts. Omitting zap only avoids the additional shared ~/Library/Application Support/Adobe/Acrobat and ~/Library/Application Support/Adobe/AcroCef deletion; it does not protect the shared update service. If you still need Acrobat, use Adobe’s Reader removal procedure above and keep its shared updater, rather than treating plain brew uninstall as a shared-service-safe alternative.

If the PDF remains but annotations are missing

Open the original PDF and verify that annotations and filled fields were actually saved into the file. Seeing them in an unsaved Reader window is not the same as saving the document. Review signature appearance, certificates, and sign-in state separately; removing caches is not a way to preserve signing material.

What Mole lists

Unselected review rows below assume Remove data and settings with apps is off, the default. Enabling it can preselect eligible Reader-owned review data; folders still used by another installed Adobe app retain their sharing protection. Untick anything you want to keep.

Mole does not list the shared ~/Library/Application Support/Adobe parent, and it does not list the ARMDC update service as a Reader leftover, the same way it treats Google's shared updater.

What this test covered

Acrobat Reader was installed from the Homebrew cask on September 17, 2026 and uninstalled through Mole. The app went, but in a later check the Acrobat Update Helper launch agent was still installed, two ARMDC privileged helpers were still running, and Homebrew still recorded the cask. Acrobat Pro, signed-in Adobe accounts, and digital signatures were not tested.