How to uninstall DBeaver on Mac

DBeaver’s default local workspace data lives in ~/Library/DBeaverData: saved connections, encrypted credentials, SQL scripts, projects, downloaded drivers and settings. Removing the app does not remove it, and deleting it removes all of that at once. Export what you want to keep before you touch the folder. Your databases themselves are not on this Mac unless you run them here, and uninstalling DBeaver does nothing to them. These steps cover the official download from dbeaver.io and the Homebrew cask dbeaver-community, which install the same DBeaver Community app.

Export connections and scripts first

In DBeaver, choose File › Export, then DBeaver › Projects, to write your projects, including their connections and scripts, to an archive you can import later with File › Import (DBeaver projects documentation). Open the archive location afterward to confirm the file exists. Saved passwords are the easiest thing to lose: after you import on another Mac or a fresh install, open one connection and check that it still logs in before you delete anything.

If you only need the raw files, DBeaver keeps each project's connection list in data-sources.json and its encrypted credentials in credentials-config.json, inside ~/Library/DBeaverData/workspace6/General/.dbeaver for the default project (connection configuration files). Quit DBeaver and confirm its processes have stopped, then copy the whole .dbeaver folder rather than single files and inspect the independent copy.

DBeaver can also keep a generated master password in the macOS Keychain when integrated security is turned on under Window › Preferences › General › Security (integrated security). Removing DBeaver does not touch that Keychain item, and Mole never reads or removes Keychain items.

Quit DBeaver and remove the app

Quit DBeaver from its app menu. It runs as a Java process, so check Activity Monitor for dbeaver if the app seems to linger. Move DBeaver from Applications to the Trash. In the recorded test a DBeaver entry stayed in System Settings › General › Login Items & Extensions after removal, pointing at the deleted app; it starts nothing, and you can turn it off there.

Where DBeaver keeps its data

~/Library/DBeaverData is not only DBeaver Community's: DBeaver Lite uses the same folder, and its Homebrew cask lists it too. If another DBeaver edition is still on this Mac, leave the folder alone.

Check the result

Run these read-only commands in Terminal:

pgrep -il dbeaver
ls -d ~/Library/DBeaverData
ls ~/Library/DBeaverData/workspace6/General/.dbeaver

• No output from pgrep means DBeaver has quit.
• The ls -d line proves only that this data directory exists; inspect actual content or a usable backup. "No such file or directory" concerns this path alone, and a permission or read error leaves the check unresolved.
• The last line lists the connection files of the default project. Seeing data-sources.json proves only that the file exists, not that connections or credentials work; use the import-and-login check above before deleting originals. "No such file or directory" means either the whole folder is gone or you never used the default project.

If you installed it with Homebrew

The dbeaver-community cask stops DBeaver on uninstall and removes the dbeaver command it links. Its zap list includes ~/Library/DBeaverData (every connection, credential and script), plus the cache, HTTP storage, preferences and saved window state. brew uninstall --cask --zap dbeaver-community moves all of them to the Trash whatever you selected in Mole, even if DBeaver Lite still uses the folder. To keep your data, remove only the app:

brew uninstall --cask dbeaver-community

Mole adds --zap only when everything in the zap list sits in your own ~/Library, none of it touches a row you left unchecked, and none of it is claimed by another installed app. ~/Library/DBeaverData is unselected while Remove data and settings with apps is off, the default. Enabling it can preselect eligible app-owned data. Leaving this row unchecked, or keeping another installed DBeaver edition that uses it, prevents zap; Mole then removes the app without --zap and moves only the selected rows.

What Mole lists

When you remove it with Mole:

• ~/Library/DBeaverData is listed with selection governed by the option above. Untick it to retain your connections and scripts; another installed DBeaver edition keeps its shared data protected.
• The cache, HTTP storage, preferences plist and saved window state named after org.jkiss.dbeaver.core.product are selected by default, as are DBeaver's crash reports.
• Keychain items are outside the uninstall scope, and Mole does not connect to database servers to delete data.

What this test covered

DBeaver Community was installed from the official download and uninstalled on September 19, 2026, with a Mole Preview build, with the review list shown. Its crash reports were selected by default and removed. ~/Library/DBeaverData was not on Mole's list at the time and stayed on disk; the review-only row above was added to Mole in the same test batch. A Login Items entry pointing at the removed app remained. No connections or scripts are recorded, so exporting, credentials and the Keychain item were not tested, and the Homebrew cask was not part of it.

On September 26, 2026, DBeaver Community 26.2.1 from the official DMG was opened and removed again with a development build of Mole. The app, the selected 57 KB ~/Library/DBeaverData review row, preferences and a temporary-cache row went to the Trash. The follow-up found none of the originally attributed paths remaining; this did not test populated connections, export recovery or Homebrew uninstall.