How to uninstall PicGo on Mac

Before removing PicGo, save and copy your image-host settings, plugins and upload-history records to a separate backup, then open the copy. This guide covers the official Mac download; Homebrew-specific removal is separate below.

Back up image-host configuration securely without sharing access keys. Removing PicGo does not remove uploaded images from the host, and its separately installed PicGo-Core CLI is a different component.

Quit and remove the app

Finish current work and quit PicGo. Check Activity Monitor for its process before removing the app in Finder. In Applications, move PicGo.app to the Trash; if you keep it elsewhere, use its actual location. Keep the Trash until your backup has been checked. Official documentation

Check the result

This read-only check searches full process command lines, not disk contents.

pgrep -ifl 'PicGo'

No output with exit status 1 means no matching command line was found. A printed entry needs inspection in Activity Monitor because names can match unrelated processes. An error is not proof of removal. Also check that the app is absent from its original Finder location; a retained data folder or independent component does not mean the app is still installed.

If you installed it with Homebrew

Use the installed cask receipt and uninstall without zap.

brew uninstall --cask picgo

The command removes the cask’s managed application artifacts without running zap. The live cask additionally names these zap targets, which can erase settings, local data or integration files; this is Homebrew’s list, not a vendor data-location claim.

  • ~/Library/Application Support/com.apple.sharedfilelist/com.apple.LSSharedFileList.ApplicationRecentDocuments/com.molunerfinn.picgo.sfl*
  • ~/Library/Application Support/picgo
  • ~/Library/Preferences/com.molunerfinn.picgo.plist
  • ~/Library/Services/Upload pictures with PicGo.workflow

A direct brew uninstall --cask --zap picgo runs its own zap scope without consulting Mole’s checkboxes. Mole uses zap only when the complete scope passes its gate; unchecked or shared paths, paths outside the review boundary, unknown stanzas and unsupported directives suppress it. Selected remnants still use Mole’s deletion path.

What Mole lists

~/Library/Application Support/picgo holds desktop settings and local state; it is listed for review and not selected by default. Back up wanted configuration securely before selecting it. Its separate Cache, Code Cache and GPUCache rows and ~/Library/Preferences/com.molunerfinn.picgo.plist are selected by default unless protected. The PicGo upload workflow is an app integration, not your uploaded images.

These defaults assume “Remove data and settings with apps” is off. Opting in also selects eligible reviewed app data; shared stores and protected data retain individual review or stay locked.

What this test covered

The October 3, 2026 record covers the following test. The official app was first-launched without signing in or extra permissions, then removed using a source-built Mole app. Reviewed paths were absent afterward; the first-launch scan was partial. Uploads, remote-image deletion and credentials were not tested.