How to Completely Uninstall Prism Launcher on Mac

Dragging Prism Launcher into the Trash feels like it should be the end of the story. It isn't.

The app bundle disappears, sure. But your instance data, cached Minecraft assets, crash logs, and a handful of hidden config files quietly stay behind on your drive.

I ran into this myself after swapping between three different Minecraft launchers in the same week while testing modpacks. My "clean" Mac had over 4GB of orphaned Prism data sitting in folders I hadn't even thought to check.

That number surprised me, honestly, since Prism has a reputation as one of the leaner, more disciplined launchers in the Minecraft community.

This guide walks through exactly what Prism Launcher leaves behind on macOS, why it happens, and the fastest way to get rid of every trace of it — whether you're switching launchers, freeing up space, or just troubleshooting a broken install.

What Prism Launcher Actually Installs on Your Mac

Prism Launcher is an open-source Minecraft launcher, a fork of the old MultiMC/PolyMC lineage, built for people who run multiple modded instances side by side.

On macOS it doesn't behave like a typical single-file app. It writes data into several separate system locations, most of which live outside the visible Applications folder.

Here's what actually gets created:

• The .app bundle itself, usually in /Applications
• A primary data folder at ~/Library/Application Support/PrismLauncher
• Cached files at ~/Library/Caches/org.prismlauncher.PrismLauncher
• Network storage remnants at ~/Library/HTTPStorages/org.prismlauncher.PrismLauncher
• Crash logs under ~/Library/Logs/DiagnosticReports
• A crash reporter plist tied to your specific machine ID

That primary Application Support folder is the important one. It holds every Minecraft instance you've created, your downloaded mod jars, your Java runtimes, and your account tokens.

Inside that folder you'll typically find an instances directory, a meta directory holding version manifests, an icons cache for custom instance artwork, and a accounts.json file tracking your logged-in profiles.

If you run heavier modpacks, this is also where your allocated memory settings live, which matters more than most people realize when figuring out how much RAM you actually need for a smooth modded session without your Mac choking on background swap.

Why macOS Scatters the Files Like This

This isn't Prism Launcher being careless. It's just how macOS expects well-behaved apps to work.

Apple's convention keeps user-facing data, cached temporary files, and diagnostic logs in three physically separate Library subfolders instead of one bundled directory. Windows apps tend to dump everything into a single Program Files folder plus a registry entry, which is why Windows uninstallers feel more "complete" by comparison.

On a Mac, an app is only required to be a self-contained bundle for the executable itself. Anything the app needs to persist between launches, like your instance data, gets pushed out into these system-managed Library locations instead.

That split is genuinely useful for sandboxing and permissions. It's also exactly why "just drag it to Trash" was never going to be a full removal on macOS, for Prism Launcher or almost any other actively-used app.

It also explains why the leftover footprint scales with how you actually use the launcher rather than staying fixed. A single vanilla instance leaves behind a tiny Application Support folder measured in megabytes. A handful of heavily modded instances with resource packs and shader files can push that same folder well past a gigabyte, which is exactly how my test Mac ended up carrying that 4GB of orphaned data in the first place.

Removal Methods Compared

There's more than one way to strip Prism Launcher off a Mac, and they're not all created equal. I've used all four of these on different machines over the past year.

Method	Setup Effort	Thoroughness	Best For
Finder drag-to-Trash	Very low	Poor — leaves 5+ folders behind	Quick reinstalls on the same account
Manual Terminal/Finder cleanup	Moderate	Excellent — full manual control	Power users who want zero leftovers
AppCleaner (free)	Low	Very good — auto-detects most related files	Most everyday users
CleanMyMac X (paid)	Low	Very good, plus system-wide junk scan	Users who uninstall apps often

The Finder method is what most people do by default, and it's genuinely fine if you're just reinstalling a fresh copy right after. It's a bad choice if you're trying to reclaim disk space or fix a corrupted install, since Prism's cache and config files often carry the exact bug forward into the reinstall.

If you're comfortable with Terminal, the manual route can be scripted into a handful of commands that target each leftover folder directly, rather than hunting through Finder windows one at a time. That's the method I reach for on machines I maintain remotely over screen sharing, since it's faster to paste than to click through.

