How to uninstall DB Browser for SQLite on Mac

DB Browser for SQLite does not build a database inside itself: it just opens .sqlite files you point it at, so removing the app never touches those files wherever you keep them. What it leaves behind is small: preferences filed under its current identifier, plus a second preferences file under the older identifier com.sqlitebrowser.sqlitebrowser. This guide covers the official universal disk image and the Homebrew cask db-browser-for-sqlite.

Quit the app and remove it

  1. Close any open database files and quit DB Browser for SQLite from its application menu.
  2. Check Activity Monitor for a lingering sqlitebrowser process.
  3. In Finder's Applications folder, move DB Browser for SQLite to the Trash. No vendor-published uninstall or data-location page was found for this app; the locations below come from the local test recorded for this guide and the Homebrew cask's own zap list.

Where its settings live

The app's current identifier is net.sourceforge.sqlitebrowser. No Application Support folder turned up in the recorded test; the list below combines what the test found with the Homebrew cask's zap list.

Location What it holds What to do
~/Library/Preferences/net.sourceforge.sqlitebrowser.plist Preferences under the current identifier, if present Selected by default
~/Library/Preferences/com.sqlitebrowser.sqlitebrowser.plist Preferences under the older identifier; 101 bytes in the test Listed but not selected
~/Library/Saved Application State/net.sourceforge.sqlitebrowser.savedState Window state, if present Selected by default

The .sqlite files you opened in DB Browser stay where you keep them; Mole does not list them.

If you installed it with Homebrew

Mole checks the cask's zap list first: when it reaches a row you left unticked, Mole drops --zap and still cleans up the rows you selected through its own recoverable Trash step.

The db-browser-for-sqlite cask's zap list is the two preference files and the saved-state file above, nothing more. Because the older-identifier com.sqlitebrowser.sqlitebrowser file is unticked by default whenever it exists, Mole normally runs brew uninstall --cask db-browser-for-sqlite without --zap.

Running the zap step yourself removes both preference files and the saved state whatever you ticked in Mole:

brew uninstall --cask --zap db-browser-for-sqlite

To remove only the app:

brew uninstall --cask db-browser-for-sqlite

Check the result

pgrep -il sqlitebrowser
ls -l ~/Library/Preferences/net.sourceforge.sqlitebrowser.plist
ls -l ~/Library/Preferences/com.sqlitebrowser.sqlitebrowser.plist
  • No output from pgrep means no DB Browser for SQLite process is running.
  • ls -l printing a file means that preferences file is still there. "No such file or directory" means it is gone, or was never written on this Mac.

What Mole lists

For DB Browser for SQLite installed from the official disk image:

  • The current preferences file and the saved window state, both filed under net.sourceforge.sqlitebrowser, are selected by default.
  • The older-identifier com.sqlitebrowser.sqlitebrowser.plist file is listed but not selected.
  • The .sqlite files you opened are not listed.

What this test covered

On September 20, 2026, DB Browser for SQLite 3.13.1 was copied from the official universal disk image into Applications and removed with a Preview build of Mole 1.15 (build 282); there was no Homebrew receipt. Mole listed only the app's temporary system cache under its current identifier. The 101-byte com.sqlitebrowser.sqlitebrowser.plist was not listed and stayed on disk after the app was removed; the review row above was added to Mole after this test. No database was opened or connected during the test, and the Homebrew cask was not tested.