All comparisons

Compare

Memos vs Logseq

Choose Memos if you want a server you reach from any browser and notes that stand on their own. Choose Logseq if you think in outlines, block references, and a local graph.

Logseq is an open-source outliner that stores Markdown or Org-mode files on your device and links every block. Memos is an open-source web app on your server where each memo is a short, standalone entry in a timeline. Both are free; they differ on where notes live and how they connect.

LicenseOpen source (MIT)Open source (AGPL-3.0)
HostingSelf-hosted web serverLocal files on each device
SyncServer-based; open it in any browserLogseq Sync, git, or iCloud
FormatMarkdown memos in a databaseMarkdown or Org-mode files
Best forShort standalone memosOutlines, journals, block references
CostNo license fee (you host)Free; paid Logseq Sync
Facts checked October 2026.

The decision

Choose for the work in front of you.

Choose Memos when

  • You want one instance on a server, open in any browser, with no file sync to manage.

  • Your notes are short and standalone rather than nested outlines.

  • You want to share a memo publicly or post to the API from scripts.

Choose Logseq when

  • You outline and reference blocks across daily journal pages.

  • You want local files you can open with any editor, fully offline.

  • You rely on plugins and the graph view.

Feature by feature

What each one actually does.

Memos answers honestly, including the rows where it says no.

Ownership
Open sourceYes.MIT license, developed in public on GitHubYes.AGPL-3.0
Self-hostingYes.Docker image or a single binary on your serverPartial.Local files; sync through git or your own storage
Official hosted serviceNo.No official hosted plan; you run the instancePartial.Logseq Sync, paid
Where notes liveSQLite, MySQL, or PostgreSQL on your serverMarkdown files in a local folder
PriceNo license fee; you pay for hostingFree; paid Logseq Sync
Writing
MarkdownYes.Write in Markdown with live rendering, code blocks, and mathYes.Markdown or Org-mode files
TagsYes.Inline #tags, nested with a slashYes.Tags are pages
Links between notesYes.Relations link memos to each otherYes.Block references, backlinks, graph view
AttachmentsYes.Images and files, stored on disk or in S3Yes.Assets folder next to the files
Full-text searchYes.Full-text search with tag, date, and visibility filtersYes.Full-text search across the graph
Reach
Works offlineNo.Browser app; reading and writing need a reachable serverYes.Local-first
Desktop appPartial.Install the web app as a PWA; no official native appYes.Windows, macOS, Linux
Mobile appPartial.PWA on iOS and Android, plus community-built appsYes.iOS and Android
Cross-device syncYes.The server is the source of truth, so every device sees the same memosPartial.Logseq Sync, git, or iCloud
Public sharingYes.Per-memo visibility: private, workspace, or public linkPartial.Publish a static site yourself
Data
API and webhooksYes.REST and gRPC APIs, signed webhooksPartial.Plugin API and local HTTP API
Import and exportPartial.ZIP export of Markdown and JSON; import from Memos exports onlyYes.Plain files; imports Roam and OPML
End-to-end encryptionNo.The server you run can read your memos; protect it with TLS and disk encryptionPartial.Logseq Sync is end-to-end encrypted; local files are plain

Questions

Questions people ask.

Is Memos a self-hosted alternative to Logseq?

For daily short notes, yes. Memos runs on a server instead of syncing files between devices. It does not have an outliner or block references.

Can I keep daily journal pages in Memos?

Memos is already a journal: every memo is timestamped in a timeline you filter by date and tag. There are no separate journal pages to create.

Can I import a Logseq graph into Memos?

Not with a built-in importer. Your graph is plain Markdown, so you can script memos through the Memos API.

Start here

Start with one memo.

Install Memos on a server you choose and write your first memo. Open source under MIT, with no license fee.