Obsidian treats your notes as plain Markdown files on disk and builds its interface around linking them: double-bracket a phrase and it becomes a navigable connection, with a backlinks pane showing every note that points here. The editor is split-pane by default — source and preview — and the workspace is a tiling system of movable panels rather than a single document view. The graph view renders your vault as a node-link diagram, a divisive feature that's either insight or decoration depending on how you work. A command palette and hotkeys make it keyboard-navigable, and a plugin marketplace means the interface is really a platform. The trade is curation: local-first freedom and infinite linking can become unstructured sprawl without personal discipline.
App store
Flows
Flows for Obsidian are being captured
We haven't taken Obsidian apart screen by screen yet. Explore the UX patterns it's known for, or request an audit of your own product.
Request a UX auditApp store
Flows
Flows for Obsidian are being captured
We haven't taken Obsidian apart screen by screen yet. Explore the UX patterns it's known for, or request an audit of your own product.
Request a UX auditLanding page
We haven't captured Obsidian's landing page yet.
Flows
Step through each flow screen by screen.
Notable UX patterns
How does your product compare to Obsidian?
Get a free UX Snapshot of your page — a quick read on what works and what to fix.
Teardowns
Teardowns of Obsidian are coming
We haven't published a written teardown of Obsidian yet. Explore related topics, or request an audit.
Request a UX auditFree course
WCAG 2.2 Fundamentals: Audit a Screen for Accessibility
6 lessons · ~25 min
Start lesson 1 →