How to Completely Uninstall Firefox on Mac
· uninstall firefox mac, firefox leftovers, mac cleanup, firefox profile backup, remove firefox completely
Most advice on how to completely uninstall Firefox on Mac stops at “drag the app to the Trash.” That's not a clean uninstall, it's just the first move. Firefox leaves behind Application Support, Caches, Preferences, and Saved Application State files in the user Library, so the browser can look gone while its profile and settings footprint is still sitting on disk, ready to reappear on the next reinstall or sync sign-in.
Table of Contents
- Why Dragging Firefox to the Trash Leaves a Trail
- Backing Up Your Bookmarks and Profile Before You Start
- Removing the App Bundle and Clearing the Obvious Leftovers
- Hunting Hidden Firefox Files with Terminal
- Using Crufti for an Audited Local-First Cleanup
- Troubleshooting Common Firefox Removal Problems
- Verifying a Truly Clean Uninstall and What to Do Next
Why Dragging Firefox to the Trash Leaves a Trail
Dragging Firefox.app out of /Applications feels like a clean break, but macOS doesn't store all app data inside the app bundle. It spreads application support, caches, preferences, and saved state across separate Library locations, which is why a visual delete of the app package doesn't equal a full removal of the browser's profile and settings footprint. Independent uninstall guides consistently call out at least four leftovers that survive the Trash move, ~/Library/Application Support/Firefox, ~/Library/Caches/Firefox, ~/Library/Preferences/org.mozilla.firefox.plist, and ~/Library/Saved Application State/org.mozilla.firefox.savedState. ThinkMobiles' Firefox uninstall guide shows the same pattern.
The hidden parts live outside the app bundle
That split matters because the app bundle is only the visible shell. The browser state lives elsewhere, including cached data, saved tabs, and preference files that macOS treats as separate from the binary itself. If you only delete the app, you've removed the launcher, not the whole footprint. For a deeper look at why deleted Mac apps keep leaving traces behind, see this explanation of leftover app data on macOS.
Firefox leaves behind more than users expect
Firefox is especially easy to misjudge because the app can vanish cleanly from the Applications folder while the profile data stays put under ~/Library. That's why people reinstall and find old bookmarks, old logins, or old session data coming back. The browser looks uninstalled, but the account state and local settings still have a place to live.
Practical rule: if you can still find Firefox folders in Application Support, Caches, Preferences, or Saved Application State, the uninstall is incomplete.
The result is simple. A real uninstall is a multi-location cleanup, not a single delete action. If you want Firefox gone for troubleshooting, privacy, testing, or a fresh reinstall, you need to clear the app bundle and then audit the Library trail it leaves behind.
Backing Up Your Bookmarks and Profile Before You Start
Start with a backup, even if you think you only want to “wipe and forget.” Firefox data is useful exactly when you need it least, after a failed migration, a broken extension setup, or a sync problem that shows up later. The safest move is to preserve the pieces you may want to bring back, then remove the rest with confidence.
Save the artifacts you may want later
Export your bookmarks from Firefox's library manager so you have a file you can import into any browser. Then copy the entire default profile folder to an external drive or a cloud folder, because that folder holds the profile state that users usually want to restore when they decide the uninstall was too aggressive. If you're doing this for a reinstall, note the bundle identifier org.mozilla.firefox, because that string is the anchor you'll keep seeing in preference and saved-state files.
- Bookmarks export: keep the exported file somewhere outside the Mac you're cleaning.
- Profile folder copy: duplicate the whole profile directory, not individual files.
- Bundle identifier note: write down org.mozilla.firefox so later searches stay focused.
Sign out of Sync before you remove anything
Firefox Sync can put old data back if you leave it active. Sign out first so the browser stops treating your machine as a live sync endpoint, then confirm you're no longer signed in before removing local files. If you skip this step, a reinstall can look “mysteriously” dirty because the browser pulls old state back in when you launch it again.
Good cleanup habit: backup first, sign out second, delete third. Anything else makes it harder to tell whether a later problem came from your uninstall or from the account data you left behind.
A clean backup also makes the rest of the process less stressful. You can be more aggressive about deleting profile leftovers when you know the important pieces are already copied somewhere safe.
Removing the App Bundle and Clearing the Obvious Leftovers
Quit Firefox completely before you touch the files. Don't trust the window closing as proof, check the menu bar and Activity Monitor if you need to, because a running browser can keep files locked and make deletion fail or leave partial cleanup behind. Once it's closed, delete Firefox.app from /Applications.
Go after the standard Library paths
Open Finder, use Go to Folder, and check the four core locations one by one. These are the places that typically survive a normal Trash deletion: ~/Library/Application Support/Firefox, ~/Library/Caches/Firefox, ~/Library/Preferences/org.mozilla.firefox.plist, and ~/Library/Saved Application State/org.mozilla.firefox.savedState. This guide to deleting app data on Mac is useful if you want a wider view of how these paths fit together.
- Application Support: review the contents before deleting, because profile-like data, extensions, and site-specific leftovers often live here.
- Caches: these files are usually safe to remove if you're fully uninstalling.
- Preferences: this is the browser's configuration trail, including the plist named for Mozilla Firefox.
- Saved Application State: remove it if you want Firefox to stop restoring previous window state later.
Review before you empty the Trash
Application Support deserves the most attention. If you kept custom certificate authorities, special site settings, or anything extension-related that you may want to inspect later, copy it out before deletion. That folder is where the cleanup can go from “routine” to “oops” if you move too fast. The other three paths are usually more straightforward, but I still recommend opening them first so you know exactly what you're removing.
After the files are in the Trash, empty it only when you're sure nothing valuable is still inside. If you're cleaning a shared Mac or an enterprise machine, a careful review matters more than speed because the goal is not just removal, it's removal without collateral damage.
<iframe width="100%" style="aspect-ratio: 16 / 9;" src="https://www.youtube.com/embed/IgRi0Z1O_gk" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>Hunting Hidden Firefox Files with Terminal
Finder covers the obvious paths, but Firefox can still leave traces outside those four Library locations. Terminal is the fastest way to confirm whether anything else matches org.mozilla or a Firefox-related helper name across the user and system Library trees. The point isn't to delete everything that looks Mozilla-adjacent, it's to identify what's still there.
Search, then read the results carefully
Use mdfind to look for Firefox-related filenames, then inspect each match before deleting anything. A broad metadata search can catch leftover configuration files, saved state folders, and other stragglers that don't stand out in Finder. After that, ls and grep help you verify whether a path is a real leftover or just a naming coincidence.
Keep your searches focused on ~/Library and /Library. Leave system areas alone if you don't recognize the result, and don't chase anything that belongs to macOS itself. The point is to find org.mozilla.* files, helper tools, or launch items, not to “clean” the operating system by guesswork.
Check the places that cause the most confusion
Some Firefox-related artifacts can survive in places users don't think to inspect. Keychain items may still hold saved passwords, LaunchAgents can keep updater or helper behavior alive, and sandbox-related containers can preserve app state even after the main app is gone. Activity Monitor is worth a quick look too, because a lingering helper process can make the uninstall seem incomplete.
- Look for running helpers: if Firefox or a related process is still active, stop it before deleting more files.
- Inspect LaunchAgents: any com.mozilla.* item in /Library/LaunchAgents deserves a close look.
- Leave system bundles alone: don't remove Apple frameworks or unrelated shared components just because they show up in a search.
Terminal is most useful when you already know the app's identity and want proof that the machine is clean. If you're guessing, stop and verify the path first, because deleting the wrong support file is the fastest way to create a new problem while fixing the old one.
Using Crufti for an Audited Local-First Cleanup
Manual cleanup works, but it's easy to miss one container, one saved-state file, or one hidden support directory when you're moving quickly. A local scanner that audits leftovers before deletion gives you a cleaner workflow, especially if you uninstall apps often or you want a review trail instead of a blind sweep. That's the practical value of a tool like Crufti, a native macOS utility designed to surface app leftovers locally on your Mac.
Why audited cleanup beats guesswork
Crufti scans eleven ~/Library locations and surfaces related files with size details and a three-tier match confidence model, exact, strong, and partial. That matters because leftover app data rarely lives in one neat folder. It's usually scattered, and the review step helps you separate clear Firefox leftovers from files that only look related.
The safety model is what makes the workflow usable. Selected files move to Trash, not permanent deletion, so you can undo a bad choice. Apple system bundles and generic patterns are blocked, user content is flagged, and a JSON audit trail records what happened. That combination is useful when you need to show what was removed or want a way to check your own work.
Local-only matters more than people think
Crufti's privacy-first design is built around zero telemetry, zero analytics, and no network connections. Everything happens locally, which is the right model for a cleanup tool that can see personal preferences, account-related leftovers, and browser artifacts. Pre-flight permission checks also keep it from touching anything before you approve the scan and the cleanup.
The best cleanup tool is the one that shows you what it found before it removes it, then keeps the removal reversible.
That auditability is especially valuable for Firefox, because the browser's footprints can span profile data, cached state, and containers. A scanner that exposes those pieces in one reviewable list is a lot safer than manually hopping between Finder windows and hoping nothing relevant was missed.
Troubleshooting Common Firefox Removal Problems
Firefox can still show up after you think it's gone, and most of the time the clue is in a leftover file, not in the app itself. I've seen people delete the app bundle, reinstall, and then wonder why old tabs, old logins, or old updater behavior come back. The machine wasn't haunted, it still had state.
Match the symptom to the leftover path
If Firefox keeps appearing in Spotlight, you may be looking at stale metadata rather than a live app. If a reinstall says Firefox is already running, a lock file or helper process may still be sitting in the profile area. If sync data comes back on launch, the problem is usually an account token or other leftover state tied to the browser profile.
- Firefox in Spotlight: rebuild the metadata index, then verify the app bundle and Library leftovers are gone.
- Profile folder remains: remove
~/Library/Application Support/Firefoxmanually if it survived the first pass. - Login items persist: check System Settings > General > Login Items for anything Firefox-related.
Don't ignore helper tools and launch items
Some users also find updater tools or Developer Edition helpers still active after the browser itself has been removed. Those usually live in /Library/LaunchAgents, which is why a clean uninstall sometimes needs a second look outside the user Library. The fix is to identify the specific helper, confirm it belongs to Firefox, and remove only that item rather than sweeping the whole LaunchAgents folder.
Diagnosis first, deletion second: the fastest fix is the one tied to the exact leftover path.
That approach saves time and reduces damage. If the file or helper keeps coming back, the root cause is almost always one of the same few locations already covered earlier, which is why tracing the symptom back to the path matters more than repeating the uninstall from scratch.
Verifying a Truly Clean Uninstall and What to Do Next
A clean check doesn't take long. Search for org.mozilla across ~/Library and /Library, glance at Activity Monitor for any Firefox-related helper, inspect the Keychain if you still suspect saved login state, and confirm that Firefox.app is no longer in /Applications. If those checks come back empty, the uninstall is complete.
The useful rule is simple. A complete Firefox uninstall is a four-location minimum, not a single Trash action. If you want the quickest one-off removal, manual cleanup is fine. If you handle multiple Macs, reinstall often, or want an auditable record of what was removed, a local scanner is the stronger choice.
Back up first, delete second, verify last.
That order prevents the two common mistakes, losing data you meant to keep, and thinking the job is done when hidden state is still present. Once the browser bundle and the leftover Library paths are gone, you can move on to a fresh install or switch browsers without dragging old profile baggage with you.
If you want a cleaner way to remove Firefox leftovers without guessing through hidden Library paths, Crufti gives you a local-first scan, an auditable review, and a reversible Trash-based cleanup. It's built for the exact kind of Mac maintenance this guide covers, and it's a strong fit when you want the uninstall to be complete without making the process risky.