Notion vs Obsidian for Working Writers (And the Third Option Nobody Talks About)

I have used Notion every day for three years. I have used Obsidian every day for two years. I have used both simultaneously for eight months. I will tell you, with reasonable confidence, what each is actually good for, what each fails at, and what the third option is that most working writers eventually drift toward but that almost nobody on the productivity-tool internet writes about. The third option is the actual answer for most writers. The Notion-vs-Obsidian debate is a distraction from it. I’ll explain.

The TLDR for people who came here in a hurry: Notion is for project management, Obsidian is for thinking, and the third option (a plain folder of plain text files) is for writing. If you only need one tool, you probably need the plain folder. The other two are sometimes useful supplements. The argument is below.

Notion: what it actually does well

Notion is a structured-data tool dressed up as a notebook. The fundamental object is a database, and almost every Notion power-user workflow is, at the architecture level, a clever use of databases with different views and relations.

What Notion is genuinely excellent at: tracking projects (clients, deadlines, deliverables), maintaining structured reading lists, organizing research with consistent metadata, building dashboards that show you what’s overdue, sharing work-spaces with collaborators who need to see status at a glance. If you have a writing business with multiple clients, multiple book projects, multiple revenue streams, Notion is the cleanest single tool for tracking the whole portfolio.

What Notion is bad at: actual writing. The Notion editor is fine for short-form notes but degrades noticeably for long-form work. Long documents become slow to edit. The block-based architecture, which is excellent for project tracking, is awkward for prose flow. The lack of a good distraction-free writing mode (there is one, but it’s hidden and incomplete) means that when you are trying to write 3,000 words, Notion’s UI is constantly visible and constantly demanding little decisions about block types.

The deeper failure: Notion’s data is trapped in Notion. The export options (Markdown, HTML, PDF) work but produce files that lose the database relationships and the formatting nuance. If you maintain three years of writing inside Notion and Notion changes pricing, gets acquired, or shuts down (any of which is possible on a 7-year horizon), the cost of extracting and migrating your work is substantial. Most Notion users do not think about this risk because the platform feels permanent. It is not.

Obsidian: what it actually does well

Obsidian is a markdown editor that operates on a folder of plain text files on your local machine. The fundamental object is a note, and the value-add is the bidirectional linking between notes and the visualization of the link graph.

What Obsidian is genuinely excellent at: thinking-with-your-notes. The Zettelkasten / second-brain crowd has built up an extensive practice around using Obsidian to capture ideas, link them to related ideas, develop them over months, and surface unexpected connections through the link graph. For the kind of working writer who reads voraciously and wants to develop arguments across multiple essays / projects / books, Obsidian is the cleanest tool for that workflow.

What Obsidian is bad at: project management. The plugin ecosystem can extend Obsidian into project tracking (Tasks plugin, Kanban plugin, Dataview), but the result is fragile and reliant on community plugins that may break with platform updates. If you need to track ten clients with deadlines, Obsidian is not the tool; Notion is.

Obsidian is also bad at finishing things. The bidirectional-linking architecture rewards continuous note-development; it does not, by structure, push you toward shipping a finished essay or book. Many heavy Obsidian users have enormous note libraries and surprisingly little finished output. The system rewards thinking, not delivering. This is sometimes a feature, often a bug.

The deeper strength: Obsidian’s data is yours. The notes are markdown files in a folder on your computer. If Obsidian disappears tomorrow, you open the same folder in any other text editor and your notes are intact. This is the single biggest reason Obsidian users stay loyal to it; the data sovereignty is real and matters.

The third option: a plain folder of plain text files

Here is the option nobody recommends because it doesn’t have a marketing budget: a plain folder of plain text or markdown files, organized by date and project, opened with whatever text editor you like.

For long-form writing, this option is structurally superior to both Notion and Obsidian. Reasons:

It is faster than either. A plain text file opens instantly. A Notion page takes 1-3 seconds to load. An Obsidian vault with a few thousand notes takes 5-10 seconds to fully index. Multiplied across a working day where you open files dozens of times, the speed difference is real productivity.

It is more durable than either. A folder of plain text files can be opened by any text editor that has ever existed and any text editor that ever will exist. Markdown is sufficiently universal that a 2026 markdown file will be readable on whatever text-editor we are using in 2056. Notion and Obsidian both have non-zero risk of becoming unusable on a 30-year horizon.

It is more focused than either. A plain text editor (BBEdit, Sublime Text, VS Code, vim, IA Writer, Lex, etc.) does one thing: present your prose for editing. There is no database to maintain, no link graph to nurture, no plugin ecosystem to manage. You write. You save. You open the next file. The lack of features is the feature.

