Choose a download

Windows x64Intel or AMD Windows Arm64Arm / Snapdragon

How to uninstall Logseq on Windows

Your Logseq graphs are the part that matters, and removing the app does not remove them. 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 %USERPROFILE%\logseq\graphs\<graph name> as a database file plus an assets folder. Back up both kinds first, and never delete a graph folder to tidy up after an uninstall. This guide covers machine and user installations from the Logseq.Logseq winget package. Use the path for the installation being removed.

Quit Logseq first

Save your work and close every Logseq window. Logseq ran five processes in this test, so check Task Manager (Ctrl+Shift+Esc) for any Logseq.exe still listed before you uninstall.

Remove the app with its own uninstaller

Go to Settings › Apps › Installed apps, find Logseq, and choose Uninstall, or run:

winget uninstall --id Logseq.Logseq

Back up before you remove data

For a file graph, copy the whole graph folder somewhere else first. For a DB graph, use Logseq's own export option before you remove anything. Plugins and app settings live in %USERPROFILE%\.logseq; copy that folder if you want them back after a reinstall.

Where the data lives

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
%USERPROFILE%\logseq DB graphs, each with its database and assets Keep it; never remove it as a leftover
%USERPROFILE%\.logseq Plugins and settings Keep it for a reinstall; remove only for a clean start
%APPDATA%\Logseq The app's own local data and caches Safe to remove after quitting once you no longer need local state
%LOCALAPPDATA%\Logseq-updater Downloaded update installers Safe to remove

Check the result

Run these read-only commands after the uninstall finishes:

Get-CimInstance Win32_Process -Filter "Name = 'Logseq.exe'" -ErrorAction Stop | Select-Object ProcessId,ExecutablePath
winget list --id Logseq.Logseq
Test-Path "${env:ProgramFiles(x86)}\Logseq"
Test-Path "$env:LOCALAPPDATA\Programs\Logseq"
Test-Path "$env:USERPROFILE\logseq\graphs"
Test-Path "$env:USERPROFILE\.logseq"
Test-Path "$env:APPDATA\Logseq"
  • A successful process query with no output means no Logseq.exe was found. A query error leaves its running state unknown.
  • A completed winget list query with no match means the package record is gone; a matching row means the uninstall did not finish.
  • The two program paths cover machine and user installs. Check the path used by this installation: False means that path is absent, and True means it still exists.
  • Test-Path "$env:USERPROFILE\logseq\graphs" only checks whether the path exists. It does not list graph names or prove database integrity. False cannot prove that no graph ever existed; check your backup before continuing.
  • Test-Path "$env:USERPROFILE\.logseq" returning True is expected if you kept your plugins.
  • Test-Path "$env:APPDATA\Logseq" returning True means the app's local data and caches are still there, which is expected unless you removed them yourself.

If you installed it with winget

winget uninstall runs the same NSIS uninstaller Settings › Apps uses and removes the same program files; it does not touch %USERPROFILE%\logseq, %USERPROFILE%\.logseq or %APPDATA%\Logseq on its own.

Account and sync

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

What Mole lists

For Logseq installed per-machine from winget:

  • The program folder, the Start Menu shortcut, the desktop shortcut and a logseq:// link registration are selected by default.
  • %USERPROFILE%\logseq is personal data, unchecked and excluded from bulk app-data selection. Selecting this personal-data row individually can still delete graphs. %USERPROFILE%\.logseq contains plugins and settings; it is Review and unchecked, but including app data includes it.
  • %APPDATA%\Logseq is listed but not selected. The Chromium cache folders inside it, such as Cache, Code Cache and GPUCache, are separate rows selected by default.
  • %LOCALAPPDATA%\Logseq-updater, which holds only downloaded update installers, is 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

The first check used machine-installed Logseq 2.0.1 and its NSIS uninstaller (Uninstall Logseq.exe /allusers /S). Graph and preference folders were not yet offered, so that run did not prove personal-data protection during bulk selection. The 2026-10-04 user-install retake verified detection of both folders and unchecked, bulk-excluded graphs. Logseq Sync, accounts and database content integrity remain unverified.

The 2026-10-04 per-user retake used %LOCALAPPDATA%\Programs\Logseq. Source Mole lists %USERPROFILE%\logseq graphs as personal data, unchecked and excluded from bulk data selection. After the measured bulk uninstall, the program and registration were absent while the existing 389120-byte Demo graph database remained. The .logseq preferences were recycled because this test explicitly included review data. The formal download package has not been verified.