How to uninstall Beekeeper Studio on Mac

Beekeeper Studio keeps your saved connections and SQL queries in one SQLite file, app.db, inside its data folder on this Mac. Your databases themselves live on their servers or in your own database files and are not affected by removing the app, but the connection list and the saved queries are. Export what you need before you delete that folder. This guide covers the disk image from beekeeperstudio.io and the Homebrew cask beekeeper-studio.

Save connections and queries first

Beekeeper Studio's data location page says connections and queries are stored in app.db, and that Help › Add Beekeeper's Database opens that file as a connection so you can browse it and export your SQL queries. Do that before removing anything, or quit the app and copy the whole data folder described below.

Your personal settings file, user.config.ini, sits in the same folder according to the configuration guide. Copy it too if you changed shortcuts or other options.

Quit Beekeeper Studio and remove the app

Quit Beekeeper Studio from its app menu.
Search Activity Monitor for Beekeeper Studio and check that the app and its Helper processes have exited.
Move Beekeeper Studio from Finder's Applications folder to the Trash.

The recorded tests found no login item, background item or launch agent from Beekeeper Studio.

Removing the app does not cancel a paid Beekeeper Studio license or subscription; manage that on the web.

Where Beekeeper Studio keeps its data

Beekeeper's data location page names ~/Library/Application Support/Beekeeper Studio, while its configuration guide and the Homebrew cask use ~/Library/Application Support/beekeeper-studio. On the test Mac only the lowercase folder appeared. Check both with Shift + Command + G in Finder.

Location	What it holds	What to do
`~/Library/Application Support/beekeeper-studio`	`app.db` with saved connections and queries, `user.config.ini`, and Chromium caches	Export or copy first; remove only when you no longer need your connections
`~/Library/Application Support/Beekeeper Studio`	The folder name the data location page gives, if your version uses it	Same as above
`~/Library/Logs/beekeeper-studio`	Log files, as the troubleshooting page describes	Safe to remove
`~/Library/Preferences/io.beekeeperstudio.desktop.plist`	App preferences	Remove for a clean start
`~/Library/Caches/io.beekeeperstudio.desktop` and `~/Library/Caches/io.beekeeperstudio.desktop.ShipIt`	Cache and the updater's download area, listed in the cask's zap stanza	Safe to remove

Check the result

Run these read-only commands after the app is in the Trash:

pgrep -ilf "Beekeeper Studio"
ls "$HOME/Library/Application Support/beekeeper-studio"

No output from pgrep means Beekeeper Studio is no longer running. A listed process means the app or a helper is still open; quit it before copying app.db.
ls listing app.db means your connections are still on this Mac, which is what you want if you kept them. "No such file or directory" means the folder is gone. If you are looking for your data, try the Beekeeper Studio spelling as well before concluding it is lost.

If you installed it with Homebrew

The beekeeper-studio cask's zap list includes ~/Library/Application Support/beekeeper-studio, which holds app.db, plus ~/Library/Application Support/Caches/beekeeper-studio-updater, the io.beekeeperstudio.desktop caches and ShipIt caches, the ShipIt ByHost preferences, the preferences file and saved window state. Running brew uninstall --cask --zap beekeeper-studio yourself moves all of them to the Trash, your saved connections included, whatever you selected in Mole. To keep them, remove only the app:

brew uninstall --cask beekeeper-studio

Mole adds --zap only when every path on the zap list sits inside ~/Library, none of them touches a row you left unchecked, and no other installed app claims them. ~/Library/Application Support/beekeeper-studio is listed but unselected by default, so Mole leaves --zap out unless you tick that row yourself.

What Mole lists

For Beekeeper Studio from beekeeperstudio.io:

~/Library/Application Support/beekeeper-studio is listed but not selected, so app.db stays unless you tick it. The Chromium cache folders inside it, such as Cache, Code Cache and GPUCache, are separate rows selected by default.
~/Library/Logs/beekeeper-studio, the io.beekeeperstudio.desktop preferences file, the recent-documents list and the temporary caches filed under the bundle ID are selected by default.
The databases you connected to, and any SQLite files you opened, are not listed.

What this test covered

On September 20, 2026, Beekeeper Studio was copied from the official disk image into Applications, opened without connecting to a database, and uninstalled with a Preview build of Mole 1.15; there was no Homebrew receipt. ~/Library/Application Support/beekeeper-studio, about 27 MB, stayed unselected, and the small log folder was also left in that run. On September 26, 2026, it was installed again from the same official download, opened once, and removed with a development build of Mole with every row ticked. Mole's Status view showed it as one row of 7 processes, about 743 MB. All 13 items went to the Trash and nothing from the list, no process and no startup item was left. Saved connections, a paid license and the Homebrew cask were not tested.