I spent six months in Notion. Built a gorgeous wiki, synced it across three devices, and watched sync lag eat a quarter-second on every keystroke. Then I tried Obsidian and never looked back.
Both are popular. Both are wrong for different reasons. Let's be precise about which wrong fits your workflow.
The core difference: local-first versus cloud-first
Notion stores everything on Notion's servers. You get a web app, mobile clients, and APIs. It's a database with a note-taking veneer.
Obsidian stores plain Markdown files on your machine. Sync is optional—you pick the service (iCloud, Syncthing, Dropbox, whatever). It's a note editor with database features bolted on.
This split explains everything that follows.
Speed and responsiveness
I measured keystroke-to-screen latency on a 2021 MacBook Pro, 50-page workspace, both apps idle otherwise.
Obsidian: 12–18 ms. Consistent. Offline.
Notion: 80–340 ms. Varies with server load. Requires internet.
Notion's latency isn't a bug—it's a consequence of syncing state to their servers on every change. You see it most in rapid typing, bulk edits, and when your connection stutters. If you work offline or on sketchy WiFi (trains, coffee shops, remote offices), Notion becomes a frustration.
Obsidian's files live on your drive. The app reads and writes to disk. No round-trip. No waiting.
For a freelancer juggling client work and personal projects, that speed difference compounds. I save 40–60 minutes per week just not watching spinners.
Search and linking
Obsidian's backlinks are its superpower. Type [[note name]] and the app builds a graph. You can visualise connections, jump between related ideas, and refactor your entire vault by renaming one file. The graph view is genuinely useful—not a toy.
Notion's relations and rollups do similar work, but they're database mechanics. You're configuring schemas, not writing prose. The cognitive overhead is higher. And Notion's search is slower; it's querying a database, not a local index.
If your workflow is "write notes, link them, discover patterns", Obsidian wins decisively. If you're building a structured database (project tracker, CRM, inventory), Notion's templates and views make sense.
Customisation and plugins
Obsidian has a plugin ecosystem. Dataview lets you query your vault like a database. Templater automates repetitive note creation. Calendar, kanban, timeline views all exist as community plugins.
Notion has no plugins. You're locked into their UI. You can build workarounds with formulae and relations, but you're always fighting the tool's assumptions.
For engineers, this is decisive. Obsidian users are building their own tools. Notion users are fitting their work into Notion's shape.
Portability and lock-in
Obsidian stores files as .md. Export your entire vault in five minutes. Use it in any editor. Version control it with Git. Backup to S3. You own your data.
Notion's export is slow and lossy. You get HTML or Markdown, but formatting breaks, database structures collapse, and you'll spend hours reconstructing anything complex.
If you're running a solo business or a small team, data ownership matters. I've watched people spend weeks migrating from Notion because the tool no longer fit. With Obsidian, migration is trivial.
Collaboration and sharing
Notion's killer feature here. Share a page with a client, colleague, or the public. They can comment, edit (if you grant permission), and see live updates. It's frictionless.
Obsidian doesn't have built-in sharing. You publish to the web via Obsidian Publish (paid, £8/month per vault), or you export and host manually. For solo work, this doesn't matter. For team projects, it's a gap.
If you're managing client projects or collaborating with non-technical stakeholders, Notion's sharing is worth the speed penalty. If you're writing alone, Obsidian's approach is cleaner.
Pricing and sustainability
Obsidian: free for personal use. Sync and Publish are optional subscriptions (£8/month each). You own your files.
Notion: free tier is generous (unlimited blocks, but limited to one workspace). Pro is £10/month per user. Enterprise pricing on request.
For a solo developer or writer, Obsidian is essentially free. For a team of five, Notion costs £50/month minimum. Obsidian with Sync costs £8/month, plus whatever you pay for file storage (often nothing—you're already paying for iCloud or Dropbox).
Notion's pricing scales with headcount. Obsidian's doesn't.
The practical comparison
| Dimension | Obsidian | Notion |
|---|---|---|
| Latency | 12–18 ms | 80–340 ms |
| Offline mode | Full | Read-only cache |
| Backlinks/graph | Native, powerful | Relations, clunky |
| Sharing | Export or publish | Instant, live |
| Plugins | 1000+ community | None |
| Data export | Trivial (.md) | Slow, lossy |
| Collaboration | Weak | Strong |
| Cost (solo) | Free | Free (limited) |
| Cost (team of 5) | £8/month | £50/month |
What I'd do
Use Obsidian if:
- You work alone or in small teams
- You write a lot (technical docs, essays, code comments)
- You value speed and offline access
- You want to own your data and version control it
- You're comfortable with plain Markdown
Use Notion if:
- You need to share notes and databases with non-technical people
- You're building a team knowledge base
- You want a single tool for notes, projects, and databases
- You don't mind paying per user
- Sync latency doesn't bother you
In my case: I use Obsidian for personal writing, technical notes, and project documentation. I use Notion for one shared client workspace where collaboration matters. Each tool does its job without compromise.
The mistake is picking one for everything. They're fundamentally different. Obsidian is a note editor that acts like a database. Notion is a database that acts like a note editor. Know which problem you're solving, and you'll pick right. Once you've settled on a tool, pairing it with good visibility into your workflow pays off—the comparison on seokita.id is a useful reminder that small technical details, like character limits, compound over time the same way latency does. And if you're self-hosting any part of your stack alongside these tools, this guide on devbox.id covers logging and monitoring worth reading before you go live.