Obsidian: A local-first notes app where your knowledge base is just Markdown files

Summary

Obsidian is a note-taking app that stores notes as plain Markdown files on your own device and centers on linking ideas together. It appeals to people building a long-term personal knowledge base who want their data in an open, portable file format.

Most note apps quietly make a bet on your behalf: that you will stay with them forever, so it is fine to keep your notes in a closed format inside their cloud. Obsidian makes the opposite bet. Your notes are plain Markdown files sitting in a folder on your own device, readable and movable with any other tool, even without the app itself. For people who think of their notes as a long-term asset rather than disposable scratch, that single design choice is the whole reason to look at it. The app layers genuinely useful things on top of those files — links between notes, a graph view of how ideas connect, and a deep plugin system — but the notes underneath stay in an open, portable Markdown format. That distinction is worth keeping straight: the app itself is a proprietary product, not an open-source project, but your data is not locked inside it. That matters because the biggest risk with a knowledge base is not losing a note next week; it is discovering in five years that your accumulated thinking is trapped in a format or service you can no longer get it out of cleanly. Plain files are the hedge against that, and it is a hedge that costs you nothing day to day. Who is this for? Developers, researchers, and writers who pile up notes over years and need to find and connect them later, plus anyone who simply prefers owning their data in a portable form. The linking-first approach nudges you toward building connected knowledge rather than a graveyard of isolated documents, which is the difference between a notes app that gets more valuable over time and one that just gets bigger. The honest caveat is a behavioral one, and it is worth saying plainly because it is the most common way people get burned. The flexibility and the plugin ecosystem make it dangerously easy to spend your time engineering an elaborate system instead of actually writing notes — the tool can quietly become the hobby. The freedom that makes it powerful is the same freedom that invites endless tinkering, and the people who get the most from it tend to be the ones who deliberately keep their setup boring. Syncing across devices and any collaboration also depend on specific options or services you choose, so it is worth confirming those fit your privacy expectations rather than assuming. For MIH News readers, the debate worth having is whether a local-first, file-based approach genuinely improves long-term knowledge work, or whether the freedom mostly invites over-engineering. Data ownership and portability are real, durable strengths; the tinkering trap is a real, recurring weakness. The most useful contributions would come from people who have used it for years rather than weeks: how they kept their system simple, which handful of plugins actually earned their place, and how they solved sync across devices without compromising the local-first promise that drew them in.

Why it matters

This submission was added for community review because it may help builders discover useful software, ideas, or technical work worth discussing.

Open source link