The Best Obsidian Alternatives in 2026

If you've outgrown Obsidian, or hit a wall with a specific plugin, sync, or mobile problem, the good news is that the space around it has quietly become interesting. Here's an honest comparison of the Obsidian alternatives worth trying in 2026, with concrete strengths and concrete failure modes for each.

Obsidian alternatives at a glance

Why people leave Obsidian

Obsidian is excellent at one thing, which is giving you a fast, local, linked markdown notebook with a plugin ecosystem. The moments people start shopping for alternatives tend to fall into four buckets, and each one points at a different replacement.

The first bucket is sync. Obsidian Sync is a paid subscription, and third-party sync through iCloud was designed to reconcile occasional file changes between Apple apps. When Obsidian saves a note and edits it again seconds later, iCloud can interpret the rapid writes as a server-side change requiring redownload, and users have reported Obsidian deleting the file rather than keeping a numbered backup. That's the kind of failure mode that sends people shopping.

The second bucket is the plugin model. Obsidian's power comes from community plugins, and plugin load order, sync timing, and version drift cause plugins to fail silently on startup, especially on devices where plugin files sync in after the app has already tried to load them. If you've ever opened your vault on a new device and found half your workflow missing for an afternoon, that's the one.

The third bucket is the markdown ceiling. Markdown is a beautiful format until you want a structured task with typed fields, a live chart off a table, or a component you can reuse across notes. Dataview queries read real values out of your notes, but the query itself is written as a code block inside a markdown string, and the abstraction shows every time you try to refactor.

The fourth bucket is mobile. Obsidian's iOS and Android apps are a real product, not a port, and they are still the most capable mobile markdown editors among this list. People leave for mobile reasons mostly when their Dataview-heavy or canvas-heavy desktop workflow doesn't map cleanly onto the phone surface, not because the mobile app itself is broken.

Each of the apps below answers at least one of these frustrations.

Logseq

Logseq is the closest Obsidian alternative for people who love the plain-markdown-on-disk model but want to work bullet-first rather than paragraph-first. It's an open-source outliner under AGPL-3.0 that stores every note as plain markdown or org-mode files on your filesystem. Daily notes, block-level bidirectional links, Datalog queries, and a graph view will feel familiar to anyone coming from Obsidian with a heavy Daily Notes and Dataview workflow.

Where Logseq wins. The outliner model is the big one. Every bullet is a real structured node, not a regex target, so Datalog queries work on actual data rather than parsing markdown after the fact. Block-level backlinks point at the bullet you linked, not at the page it happens to be on, which changes how reference-heavy workflows feel.

Where Logseq still hurts. The mobile apps are officially beta and carry concrete bugs, including an iOS graph-switch issue where users with multiple graphs can only open the first one from the picker. Sync across devices without the paid Logseq Sync subscription still means wiring up Git, Syncthing, or iCloud, with the same setup dance as Obsidian. If you write in paragraphs, pasting a multi-paragraph quote into Logseq splits it into one bullet per paragraph, which you then have to re-indent by hand.

Pick Logseq if your Obsidian wall is the prose-first editor or the Dataview ceiling, and you already think in outlines.

Anytype

Anytype is the bet that notes are objects with relations, and that plain markdown was always the wrong primitive for knowledge work. It's open source, local-first, and end-to-end encrypted by default. Your notes, projects, people, and tasks live as typed objects in an object library, with relations between them instead of free-form links between markdown files. The free tier includes 1 GB of managed backup, and the Plus and Pro plans sit at $5 and $10 per month for additional storage. Self-hosting a backup node keeps the whole stack free.

Where Anytype wins. The typed object model is the feature you don't realize you want until you've had it for a week. Filling in the fields on a "book" object and then querying "all books I marked finished this year" is the kind of thing that takes a custom Dataview query and three plugins in Obsidian. Built-in encrypted sync works across iOS, Android, Mac, Windows, and Linux without a subscription if you self-host.

Where Anytype still hurts. The on-disk storage format is proprietary to Anytype, even though the whole codebase is open. Importing an existing Obsidian vault is a manual translation because the two tools think in different units, and there's no official Obsidian importer today. The mental model of objects and relations takes a real week to click compared to "here is a folder of markdown files."

