How to uninstall Bambu Studio on Mac

Bambu Studio is Bambu Lab's slicer for 3D printers, from bambulab.com. Its settings live in one large folder, ~/Library/Application Support/BambuStudio, which was 213 MB in the test. A user on the Bambu Lab forum reset the app by deleting the files in that folder, so treat it as the app's own state and possibly your printer, filament and process presets. Projects you saved as .3mf files sit wherever you saved them and are not touched. Before you remove anything, save any open project and export the presets you want to keep from inside the app, or copy the BambuStudio folder. Removing the app does not sign you out of your Bambu account or delete its cloud data. This guide covers the disk image from Bambu Lab's GitHub release and the Homebrew cask bambu-studio.

Quit and remove the app

1. Save your projects, export the presets you want, and copy ~/Library/Application Support/BambuStudio if you want a full backup.
2. Quit Bambu Studio with Command + Q. In the test it ran as 16 processes (the app plus WebKit and Metal helper services) and registered no login item or launch agent.
3. Open Finder, go to Applications and drag BambuStudio.app to the Trash.

Where the data lives

Press Shift + Command + G in Finder to open each path. Skip any path that is not on your Mac.

Check the result

pgrep -il bambu
ls -d /Applications/BambuStudio.app ~/Library/Application\ Support/BambuStudio ~/Library/Preferences/com.bambulab.bambu-studio.plist ~/Library/WebKit/com.bambulab.bambu-studio

• No output from pgrep means Bambu Studio is not running. A printed line is a process still alive; quit it and run the command again.
• For ls -d, "No such file or directory" means that path is gone. A printed path is still on disk; a surviving Application Support/BambuStudio is expected if you kept your presets.

If you installed it with Homebrew

brew uninstall --cask bambu-studio

The cask has no uninstall stanza, so this removes the app only. brew uninstall --cask --zap bambu-studio also trashes ~/Library/Application Support/BambuStudio, which holds your presets, the cache, the preferences file, the binary cookies, Saved Application State and WebKit entries, and /Library/Logs/DiagnosticsReports/BambuStudio*. A direct brew command does not read Mole's checkboxes. The zap list reaches outside ~/Library through that absolute /Library path, so Mole leaves --zap off for this cask and removes the rows you selected itself. The Homebrew install was not tested.

What Mole lists

Mole selects the app, the preferences file, ~/Library/Caches/com.bambulab.bambu-studio, ~/Library/WebKit/com.bambulab.bambu-studio, the Cache folder inside BambuStudio and its two temporary cache rows. It lists ~/Library/Application Support/BambuStudio for review and selects it by default when eligible, so untick it if you keep your presets. Before removing, Mole asks Bambu Studio to quit.

What this test covered

On November 9, 2026, the test downloaded Bambu Studio 02.09.01.70 as a universal disk image from Bambu Lab's GitHub release, whose checksum matched the Homebrew cask, copied the app to Applications without running brew install, launched it once and quit it. A source-built Mole with the review rows ticked moved the app and 7 rows to the Trash, the 213 MB BambuStudio folder included; no row failed and the name rescan found nothing left. Status showed one Bambu Studio row with 16 processes. Mole found no update channel, and no update was run. No Bambu account was signed in, no printer was connected, nothing was sliced or exported, and the Homebrew install and Mole's notarized release build were not tested.