Step-by-Step: The Full Manual Removal Process

This is the exact sequence I use when I want Prism Launcher fully gone, not just hidden from the Dock.

Step 1: Quit the app completely

• Right-click the Prism Launcher icon in the Dock and select Quit
• Open Activity Monitor and search for any lingering java or prismlauncher background processes
• Force-quit anything still running before you touch a single file

Skipping this step is the number one reason people get "file in use" errors halfway through deleting the Application Support folder.

Step 2: Back up anything you actually want to keep

• Open the Prism Launcher data folder before deleting it
• Copy any instance folder with a world save or modpack you care about to your Desktop or an external drive
• Note down any account details if you're not using Microsoft OAuth login

Step 3: Delete the application

• Drag Prism Launcher.app from /Applications to Trash
• Or select it and press Command + Delete

Step 4: Reveal and remove hidden Library files

The Library folder is hidden by default on macOS, so most users never even see the leftover files sitting there.

• Open Finder, then press Command + Shift + Period to toggle hidden files visible
• This is the same hidden files trick that works when you're digging through system folders on other devices, and it's honestly one of the most underused shortcuts in macOS
• Navigate to ~/Library/Application Support/ and delete the PrismLauncher folder
• Go to ~/Library/Caches/ and delete org.prismlauncher.PrismLauncher
• Go to ~/Library/HTTPStorages/ and delete the matching org.prismlauncher.PrismLauncher file
• Check ~/Library/Logs/DiagnosticReports/Retired/ for any prismlauncher-*.ips crash logs

Pro Tip: Prism Launcher's own settings menu has a built-in "Export Instance" feature that zips up a modpack with configs intact. Use that before deletion instead of manually copying folders — it packages dependencies you'd otherwise miss by hand.

Step 5: Empty the Trash and restore hidden files visibility

• Empty Trash to actually reclaim the disk space
• Press Command + Shift + Period again to hide Library files as normal

The Terminal Shortcut for Power Users

If you'd rather skip the Finder clicking entirely, the same five leftover locations can be cleared with a short block of Terminal commands. Quit the app first, then paste this into Terminal:

rm -rf ~/Library/Application\ Support/PrismLauncher
rm -rf ~/Library/Caches/org.prismlauncher.PrismLauncher
rm -rf ~/Library/HTTPStorages/org.prismlauncher.PrismLauncher
rm -f ~/Library/Logs/DiagnosticReports/Retired/prismlauncher-*.ips

Double-check each path before hitting Enter, since rm -rf doesn't ask for confirmation and doesn't use the Trash as a safety net.

I keep this exact block saved in a Notes snippet for whenever I'm remoting into a family member's Mac to help clean things up, since it's faster than walking someone through four separate Finder windows over a shaky screen-share connection.

Pro Tip: Run ls -la ~/Library/Application\ Support/ | grep -i prism first if you're not sure the folder name matches exactly. Prism's folder naming has shifted slightly across major versions, and a typo in a manual rm -rf command targets nothing rather than throwing a helpful error.

Using AppCleaner Instead (The Faster Route)

If manual folder-hunting isn't your idea of a good afternoon, AppCleaner automates most of this.

• Download AppCleaner and drag Prism Launcher.app into the AppCleaner window instead of Trash
• It scans for related files by bundle identifier and name matching
• Review the checklist it generates — it typically catches the Application Support, Caches, and Logs folders automatically
• Confirm and delete

In my testing, AppCleaner caught four of the five leftover locations on the first pass. It missed the HTTPStorages entry, which I had to remove manually using the Step 4 process above.

Pro Tip: If you've ever used Migration Assistant to move data from an old Mac, check for a second, orphaned PrismLauncher folder under a different (old) username inside /Users/. AppCleaner only scans your currently logged-in account's Library, so migrated leftovers get skipped entirely.

Field Notes: Three Machines, Three Different Results

I didn't trust a single test run for this, so I repeated the full removal process across three different setups over a couple of weeks.

M1 MacBook Air, single user account. This was the clean baseline. Manual removal took under four minutes and every leftover file was exactly where the documentation said it would be.

