Semnote vs Obsidian: an honest comparison

Both Semnote and Obsidian store files on your machine. Both work without an internet connection. Both let you open your documents in other editors if you ever want to leave. That common ground — local files, user control, no cloud dependency — is real and worth noting. But the two tools are built for different purposes, and the differences matter more than the similarities.

What they share

Obsidian and Semnote are both local-first. Your files stay on your device by default. Neither requires an account to use (though Obsidian offers paid sync and publish services). Both work offline. Both treat plain text as the primary storage format.

If you care about owning your documents and not depending on someone else’s server, both tools respect that. This is not a trivial overlap — most document tools get this wrong.

Where Obsidian excels

Obsidian has been publicly available since 2020. It has a mature plugin ecosystem with over a thousand community plugins, an active community, and a well-understood workflow for linking notes into a knowledge graph. If you think in connections — linking ideas, building maps of content, navigating relationships between notes — Obsidian is built for that.

The graph view is not a gimmick. For researchers, writers with large vaults, and anyone who thinks visually about how their ideas relate, it is a genuine productivity tool. Nothing in Semnote replaces it right now.

Obsidian’s community is another real strength. There are community themes, plugins for nearly every workflow, and years of accumulated guides and templates. If you run into a problem, someone has probably written a plugin or a forum post about it.

If you want a rich knowledge graph with hundreds of community plugins and years of community knowledge to draw on, Obsidian is the obvious choice today.

Where Semnote differs

Semnote is a document environment, not a knowledge management system. The focus is on structured documents — writing that has a clear hierarchy, typed fields, and professional output — rather than networked notes.

Semnote uses SEML (Semantic Markup Language) as its primary authoring format. Where Markdown is deliberately minimal, SEML adds explicit structure: typed sections, metadata fields, and semantic relationships that survive across tools and time. Think of it as plain text that knows what it contains, not just how it looks.

This matters for documents that need to be durable. Contracts, policies, client deliverables, technical documentation — anything you might need to open, reformat, or migrate in five years. Markdown works well for short notes. For structured professional documents, it starts to strain.

Semnote also supports multiple output formats. The same document source can produce a web page, a PDF, or an export suitable for another system. Typst handles rendering underneath, which means typographic quality is high without requiring specialist knowledge.

The licensing model is different too. Semnote’s code is AGPL-3.0-or-later — you can read the source, verify what it does, and fork it if you need to. Obsidian’s core is proprietary. Whether that matters to you depends on how much you value being able to inspect and modify the tools you depend on.

Where Obsidian is the better choice right now

Semnote is in alpha. This is not a hedge — it means the software is early, the feature set is narrower than Obsidian’s, and things will change. If you need a stable, production-ready tool today, Obsidian has years of maturity that Semnote does not.

Specifically, stick with Obsidian if:

• You are deep in Obsidian’s plugin ecosystem and rely on specific plugins daily.
• You use the graph view as a core part of your workflow.
• You need a large, active community for support and shared resources.
• You want a stable tool that will not change its API or behaviour suddenly.
• You work primarily with short-form linked notes rather than structured long-form documents.

None of these are weaknesses in Semnote’s design. They are things Obsidian has earned through years of development that Semnote has not had yet.

Where Semnote might be worth exploring

If you care about document structure beyond what Markdown headers and bullet points offer — typed fields, semantic sections, professional formatting — Semnote is designed around that from the ground up rather than layering it on after the fact.

If you prefer open-source tools not because of ideology but because you want to verify what your software does and keep control of your toolchain, the AGPL licensing is a concrete difference.

If your work is more about producing polished documents than building a knowledge graph, the focus on professional output and multi-format export may fit better than Obsidian’s note-linking model.

And if you are comfortable using alpha software and want to shape how a tool develops — filing bugs, offering feedback, influencing direction — Semnote is at the stage where that input matters most.

Trying either

Obsidian is at obsidian.md. Semnote is at semnote.app. Both are free to try, both store files locally, and both let you leave with your data if you decide they are not right for you. That is the baseline every document tool should meet.