How to uninstall Prism Launcher on Mac
Back up Minecraft instances, world saves and mods before removing Prism Launcher. The official data-location guide explains the launcher root, while instance-copy documentation distinguishes saves, mods and other instance content. This page covers the official Mac archive app.
Quit and remove the app
Finish and close running Minecraft instances while keeping Prism Launcher open. Use Folders › Launcher Root to locate and copy wanted data, including custom instance locations. Verify the copies, then quit Prism Launcher and move Prism Launcher.app to the Trash.
Data to keep or review
~/Library/Application Support/PrismLauncheris the documented default Mac root. Itsinstancesfolder holds instances; the root also has game assets, managed Java installations, libraries, themes and logs. Back up wanted instances and their saves before removing the parent.- Custom data or instance locations must be checked separately.
- The current cask zap targets
metacache,PrismLauncher-*.logandprismlauncher.cfginside the root, plus exact preferences, saved state and WebKit data. It does not zap the entire root or its instances folder.
For manual cleanup after the backup, use Finder’s Shift + Command + G to open ~/Library/Application Support/PrismLauncher. Check the metacache folder, log files beginning with PrismLauncher- and prismlauncher.cfg individually. Other cask paths are ~/Library/Preferences/org.prismlauncher.PrismLauncher.plist, ~/Library/Saved Application State/org.prismlauncher.PrismLauncher.savedState and ~/Library/WebKit/org.prismlauncher.PrismLauncher. Move only unwanted app-owned items to the Trash, keeping backed-up instances separate.
Check the result
pgrep -ifl prismlauncher
command -v prismlauncher
ls -ld "/Applications/Prism Launcher.app" "$HOME/Library/Application Support/PrismLauncher"
No process output means this name was not found, not that every helper has gone. Check any match against the app’s actual executable path. A missing-path error from ls means only that location is absent; permission errors leave its state unknown. A surviving folder can be intentional data to keep.
command -v reports the command found by this shell, not a running process. No path means it is absent from this shell’s PATH; a surviving command may belong to another installation.
If you installed it with Homebrew
The cask has no separate uninstall helper. Ordinary uninstall removes its managed prismlauncher command. Zap resets the named configuration/cache paths rather than deleting the whole instance store; keep wanted launcher settings before running it.
To uninstall without zap, use:
brew uninstall --cask prismlauncher
Mole checks Homebrew's full removal list and skips --zap when it reaches unchecked data, shared files or anything it cannot verify. It still removes the leftovers you selected. A direct brew uninstall --cask --zap prismlauncher runs Homebrew’s full zap list without consulting Mole’s checkboxes.
Removing the launcher does not delete your Microsoft account or cancel Minecraft access. Local backups must be made separately; signing in again is not a backup of your worlds.
What Mole lists
Mole selects the app, exact preferences and attributable log, crash-report and temporary-cache rows by default. With “Remove data and settings with apps” off, the PrismLauncher support parent stays unticked. Turning it on can select that parent when it passes the app-data checks, so back up wanted instances and uncheck it before confirming if they should remain.
These are the defaults with “Remove data and settings with apps” turned off. Enabling that preference can also select eligible reviewed app data; shared stores, protected profiles and agent archives keep their individual review or remain locked. Check the final list before confirming.
What this test covered
On September 25, 2026, Prism Launcher 11.1.0 was copied from the official Mac archive and tested with a development build of Mole without signing in. The app and selected first-run support, preference and cache rows were removed. Populated Minecraft instances, world recovery and account sign-in were not verified.