Your Notes in Plain Text: The Obsidian Philosophy of Markdown

Imagine this: it's 2075, fifty years from now. You want to read notes you wrote today.

With Notion, you'd need Notion's servers to still exist and support the old format. With OneNote, you'd need Microsoft. With Apple Notes, you'd need an Apple device.

With Obsidian, you'd just open a text file. That's the power of Markdown.

This philosophy—storing everything as plain-text Markdown files—isn't a technical limitation of Obsidian. It's a deliberate design choice. And it's one of the reasons Obsidian is uniquely suited for building a long-term second brain.

Why Markdown Matters

Markdown is a simple syntax for formatting text. Created in 2004 by John Gruber, it's designed to be:

• Human-readable: Even the raw markdown file is easy to read
• Simple: A few characters (# for headers, * for bold) express formatting
• Portable: Any text editor can open it
• Durable: Plain text never becomes obsolete

# This is a header

This is a paragraph with **bold** and *italic* text.

- This is a list
- With multiple items

[This is a link](https://example.com)

Even if you've never seen Markdown before, this is immediately understandable. The syntax is so intuitive that it's been adopted by developers, writers, and academics worldwide.

Compare this to proprietary formats:

Notion's format: Stored on Notion's servers in a proprietary JSON structure. If Notion goes out of business or changes their export format, you're stuck.

Microsoft Word (.docx): A zipped XML file with embedded metadata. Open it in a text editor and you see gibberish.

Apple Notes: iCloud-only, encrypted, impossible to export cleanly.

Evernote (.enex): An XML format that's nearly impossible to migrate to another platform without data loss.

Markdown is different. It's not just readable; it's canonical. The Markdown file is the source of truth, and it's human-readable.

Plain Text = Future-Proof

Here's the deeper principle: plain text is the most durable format ever created.

A .txt file created in 1985 is readable on today's computers. A Microsoft Word file from 1995? Probably requires an old version of Office to open reliably. A Evernote export from 2012? Good luck making sense of it.

Plain text has no version number, no proprietary codecs, no dependencies. A text editor from any era can read it. This is why developers prefer plain text for code. This is why Unix systems use plain text for configuration. This is why long-term archivists recommend plain text for important records.

When you store your second brain in Markdown:

• Your great-grandchildren can read your notes: No obsolescence. No "this format is no longer supported."
• You can use any tool: Edit in Obsidian, VSCode, Vim, Sublime, cat, or grep. The notes don't care.
• Your data is secure: No cloud accounts, no authentication, no servers needed. Your files are yours alone.
• You can process notes with any programming language: Python script to extract all notes tagged #philosophy? Write a 10-line script. Impossible in proprietary systems.

This durability compounds over decades. A vault of notes is a long-term investment in yourself. Choosing Markdown is choosing an investment that will outlive any particular tool.

Version Control & Git Integration

Another powerful consequence of using plain-text Markdown: you can version control your vault with Git.

Git is a system designed for tracking changes to text files. Developers use it to collaborate and maintain history. With Obsidian, you can use Git for your vault via the Obsidian Git plugin:

cd /path/to/obsidian-vault
git init
git add .
git commit -m "Initial vault commit"

With Obsidian Git plugin installed, you can automate this process—commits and pushes happen automatically on a schedule you choose. Now every change to every note is tracked. You can:

• See the history of any note: When did I write this? How has my thinking evolved?
• Revert mistakes: Accidentally deleted an important note? Restore it from Git history.
• Sync across devices: Use Git to sync your vault across computers without relying on a cloud service.
• Collaborate: Share a vault with colleagues using Git—true collaboration without cloud dependency.
• Back up reliably: Push your vault to GitHub (private repository) for backup.

This is a feature that cloud-first apps can't match. Notion can't be version-controlled because it's not plain text. OneNote can't be Git-synced. But Obsidian? Your entire intellectual history is a Git repository.

Try this with a closed-source app. You can't.

Interoperability: Edit Anywhere

Because your notes are plain-text files, you can edit them anywhere.

• Open a note in Obsidian on your Mac
• Edit the same note in VSCode on your Linux machine
• Quickly jot down an idea in a text editor on your iPad
• Search through your notes using grep on your terminal

The files don't care which tool opened them. This is radical freedom compared to locked ecosystems:

With Notion, you must use Notion's interface. With OneNote, you need Microsoft's application. With Obsidian, you have complete freedom.

I've used this in practical scenarios:

• Quick edits on the terminal: echo "## New thought" >> note.md
• Bulk search and replace: sed -i 's/old-tag/new-tag/g' *.md
• Building tools: Custom Python scripts to extract data from my vault for analysis
• Export and conversion: Converting Markdown to PDF, HTML, or other formats using standard tools

This flexibility is impossible with proprietary formats. You're not locked into a single tool. Your notes are resources that can be used by any tool.

The Obsidian Vault is Just a Folder

Obsidian doesn't hide your data. Your vault is just a folder of files on your computer. No special database. No binary blobs. Just .md files that you can see in Finder or Terminal.

This simplicity has profound implications:

Backup: Copy the folder to an external drive. Done. No complex export process.

Sync: Use Dropbox, iCloud Drive, OneDrive, or the free Obsidian Git plugin for Git-based sync. Any file syncing method works. If you want automatic Git commits and pushes without configuration, the Obsidian Git plugin handles it seamlessly.

Migrate: Move your entire vault to another computer by copying a folder.

Transparency: If Obsidian disappeared tomorrow, you'd still have your notes. They're just files.

Customize: You can write scripts to process your vault. Add metadata, generate statistics, extract data—the possibilities are endless.

Compare this to Evernote, where exporting your notes is a slow, painful process that often loses formatting. Compare to Notion, where export is glacially slow and imperfect.

Obsidian's approach is fundamentally different because it's based on a principle: your data is your data, and it should be in a format you control.

Markdown's Growing Adoption

Markdown has become the standard for technical and knowledge-work communities:

• GitHub uses Markdown for READMEs and documentation
• Reddit uses Markdown for comments and posts
• Discord uses Markdown for formatting messages
• Dev.to uses Markdown for articles
• Hugo, Jekyll, and Gatsby (popular static site generators) use Markdown for content

This isn't coincidence. Markdown won because it's simple, readable, and universal. Its adoption means:

• Your notes are compatible with any modern system: If you ever want to publish your notes on a blog, convert them to HTML, or share them on GitHub, Markdown is a single conversion away.
• Tooling is abundant: Markdown processors, syntax highlighters, and converters are everywhere because the format is open and widely used.
• Community is strong: There are thousands of tools built around Markdown because so many people value its principles.

Markdown Limitations (And Why They Don't Matter)

Markdown isn't perfect. Some limitations:

• Limited formatting: Markdown doesn't support complex layouts or styling (though some extensions add this)
• No embedded media natively: You can link to images, but Markdown doesn't embed them directly in the syntax
• No tables in base Markdown: Though extended Markdown (like GitHub Flavored Markdown) adds this

These feel like limitations, but they're actually features. The simplicity of Markdown is its strength. It refuses to let you create beautiful-but-unusable documents. It forces clarity.

And Obsidian extends Markdown with:

• Wikilinks: [[Note Name]] for internal linking
• Embed syntax: ![[Image.png]] to embed images and notes
• YAML frontmatter: Metadata at the top of files
• Math support: LaTeX equations
• Code blocks: With syntax highlighting

These extensions remain compatible with plain Markdown. A tool that doesn't understand [[Wikilink]] will simply display it as text. Nothing breaks.

Long-Term Thinking

Choosing Markdown for a second brain is choosing long-term thinking over short-term convenience.

Notion is convenient. Its interface is beautiful and features are abundant. But you're betting that:

• Notion will always exist
• Notion's format will remain stable
• Notion will always allow exports
• You'll always want to use Notion

These are risky bets across decades.

Markdown bets on:

• Open standards
• Human readability
• Portability
• Independence

When you store your life's knowledge in Markdown, you're building something that will outlast any single company or tool.

Making the Switch

If you're currently in Notion, OneNote, or Evernote, moving to Obsidian isn't just about the app. It's about choosing a fundamentally different philosophy:

• Data ownership: Your notes are files on your computer
• Durability: Plain text lasts forever
• Flexibility: Use any tool you want
• Privacy: No cloud dependency
• Accessibility: Open your notes fifty years from now without any special software

This is why smart knowledge workers choose Obsidian. Not because it's flashy. Because it's built on principles that endure.

Explore the full Obsidian cluster:

• Obsidian: The Second Brain That Changed My Note-Taking — The transformation story
• Why Obsidian Wins: The Advantages You Can't Ignore — Architecture and design philosophy
• From Notes to Knowledge: How Obsidian Unlocked My Second Brain — Atomic notes and Zettelkasten
• Supercharge Obsidian: Top Community Plugins That Changed My Workflow — Tools to amplify your vault
• Building My Knowledge Hub: From Chaos to Organized Insight — Structure and discovery methods