How to uninstall Logseq on Mac

Back up your Logseq graphs before removal. Removing only the app leaves them in place; selecting graph-data rows in Mole or running Homebrew zap can remove them. Where they live depends on the kind of graph. A file graph is the Markdown folder you picked when you created it, with journals, pages and logseq inside. A DB graph, the database format of Logseq 2.0, lives in ~/logseq/graphs/<graph name> as a db.sqlite file plus an assets folder, as Logseq's DB version notes describe. Back up both kinds before you remove anything, and never delete a graph folder to tidy up after an uninstall. This guide covers Logseq from its disk image and the Homebrew cask logseq.

Back up your graphs first

  • For a file graph, quit Logseq and copy the whole graph folder somewhere else, then open a few pages in the copy.
  • For a DB graph, open the three-dot menu at the top right, choose Export graph, and pick Export both SQLite DB and assets. Logseq's DB version guide also says the desktop app keeps the last 12 automatic backups in a backups folder inside each graph directory; they sit inside ~/logseq/graphs, so they are not a copy that survives deleting it.
  • Plugins and app settings are in ~/.logseq. A Logseq documentation post says to copy that folder without its graphs subfolder if you want your plugins back later.

Quit Logseq and remove the app

  1. Quit Logseq from the Logseq menu.
  2. Search Activity Monitor for Logseq and check that its processes have exited. In the recorded test Logseq ran seven processes, which Mole's Status page folded into one row.
  3. Move Logseq from Finder's Applications folder to the Trash.

Removing the app does not cancel Logseq Sync or delete a Logseq account. Graphs you synced stay in that service.

Where Logseq keeps its data

Location What it holds What to do
The folder you chose for a file graph Your Markdown pages and journals Keep it; it is your notes, not app data
~/logseq DB graphs in graphs, each with its database, assets and backups Keep it; never delete it as a leftover
~/.logseq Plugins and settings; older versions also keep a graph cache in graphs Keep it for a reinstall; remove it only when you want a fresh setup
~/Library/Application Support/Logseq The app's local storage and Electron caches Remove after quitting once you no longer need local state
~/.local/bin/logseq A command-line launcher Logseq can install, marked logseq-cli-managed, pointing into Logseq.app Remove it with the app if you do not use the logseq command; leave the rest of ~/.local/bin alone

Check the result

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

pgrep -il logseq
ls ~/logseq/graphs
ls -d ~/.logseq "$HOME/Library/Application Support/Logseq"
grep -H Logseq.app ~/.local/bin/logseq
  • No output from pgrep means Logseq is not running.
  • ls ~/logseq/graphs lists directory entries, not proof that each database and its assets are intact. Check the actual graph files and independent backups. "No such file or directory" means this path is absent; it cannot distinguish a graph that was never created, moved or deleted. Permission or other read errors leave it unresolved.
  • ls -d prints each folder that still exists. A surviving ~/.logseq is expected if you kept your plugins.
  • grep printing a line that names Logseq.app means the launcher is still there and points at an app that is gone. No output means the file exists but is not Logseq's launcher, so leave it. "No such file or directory" means it was never installed or is already removed.

If you installed it with Homebrew

The current logseq cask includes ~/logseq and ~/.logseq in its zap list, as well as ~/Library/Application Support/Logseq, ~/Library/Logs/Logseq, and the com.electron.logseq preferences file and saved window state. Running brew uninstall --cask --zap logseq moves all of these to the Trash, including DB graphs, their assets and automatic backups, and plugins and settings. A file graph stored inside one of these targets goes with it too. Back up and check your graphs and plugins before any zap; to keep them, uninstall without zap:

brew uninstall --cask logseq

Because ~/logseq and ~/.logseq are outside ~/Library, Mole uninstalls this cask without --zap, even if you select their rows. Mole handles selected leftovers separately. A brew command you type yourself never consults Mole's checkboxes.

What Mole lists

For Logseq from its disk image:

  • ~/logseq and ~/.logseq are listed but unselected with the default app-data setting off. Turning on Remove data and settings with apps can preselect eligible rows when no other installed app shares them. Review graph and plugin backups before removing these rows; leave them unticked to keep that data.
  • ~/Library/Application Support/Logseq is listed but unselected with that setting off; eligible app data can be preselected when it is on. The Chromium cache folders inside it, such as Cache, Code Cache and GPUCache, are separate rows selected by default.
  • ~/.local/bin/logseq is listed but not selected when it is the managed launcher pointing at this Logseq.app. Nothing else in ~/.local/bin is matched by name.
  • ~/Library/Logs/Logseq, the recent-documents list, and the caches, preferences and saved window state filed under com.logseq.logseq are selected by default.
  • Mole does not search custom folders for file graphs. Check any graphs stored inside the candidate folders above before deleting them.

What this test covered

On September 19, 2026, Logseq was copied from its disk image into Applications, opened, and uninstalled with a Preview build of Mole 1.15. There was no Homebrew receipt. ~/Library/Application Support/Logseq was listed, left unselected and stayed on disk. The ~/.logseq and ~/logseq rows were added to Mole after this test, and the ~/.local/bin/logseq row on September 25, so that test does not show them being kept or removed. On September 26, 2026, Logseq 2.0.1 was installed again from its disk image, opened once and removed with a development build of Mole with every row ticked, including the unselected ~/logseq, ~/.logseq, ~/.local/bin/logseq and Application Support rows. Mole's Status page showed Logseq as one row of seven processes. All 16 items, the app included, went to the Trash, none of them was still on disk afterwards, and no login item or launch agent appeared. No graph content, plugin, Logseq Sync or Homebrew install was tested.