Pick Anytype if your Obsidian wall is the flat markdown ceiling and you want to think in structured objects without losing local-first ownership.

AFFiNE

AFFiNE is the one that tries to combine a Notion-style block editor with a Miro-style whiteboard in the same workspace. It's open source and built on a local-first data engine called OctoBase, with optional cloud sync and a free self-hosted option for people who prefer to run their own server.

Where AFFiNE wins. If your note-taking regularly spills onto a whiteboard, like architecture diagrams, meeting maps, or sketches that link back to docs, AFFiNE is the only serious open-source tool that treats both modes as first-class. The block editor is close enough to Notion in feel that onboarding is short for anyone coming from that camp. Whiteboard mode handles shapes, connectors, and embedded live documents on one canvas.

Where AFFiNE still hurts. The storage format isn't plain markdown, so your notes are not portable in the Obsidian sense, and export currently loses block-level features that the markdown spec can't represent. AFFiNE is built on BlockSuite, an evolving block editor toolkit, and block types shipped in one minor release have been restructured in the next, which breaks custom blocks you may have relied on between upgrades. It's a heavier download and a heavier runtime than Obsidian, which matters on older laptops.

Pick AFFiNE if your Obsidian wall is the absence of a canvas sitting side by side with your docs.

SilverBullet

SilverBullet is the one I'd recommend to anyone who wants Obsidian's philosophy but thinks "plain markdown plus a plugin marketplace" is the wrong extension mechanism. It's a self-hosted, MIT-licensed wiki that stores your notes as plain markdown files on disk and embeds a Lua scripting layer so you can query and transform your own notes like a database.

Where SilverBullet wins. Your notes are plain markdown. Your queries are Lua code blocks that render inline. The two layers compose instead of bolting a plugin runtime onto a text editor. SilverBullet ships as a single binary or Docker container, which turns self-hosting from a project into a command. The hybrid WYSIWYG-and-markdown editor is pleasant in a way that Obsidian's edit-mode toggle is not.

Where SilverBullet still hurts. There is no first-party mobile app today, so phone access means opening the hosted URL in a browser. There is no managed sync either, so you host it yourself or you don't use it. SilverBullet has no plugin marketplace, so every custom behaviour is code you write yourself, which is an honest win for some readers and an honest deal-breaker for others.

Pick SilverBullet if your Obsidian wall is the plugin load-order problem and you'd rather write fifty lines of Lua than audit fifty community plugins.

Apple Notes

Apple Notes is the dark-horse alternative that most power users dismiss too quickly. It's proprietary, iCloud-backed, and free with any Apple ID. It's also the lowest-friction capture surface that exists if you live in the Apple ecosystem, and in the last few years it added document scanning, tags, and linked notes.

Where Apple Notes wins. Capture is instant across iPhone, iPad, Mac, and Watch. Sync is the OS feature, not a subscription, and it does not hit the race conditions that break Obsidian on iCloud because Apple Notes was designed for the same sync engine from day one. There is zero setup. For readers whose Obsidian frustration is "I spend more time maintaining my notes than writing them," this is the trade worth considering.

Where Apple Notes still hurts. The data lives on Apple servers in a format you do not own, and the export options are either PDF or a share sheet, with no bulk markdown export. There is no Windows, Linux, or Android client, and the iCloud for Windows app does not surface Notes at all. There is no serious backlink system, no queries, no community plugins, and no advanced organization beyond folders and tags.

Pick Apple Notes if your Obsidian wall is maintenance overhead and you've decided that frictionless capture is worth giving up the graph.

CoCube

CoCube is the one I'm building, so this section is the one I'll try hardest to keep honest. CoCube is not a drop-in Obsidian replacement today. If your current workflow is a pile of markdown files with backlinks and Dataview queries, Obsidian or Logseq is still the closer match.

CoCube is the bet that a note should be a tree of typed cells on top of a CRDT format, and that a knowledge tool should let you build small components the way a spreadsheet lets you build small formulas. Every document is stored as a Loro CRDT in a local database on your device, the sync layer ships binary deltas between devices you own, and the underlying format is documented. The broader data story is laid out in the local-first article. The programmable-workspace story is in the visual programming post and in the composable software vision article.