It composes better with other tools. A folder of plain text files can be searched with the operating system’s built-in tools, version-controlled with git, backed up to any cloud service, processed with any scripting language, fed into any AI tool, and migrated to any other system in seconds. The format’s universality is its leverage.

What the plain folder is bad at: project management (use a separate tool like a Things or OmniFocus, not built into your writing files), structured database work (use Notion or a real database), and second-brain link graphs (use Obsidian if you want this; the writing files don’t need it).

The architecture I recommend for most working writers, after years of experimentation: a plain folder of markdown files for actual writing, plus one or two narrowly-scoped tools for the specific workflows the plain folder doesn’t handle. Notion for project tracking. Obsidian for research and idea-development. Both at light usage, with the writing always living in the plain folder.

What the productivity-tool internet keeps getting wrong

The Notion-vs-Obsidian debate dominates writing-tool discourse online because both companies have substantial marketing presence and active user communities that produce enormous amounts of free content (YouTube tutorials, Twitter threads, course offerings) about how to use the tools. The plain-folder option has none of this. There is no “Plain Folder Productivity Guru” with a 200,000-subscriber YouTube channel. The plain folder does not need an evangelist; you discover it by trying everything else and noticing what survives.

Tiago Forte’s Building a Second Brain (canonical book in this space) is mostly tool-agnostic but tends to default to Notion-shaped examples; Andy Matuschak’s working notes (one of the most influential examples of the digital-garden / Zettelkasten genre) are built in a custom system that nobody else can use; Maggie Appleton has written extensively about digital gardens in tools that range from custom HTML to Obsidian to Roam. The thoughtful end of the second-brain literature is more nuanced than the tool-bro YouTube version, but it still tends to assume the tool is doing more of the work than it actually is.

The honest picture, after a decade of writing-tool evolution: tools are mostly substitutable. Workflows are not. The writer who has a clear workflow (capture, develop, draft, finish) will produce work in any tool. The writer who does not have a clear workflow will struggle in every tool. Switching from Notion to Obsidian (or vice versa) does not produce a workflow; it just changes the friction profile of your existing workflow’s failures.

My current actual setup, for the record

I work in a plain folder of markdown files, organized by year and project type, opened in IA Writer (paid app, focused-writing mode is the cleanest I’ve found). I keep a Notion workspace for client tracking and invoicing only; nothing else lives there. I keep an Obsidian vault for research notes and book-development thinking; the vault is separate from my writing folder and does not sync. The three tools do not interact with each other. Each does one thing.

This setup took me about four years to arrive at. I started in Scrivener (great tool, the long-form-fiction option I’d still recommend for novelists), tried Ulysses (too rigid for my workflow), then went deep on Notion (collapsed under its own complexity), then went deep on Obsidian (collapsed because I stopped finishing things), then arrived at the current three-tool minimal setup.

If I had skipped all the experimentation and just started with the current setup, I would be five years more productive than I currently am. I am telling you this so you can skip the experimentation. Do the plain folder. Add a project-tracker if you have client work. Add Obsidian if you have a research-development practice. That’s it. Stop reading productivity-tool YouTube. Stop optimizing your tool stack. Write the next thing.

What about specific writing apps? (Scrivener, Ulysses, IA Writer, etc.)

Briefly, because this is the question I get most often:

Scrivener is the canonical long-form-fiction writing tool. If you write novels, it is genuinely useful for managing chapter structure, character notes, and research alongside the prose. The cork-board view and the ability to rearrange chunks are excellent. The corkboard learning curve is steep. Worth the investment if you write novels regularly.

Ulysses is similar but cleaner-designed and more aggressively focused on the “writing in markdown” workflow. Worth trying if Scrivener feels heavy to you.

IA Writer is what I currently use. It’s a focused-mode markdown editor with one-thing-at-a-time UI. Fast, durable, simple. Highly recommended for essay-and-blog-post writers. Less useful for book-length projects.

Lex.page (browser-based, AI-augmented) is what I use for occasional first drafts when I’m at a different machine.

For a broader rundown of the writing-software landscape including the non-AI tools I rely on, the comprehensive writing-app guide on creativindie covers the full map. Most of it is still relevant. Apps come and go, but the writing-tool category has matured to a point where the major options are stable and serve specific use cases.

The takeaway, again

Notion is for project management. Obsidian is for thinking. The plain folder is for writing. Most writers need the plain folder primarily and one of the others secondarily. Almost no writer actually needs both Notion and Obsidian simultaneously, regardless of what the productivity-tool YouTube channels imply.

Stop optimizing your tool stack. Write the next thing.

You have eighteen lifetime years of productive writing time, optimistically. You have spent at least three of them, statistically, on tool optimization. That is a real fraction of your remaining career to spend reading reviews of writing apps. Go write.