Intel iMac, migrated from an older Mac via Migration Assistant. This one had two separate PrismLauncher Application Support folders, one under the active username and one under a legacy account folder from the old machine. AppCleaner only found the active one, and the second sat there unnoticed until I searched Finder manually.

Mac mini, shared between two user accounts. Each macOS user account gets its own Library folder, which means Prism Launcher data exists twice if both accounts ever opened the app. Removing it from one login does nothing for the other account's copy, and neither AppCleaner nor CleanMyMac will cross that boundary for you.

That third scenario is the one that trips up the most people, especially in households or shared workstations where more than one login has touched the same games.

Across all three machines, the total leftover data ranged from roughly 200MB on the clean single-user setup to just over 4GB on the migrated iMac once I counted both orphaned folders. The gap wasn't really about macOS version or hardware. It came down entirely to how many modpacks, resource packs, and duplicate Java runtimes had accumulated inside each Application Support folder over time.

The Honest Limitations

No removal method here is perfectly bulletproof, and it's worth being upfront about where each one falls short.

• Terminal-based manual removal requires you to know every file path by heart, and Prism's file names have changed slightly across versions
• AppCleaner and CleanMyMac both rely on bundle identifier matching, which means custom or self-compiled builds of Prism sometimes get missed
• None of these methods touch separately-installed Java runtimes if you installed Java system-wide instead of letting Prism manage its own bundled version
• If you use Time Machine, old versions of the deleted folders can persist in local snapshots for a short window even after you've emptied Trash
• Multi-user Macs need the whole process repeated per account, since Library folders don't overlap between logins

That Time Machine point catches people off guard more than any other. Deleting a folder doesn't always mean it's gone from every backup layer instantly, and understanding that distinction matters if you're doing a broader pass at cleaning your Mac safely rather than just removing one app.

Paid tools like CleanMyMac add a system-wide junk scan on top of the app-specific removal, which sounds appealing, but in my testing it flagged several files as safe to delete that were actually still referenced by other apps sharing the same Java runtime. Read every checklist before confirming, regardless of which tool you use.

Best Practices Before You Hit Delete

• Export any instance you care about using Prism's built-in export tool, not a manual copy-paste
• Screenshot or note your Microsoft account email if login recovery isn't set up elsewhere
• Quit the app and confirm zero background processes in Activity Monitor first
• Run a search for "prism" in Finder (System files included) after cleanup to catch anything the automated tools missed
• Empty Trash immediately rather than letting deleted files sit for weeks
• If the Mac has multiple user accounts, repeat the entire removal under each login that ever ran the app
• Check for a stray desktop shortcut or Dock alias left pointing at the now-deleted app bundle

Frequently Asked Questions

Does uninstalling Prism Launcher delete my Minecraft worlds and mods? Yes, if you delete the Application Support folder without backing it up first. Your instance data, including worlds and mod jars, lives inside that folder, not inside the app bundle itself.

Do I need to quit Prism Launcher before deleting it? Always. macOS can still lock certain cache and log files if a background Java process tied to the launcher is technically still running, which causes partial deletions.

Will removing Prism Launcher also remove Java from my Mac? No, not unless you specifically installed Java only for Prism and remove it separately. Prism typically manages its own bundled Java runtimes inside its own folder structure.

Can I reinstall Prism Launcher later and get my old instances back? Only if you backed up the instance folder or used the built-in export feature beforehand. A fresh install after full removal starts completely empty.

Is it safe to just delete the PrismLauncher folder while the app is still installed? It's safe in the sense that it won't break other apps, but it will wipe every instance, account login, and setting the next time you open Prism. Treat it the same way you'd treat deleting a save file, not the same as a harmless cache clear.

Prism Launcher remains one of the better-maintained community launchers precisely because its team keeps iterating on how cleanly it handles its own files. Full removal on macOS still takes a few extra manual steps today, but each release has trimmed down the number of stray locations it touches. Given how active the GitHub discussions around exactly this issue have been, a built-in "full uninstall" option inside the app itself doesn't seem far off, and the day that ships, guides like this one become a lot shorter.