Where CoCube wins today. The reactive cell model lets you build a Dataview-like view without leaving the document format, because the cells the view reads are the same cells the note is written in. CRDT sync is built in, works offline, and does not require a subscription. The on-disk format is an open Loro CRDT, so your documents aren't trapped in CoCube even though the editor itself is closed source during the current beta.

Where CoCube still hurts today. Importing a large Obsidian vault is a manual process and loses Dataview-specific structure. There is no plugin marketplace and no third-party theme ecosystem. The app is closed source today, which matters if "open source" is the line in the sand that brought you to this roundup.

Pick CoCube if your Obsidian wall is the static markdown ceiling and you are more interested in building your own reusable components than finding a prebuilt plugin for a problem.

How to pick

Work backwards from your own frustration.

If your Obsidian wall is sync reliability, look at Anytype, AFFiNE, or CoCube, which all use CRDT or encrypted object sync as a first-class feature rather than a file-sync hack.

If your Obsidian wall is the plugin load-order problem, look at SilverBullet and Logseq.

If your Obsidian wall is the markdown ceiling, look at Anytype, AFFiNE, and CoCube.

If your Obsidian wall is canvas and diagrams, AFFiNE is the only serious answer.

If your Obsidian wall is maintenance overhead, Apple Notes is the honest answer.

One honesty note on this roundup. I've deliberately avoided running any of these apps as my actual second brain while I'm building CoCube, to keep the design space clear of other people's conventions. The one exception is Apple Notes, which I use as scratch memory for things I need to remember for the next three minutes, like a dentist appointment, not anything I'll ever go back and search for. Everything above is sourced from primary material, meaning GitHub issues, forum threads, and project docs, rather than from a year of running each tool as my own knowledge base. If you want the lived-experience version of any of these, the app subreddits and the r/PKMS community are where to go.

FAQ

What is the best open-source Obsidian alternative?

Logseq is the closest open-source match for the Obsidian workflow, especially for anyone who thinks in outlines and daily notes. Anytype and AFFiNE are stronger if you are willing to give up plain markdown in exchange for structured objects or a combined docs-and-canvas workspace. SilverBullet is the best pick if you want to stay in plain markdown but route extensibility through Lua scripts in your own notes instead of a plugin marketplace.

Is Logseq really a replacement for Obsidian?

For people whose Obsidian workflow is heavy on Daily Notes, block references, and Dataview queries, Logseq replaces those three things with first-class structured versions. For people whose workflow is prose-first and plugin-heavy, Logseq is a different tool with a different mental model, and it will feel like one.

Which Obsidian alternative is best for mobile?

Obsidian's own mobile app is still the most capable markdown editor on phones, and nothing in this list beats it on mobile markdown editing specifically. Anytype has the most polished cross-platform mobile experience among the non-markdown local-first tools. Apple Notes is the least friction if you only use Apple devices.

Are any of these tools fully local-first?

Logseq, Anytype, AFFiNE, SilverBullet, and CoCube all treat the copy of your data on your device as the primary copy, which is the definition used in the local-first article. Apple Notes does not fit the definition because the primary store is iCloud, not your device. Obsidian itself does fit the definition, which is a real reason to stay if local-first ownership is the only thing that brought you here.

Is CoCube open source?

Not today. CoCube is closed source during the current beta. The data format on disk is a Loro CRDT, which is open source, so your documents are portable even though the editor is not.

What to read next

If you're picking an alternative to Obsidian because you want real data ownership, the local-first article is the framework for evaluating that. If the part you miss from a knowledge tool is the reactive, spreadsheet-like calculation layer, the reactive programming article is the one to read next. If you haven't yet built a sustainable PKM system underneath whatever tool you pick, the PKM guide is the pillar for that whole arc. If you've heard the term "second brain" and want to know how it fits, the second brain article is the sibling post. The vision behind why CoCube exists lives in the composable software post.

Pick the tool whose specific failure modes you can live with. Every tool in this post has a different one, and pretending otherwise is how roundups stop being useful.