Notion vs Obsidian — How the docs said it works and how it actually felt

Picking between Notion and Obsidian isn’t just about features — it’s about how the tools flex (or collapse) under your actual, messy workflow. I use both, sometimes in the same hour, usually for different reasons, but occasionally because I forgot which one I had open in which tab ¯\_(ツ)_/¯.

I started leaning more into Obsidian after I hit two consecutive sync bugs in Notion where the same paragraph was duplicated three times on different devices — and worse, the rollback wouldn’t let me see the diff unless I exited the page.

1. How block-based editing in Notion treats your content like legos

In Notion, everything is a “block.” That sounds clean in a demo, but in real work sessions it can get weird — like when I dragged a multi-paragraph quote into a callout and only half of it moved. Or when I duplicated a column layout and lost the synced block status on a linked database view. You start feeling like you’re building a web app, not jotting thoughts.

Undo also behaves strangely when you’re working across toggles and nested bullets. I’ve repeatedly hit a situation where ctrl+Z undid the block relocation but didn’t remove the drag highlight — so it looked like the block was still selected, even though it wasn’t in the same spot.

There’s a deeper architectural layer that constantly auto-updates collaborators, which is great when it works. But in shared documents with multiple comments and toggled sections, we’ve run into a bug where clicking on a comment highlights the wrong block — which gets really confusing if you’ve collapsed that section because you didn’t want to look at it right now :P.

Nobody tells you that half the time you spend in Notion is tweaking layout to make it more readable for Future You. Padding out the sidebar with fake dividers, making nested headings just so, reordering database filters because the logic feels off at 10pm. It’s a productivity tool that becomes your Saturday night markdown sandbox.

2. Why Obsidian feels quieter until you install 14 plugins

Out of the box, Obsidian feels like a plain-text playground. If Notion is a whiteboard you share, Obsidian is a notebook you leave open on your desk. Except it syncs, backlinkifies your thoughts, and remembers where you were three documents ago.

But the power doesn’t show up right away. The first five days I used it, I thought: “Okay, so this is just a Markdown reader with some links.” Then I installed Dataview 😅.

After that it became something else. Suddenly I had YAML frontmatter controlling queries, smart links generating task lists, and a weekly review file that wrote itself using auto-populated block embeds. Sounds slick until you forget that one tag was capitalized and now your weeklies don’t show up in the query.

The plugin repo is both a gift and a trap. Here’s what I actually keep running (and still breaks sometimes):

• Advanced Tables — because pasting CSV directly creates chaos
• Templater — but only after I fixed its aggressive global date substitution
• Calendar — for muscle memory, even though its weekly outline fails to show tasks when linked inside callouts
• QuickAdd — which I broke by nesting macros inside templates with missing fields 🙁
• Periodic Notes — now patched so it doesn’t create a daily note with the wrong title format

If you try to do a simple thing (like create a button for “Insert Today’s Meeting Template”) you will spend at least an hour debugging nested variables because Obsidian won’t throw an error — it just… renders nothing.

Still, the local-first model saved me during a power outage that killed my Google Docs tab. I typed through the blackout, and Obsidian just synced changes to git when my hotspot rebooted. Notion would’ve just said “offline mode” and let me pretend I was being productive.

3. Daily notes and habits behave completely differently in each

Setting up a morning routine note in Notion is like building a webpage. You add: callout blocks for context, a synced template button for your agenda, maybe a dumb little quote at the top because you’re trying to be a person who reflects. It’ll look good, especially if you like toggles and progress bars. But it takes way more time than it should.

Obsidian, on the other hand, lets you make a daily.md file with three hash headers and some checkboxes — simple. Once you tie that to a template and invoke it with a hotkey (through Templater), it’s muscle memory. The friction to capture is basically zero. I wrote half this article from my daily note buffer.

Here’s the rough pattern I landed on:

– Notion: Structured plans, shared project timelines, docs that need a polished visual language
– Obsidian: Scratch thinking, idea journals, task pipelines coming from 6 apps (via plugins)

It’s worth noting: Notion’s recurring task options are limited unless you manually build property formulas or rely on external automation (like Zapier or Make.com). Meanwhile, Obsidian task recurrence works if you install the Tasks plugin — but breaks if you move the task between files before it checks off. Spent way too long on that one because it felt like I was going crazy.

4. Syncing across devices almost ends the debate

Here’s where stuff got a little too real.

I was in an airport gate lounge trying to update a Notion checklist. My laptop was dead, so I pulled out my phone. Opened Notion. Notes looked desynced. The app loaded but my edits from the lounge weren’t there. I refreshed manually. Still nothing. Two minutes later, the app forced me to re-authenticate. When it finally loaded again, I had four dupe entries for the same database row 😡.

Obsidian, meanwhile, with Obsidian Sync (which costs around the price of two burritos per month), immediately reflected my desktop edits on mobile. I did have to wait 10 seconds for the initial sync, but knowing it was git-backed and local made it feel solid.

However — one gotcha: Editing backlinks in mobile Obsidian is genuinely clunky. Long-pressing text gives inconsistent cursor control. Try renaming a note mid-sentence, and you’ll get stuck between rename modal and text buffer. Also, if your vault has more than 1,000 notes, the search on mobile starts feeling like dial-up.

In Notion, though, search is faster across linked databases, especially when you need to pull up last month’s client doc or remember a status page you soft-deleted. As long as the app is already open 🙂.

So yeah: syncing is less about whether it works and more about whether it breaks in a predictable way.

5. Linking notes and connecting ideas works better in one

There’s no easy way to say this: Notion backlinks are shallow.

Sure, if you @-mention a page, it shows up in the little “backlinks” section. But there’s no graph view. There’s no standard way to link a block across notes and see every note that references that atomic idea. It’s almost like backlinks were added to Notion reluctantly — they work, but barely.

Obsidian built its entire identity around connections.

[[Double bracket links]] create instant references, and the graph view actually means something once your vault gets over 200 notes. It was slightly overwhelming at first, but then I added a tag hierarchy and started limiting the view to specific folders — suddenly I was seeing patterns in my own writing. I found three related notes on attention residue I didn’t even remember writing. That never happens in Notion unless you manually comb your sidebar.

Also, the fact that you can link to exact blocks (like ^blockID) and then embed those blocks in other notes… that’s wizardry. Notion sort of has synced blocks, but once you edit it too many times or drag it into a different layout, it unsyncs silently. No warning. Just stops being connected.

I did break Obsidian backlinks once by using accented characters in filenames (blame the French tags I was experimenting with). Turns out certain characters caused Obsidian’s internal link engine to misbehave unless I URL-encoded them. Weird bug, but worth flagging.

Still, if you’re trying to think in a Zettelkasten-ish or crosslinked PKM flow, Obsidian actually holds onto your ideas without you having to build a navigation UI from scratch. That alone made the difference for me.