Obsidian vs Zed, Neovim or VS Code for Markdown notes
Checked on 2026-09-03 for Obsidian pricing and platform support, and on 2026-09-11 for its plugin marketplace. Obsidian feature rows were last checked in May 2026. IWE facts checked against IWE 0.23.0.
Obsidian and a code editor can open the same folder of Markdown files. The question is which one you want to write in. This page is for you if you already spend your day in Zed, Neovim, VS Code or Helix and wonder whether your notes belong there too.
The short answer
Pick Obsidian if you want one application that does everything, with mobile apps, a graph view, canvas, a web clipper and thousands of community plugins. If you do not already live in a text editor, Obsidian is very likely the right choice.
Pick your code editor with IWE if you already write code in Zed, Neovim, VS Code or Helix and want your notes to work like code: follow links, find what links here, rename with every reference updated, and restructure notes with code actions. Your AI agent works on the same folder through the iwe CLI and MCP server.
You do not have to choose once. Your notes stay a folder of .md files, so Obsidian, your editor and IWE can all open the same folder.
Obsidian vs Zed
In Zed, the notes features come from the IWE extension for Zed:
F12follows a link andShift+F12lists every note that links to the current one.Cmd+Tfinds a note by heading.Cmd+.opens code actions that extract a section into its own note or inline it back.F2renames a note and updates every link to it.- Format on save keeps titles and link text consistent.
The extension installs from Zed Extensions and downloads the iwes language server on first start. It supports macOS and Linux; Windows support is planned. Obsidian, by contrast, has its own editor, mobile apps, and a graph view.
Obsidian vs Neovim, VS Code and Helix
The same language server runs in each editor, so the features are the same and only the keys differ:
| Editor | How IWE installs | Follow link | Backlinks |
|---|---|---|---|
| VS Code | Extension from the Marketplace | F12 | Shift+F12 |
| Neovim | iwe.nvim plugin, with Telescope pickers | gd | gr |
| Zed | Extension from Zed Extensions | F12 | Shift+F12 |
| Helix | Plain LSP configuration, no plugin | gd | gr |
Any other editor with Language Server Protocol support works too, configured by hand.
Feature comparison
| Feature | Obsidian | Code editor with IWE |
|---|---|---|
| Where you write | Obsidian’s own editor | The editor you already use |
| Cost | Free for personal use; Sync $4–5/month, Publish $8–10/month, commercial use $50/user/year | Free and open source |
| Plugins | 4,000+ community plugins | No plugin ecosystem; extend through LSP features, the CLI and MCP tools |
| Preview | Built in | Not part of IWE; whatever your editor or its plugins provide |
| Graph view | Interactive, with custom styling | Dot export from the CLI |
| Canvas | Native infinite canvas | Not supported |
| Web clipper | Native browser extension | Not supported |
| Mobile | Native apps with sync | Desktop and terminal only |
| Sync | Obsidian Sync (paid) or your own Git setup | Git, with any hosting |
| Restructuring | Manual linking and organization | Extract and inline sections, section to list, attach, with links rewritten |
| Queries | Bases (typed database views) and the Dataview plugin | MongoDB-style YAML queries over frontmatter and links |
| Bulk edits | No batch operations | iwe update and iwe delete across the folder, filtered by a query |
| Formatting | Basic; plugins for more | Normalization of headers, lists and link titles on save |
| AI agents | Through third-party plugins | Built-in MCP server and CLI for Claude Code, Codex and other agents |
| Performance | Electron app; can be slower with large vaults | Rust; 20,000 files in under a second |
| Learning curve | GUI, works out of the box | Needs a terminal, a binary and editor setup |
What the editor setup gains
- Your editor’s keys, themes and splits. Notes open in the same tool as your code, with the same shortcuts.
- Notes that refactor like code. A code action moves a section into its own note and leaves a link behind, or merges a linked note back in.
- One folder for you and your agent. Claude Code, Codex or any MCP client searches the notes, pulls a note with its surrounding structure into context, and makes guarded edits. Agent tooling ships with IWE, not through community plugins.
- Queries and bulk edits from the command line. The same query language works in the CLI and the MCP server.
- No subscription. Sync is whatever Git hosting you already use.
What it lacks next to Obsidian
Be clear about what you give up:
- No plugin ecosystem. Obsidian has thousands of community plugins. IWE has none of its own; it extends through LSP features, the CLI and MCP tools.
- No preview from IWE. IWE does not render Markdown. You get whatever preview your editor offers, or none; in Neovim, the guide suggests render-markdown.nvim for in-buffer rendering.
- No mobile apps, canvas, web clipper or interactive graph view. Obsidian wins these outright.
- Slower first run. IWE is a binary, an editor configuration and a folder of Markdown. If you have never used a language server, Obsidian will be working before IWE is configured.
- Some Obsidian syntax resolves differently. IWE reads
[[wiki]]and[[wiki|piped]]links, but resolves them to whole notes: links to a heading or a^blockpoint at the note, not the section. Inline#tagsare not indexed, and notes have no aliases. - Weaker daily notes. Templates through attach, with no natural-language dates.
Bring your Obsidian vault
An Obsidian vault is a folder of .md files, so it already works as an IWE workspace. Run iwe init in the folder to write .iwe/config.toml, fitted to the conventions the notes already use. Nothing is imported or converted, and Obsidian keeps working on the same files.
Want an app, not an editor?
iWe for Mac is a free native app for the same kind of folder Obsidian uses. It has a graph view, full-text search, search pages that filter notes by properties and links, and Claude Code or Codex working inside the document. It needs macOS 15 or later, and your editor and the iwe CLI keep reading the same files.
Next steps
- Get started to install IWE
- Editor setup for VS Code, Neovim, Zed and Helix
- How IWE compares for the full, sourced comparison with Obsidian and other tools
- IWE vs markdown-oxide vs Marksman if you are choosing a Markdown language server