Developers have note-taking needs that general-purpose advice ignores: notes arrive from a terminal as often as from a keyboard-in-a-GUI, they contain code that must survive formatting, and increasingly they need to be readable by AI tools as well as humans. This guide lays out the criteria that actually separate the options, then walks through the main categories and where each fits.
The criteria that matter
Before any tool names, the questions worth asking:
Capture friction. How many seconds and decisions between "thought" and "saved"? Can you capture from a terminal? From a browser without switching apps?
Code handling. Code blocks with sensible formatting, markdown support, paste that doesn't mangle indentation.
Retrieval. Keyword search only, or search by meaning? Does finding an old note depend on how well you filed it?
AI access. Can assistants like Claude or Cursor read and write your notes (typically via MCP), or is the vault opaque to them?
Lock-in. Can you export everything to markdown or plain text, today, without asking support?
Sync and platforms. Where do notes live, and which of your machines can reach them?
No tool wins on all six. The categories below make different trades.
Local-first markdown: Obsidian and kin
Obsidian stores notes as plain markdown files in a local folder, with a large plugin ecosystem and first-class linking between notes. The files-on-disk model is the strongest possible answer to lock-in — your vault is a folder you can grep, back up, and edit with any tool — and it works offline by definition. The trade-offs are the mirror image: sync across devices is an add-on you configure, capture from outside the app (a terminal, a browser bar) requires plugins or scripting, and search is fundamentally text matching unless you extend it.
Choose this category if data sovereignty is your top criterion and you enjoy assembling your own workflow from plugins.
The workspace suites: Notion and friends
Notion is a workspace first and a notes tool second: databases, docs, wikis, and project views in one place, with strong team collaboration. For structured team knowledge — specs, onboarding docs, project trackers — it is a reasonable center of gravity. As a personal capture tool for developers it is heavier: capture means opening the app and choosing where the note lives, and the block model is built for composing pages, not for two-second thoughts. Many teams pair a workspace suite for documents with a lighter tool for personal capture.
Choose this category when the primary artifact is team documentation rather than personal working notes.
The default apps: Apple Notes, Google Keep
The built-in options deserve honest credit: zero setup, reliable sync within their ecosystem, and good enough capture on their home platforms. Their limits for developers are equally clear — weak or absent code formatting, platform boundaries (Apple Notes outside Apple hardware is painful), export paths that range from awkward to lossy, and no terminal or AI-tool access. They are fine as a scratch buffer; they struggle as a system of record for technical notes.
Capture-first vaults: Notez
The newest category optimizes the front of the funnel: making capture nearly free from wherever a developer already is, with retrieval handled by search that understands meaning.
Notez is built as one vault with four capture surfaces. Type notez.dev/your thought into any browser address bar and the URL becomes the note. A 3 MB CLI (notez "...", with piped stdin support) captures from any shell on macOS, Linux, or Windows — including over SSH. AI tools connect over MCP, so Claude, Cursor, or Windsurf can read and write the same vault, giving your assistants persistent, shared memory. And the web app provides the full editor — blocks, code, tags, kanban boards, custom properties, sub-notes, and [[ links with synced backlinks — plus a Mac app that runs the web app in its own window.
Retrieval is embeddings-based: search matches meaning ("that caching idea" finds the memoization note), and an ask-your-notes chat answers questions across the vault with sources. On lock-in, any member can export the whole workspace at any time as a .zip of markdown files with attachments, which opens as an Obsidian vault. The free plan needs no credit card; paid plans ($4.99 and $9.99 a month) raise storage and AI allowances.
The trade-off relative to local-first tools is the obvious one: notes live in a service, not a folder on your disk — mitigated, but not eliminated, by the markdown exit.
Choose this category if your notes die at the capture step today, you work across terminal and browser, or you want your AI tools reading and writing the same notes you do.
Honorable mentions
Simplenote — free, fast, plain text, great as a minimal cross-platform scratchpad; minimal is also its ceiling.
Joplin — open-source, markdown, self-hostable sync; a solid Obsidian alternative with a more traditional app feel.
nb / plain files + git — for maximal-control users, notes as text in a repo is a legitimate system; you own every byte and build every feature yourself.
How to decide
Skip the feature matrices and ask two questions. First: where do your notes currently die? If they die at capture (thoughts not written down), weight capture friction above all and look at capture-first tools or the built-ins. If they die at retrieval (written but never found), weight search and linking — semantic search or a disciplined link graph. If they die at handoff (you have notes, your team or your AI tools can't use them), weight collaboration or MCP access.
Second: what happens when you leave? Whatever you pick, confirm the full-export path exists before you invest a year of thinking in it.
Then pick one tool and run it for a month with real notes. A month of actual captures will tell you more than any comparison post — including this one.
Continue reading
Lightweight Notion Alternatives for Fast Note Capture — Simplenote, Apple Notes, Obsidian and Notez compared on one job, saving a two-second thought, plus a setup that keeps Notion as the library.
Moving in from Notion or Evernote — what a Notion or Evernote export keeps on the way into Notez, the size limits, and how to undo an import.
How to Build a Note-Taking System as a Developer — what to capture as a developer, where to keep it, and the habits that let you find a note months later.