Obsidian vs Capacities (2026): Object-Based Notes Guide

Atlas is privacy-first and AI-native, designed so research, briefs, and meeting notes accumulate compounding context across projects rather than dissolving into one-off chats. Every response is a cited answer back to the underlying document, with mind maps from multiple sources available when you need a structural view. $20/mo Pro. Get started.

The Obsidian vs Capacities question is whether you want a programmable plain-text vault or a typed object graph. Obsidian gives you raw materials and asks you to build your system. Capacities gives you a pre-built system with named object types. This guide tests both and tells you which fits which workflow.

How We Tested

For the deeper framework, Cognitive Load, Vendor Lock-in, and Knowledge-Graph Density, applied across eight leading second-brain apps, see our second-brain apps guide.

Tested over 4 weeks on macOS Sonoma, iPadOS 18, iOS 18, Windows 11. Obsidian free with Sync. Capacities Pro subscription. Workloads: 200-note research vault, daily-notes journal, Books + Papers + Authors typed objects, weekly-review template.

Disclosure: we make Atlas, one of the products discussed in this post. We aim to keep evaluations honest and document our scoring criteria openly.

1. Pricing

Obsidian is free without limits for personal use per its pricing page in May 2026. Optional add-ons include Sync at $4/user/month annual or $5/month monthly, Publish at $8/site/month annual or $10/month monthly, a $50/user/year commercial license, and a $25 one-time Catalyst tier. The free tier has no feature limits, which is unusual across PKM tools.

Capacities has a limited free tier. Pro is $9.99/month monthly or $7.99/month annual per public listings in May 2026. The Believer lifetime tier is the unusual move: pay once and keep updates forever, a model only a handful of indie PKM tools ship.

Obsidian free wins for solo users who do not need first-party sync. Capacities Pro is the cheaper all-in tier when you want sync, AI, and mobile built in. Anyone weighing Obsidian against simpler defaults should also see obsidian alternatives simpler.

2. Data Model

Obsidian stores plain-text Markdown files. Structure comes from folders, tags, frontmatter, and links, so the user designs the system. Mueller & Oppenheimer 2014 framed a related problem as "external storage": notes re-encoded by the writer outperform notes that merely sit in a database. Markdown's friction, including choosing tag names and link targets, can drive that encoding.

Capacities uses typed objects. Every note has a type, such as Page, Person, Book, Idea, Place, Project, Quote, Image, or Tweet, with structured properties per type. The system designs you, which removes the blank-page paralysis Obsidian users often cite.

Obsidian wins flexibility and ownership. Capacities wins when you want structure without designing it yourself.

3. Daily Notes and Backlinks

Capacities ships daily notes as a core feature, with bidirectional links and backlinks treated as first-class. Obsidian has Daily Notes as a default plugin, and bidirectional links plus backlinks are also first-class.

The feature result is a tie. Capacities is set up for you. Obsidian needs the plugin enabled.

4. Plugins and Extensibility

Obsidian has 2,000+ community plugins, including Dataview, Excalidraw, Templater, Smart Connections, Calendar, and Mind Map. Karpicke & Roediger 2008 research on retrieval practice maps well onto Dataview queries because a prompt like "show notes touched in the last 14 days" surfaces material at a spaced-review window.

Capacities has no plugin system. It offers built-in features only, and the team ships updates. The closed system means fewer dependencies break across upgrades, a tradeoff cited by users who left Obsidian to escape plugin churn.

Obsidian wins extensibility for power users. For a Notion-vs-Obsidian framing of the same trade-off, see Notion vs Obsidian.

5. Mobile

Capacities has mobile apps for iOS and Android. It is cloud-synced and works offline once content is loaded. Cold start is around 2-3 seconds on a 2024 iPhone per user reports.

Obsidian also has iOS and Android apps, but sync requires Obsidian Sync at $4/user/month annual, iCloud Drive, Syncthing, or Git. A 1,000-note vault opens in 2-4 seconds on a 2024 iPhone per public benchmarks. Large 10K-note vaults push that to 6-8 seconds, which Microsoft Work Trend Index 2024 would frame as a productivity tax across workers using several devices weekly.

Capacities wins for mobile users who want zero sync setup. For Apple-only Markdown writers comparing mobile-polished options, Bear vs Obsidian covers that axis.

6. AI Features

Capacities Pro includes an AI Assistant for summaries, rewrites, and Q&A inside the app. Obsidian reaches AI through Smart Connections, Copilot for Obsidian, or local LLM workflows through Ollama. Obsidian is more flexible but needs more setup. The Ahrefs 600K-page AI-content study makes semantic-search AI feel like a baseline expectation in 2026 rather than a premium extra.

Capacities wins out of the box. Obsidian wins on flexibility and bring-your-own-key cost. For an Evernote-flavored take with built-in AI Search, Obsidian vs Evernote tests that path.

7. Web Clipper

Capacities' browser extension clips into typed objects. A clipped tweet becomes a Tweet object, and a clipped book can auto-fill author, year, and ISBN where Capacities detects them. That removes friction at capture time.

Obsidian's official Web Clipper, launched in 2024, clips to Markdown. The output is a .md file in your vault, which preserves ownership and keeps capture compatible with the rest of the vault.

Capacities wins the typed-clipping workflow. Obsidian wins on Markdown ownership of clips.

8. Data Portability

Obsidian stores Markdown files in a folder. They open in any editor and migrate freely. Public reports indicate that vaults from 2020 still open cleanly in 2026 builds, with Markdown stability doing the architectural work.

Capacities exports Markdown with frontmatter. Round-trip works for typed objects, but views and queries do not transfer. A 1,000-note migration plus query rebuild in Obsidian Dataview takes a few hours per user reports.

Obsidian wins portability. For a smart-notes synthesis layer that sits above either tool, see smart notes app.

When to Pick Obsidian

You want plain-text data ownership. You build a long-term knowledge base and worry about tool lock-in. You want a plugin ecosystem (Dataview, Excalidraw, Smart Connections). You're fine with upfront system design. You're on Linux or want offline-first behavior.

When to Pick Capacities

You want structure without plugin tinkering. You think in typed objects (Books, People, Projects, Concepts). You want daily notes, backlinks, mobile sync, and AI Assistant all included. You're fine with cloud-first storage. You want to be productive in 30 minutes, not 30 hours.

When to Pick Atlas

Neither does AI synthesis with source citations well at scale. Atlas turns notes, PDFs, and research into a navigable mind map and answers cross-source questions with citations to the specific passage. Pair Atlas with Obsidian (reads your vault) or Capacities (export Markdown to Atlas). $20/month Pro. Try Atlas.

Comparison Table

Three-Year Cost in Real Numbers

Both apps have free tiers. Real cost depends on the add-ons.

Obsidian's pricing page lists Sync at $4/month, Publish at $8/month, and Commercial at $50/user/month. Capacities' pricing page lists Pro at $7.99/month and Believer at $399 for 5 years, or about $80/year. The honest cost picture is that casual personal use can be free in both tools. For commercial use, Obsidian's $50/user/month is the line item that surprises companies that picked Obsidian for individual employees and then had to retroactively license it.

Privacy and Data Handling

Obsidian's posture is the strictest available: by default the data never leaves your device. Obsidian Sync adds end-to-end encryption with a passphrase you hold, so Obsidian's servers cannot read your notes. Capacities is cloud-first with EU data residency, which is a meaningful advantage for European users with GDPR-driven preferences. For users with the highest privacy bar in medical, legal, or journalism workflows, Obsidian without Sync is the strongest answer in this category.

Migration Between the Two

Moving from Obsidian to Capacities starts with Markdown import. Capacities tries to map folders to object types, and wikilinks usually convert to Capacities backlinks. Dataview queries do not transfer because Capacities has its own query language. A 1,000-note Obsidian vault takes 3-6 hours to clean up after import. Most plugin-driven features such as Templater, QuickAdd, and custom Dataviews have no direct Capacities equivalent.

Moving from Capacities to Obsidian starts with JSON export. Obsidian does not import JSON natively, so you need a script or community template to convert each Capacities object type into a Markdown file with frontmatter. The typed-object structure becomes Obsidian frontmatter properties. A 5,000-object Capacities database takes 8-15 hours to migrate cleanly. Per the Capacities export documentation, the JSON is complete but the import-side work is yours.

Real-World Workflows Compared

An Obsidian day starts in the vault. Today's daily note auto-creates from the Daily Notes plugin. You capture during meetings, link to project notes with [[wikilinks]], tweak a Templater snippet at lunch, run a Dataview query in the afternoon to surface open action items, then commit the vault to Git for version history. The pattern is do-it-yourself and infinitely customizable.

A Capacities day starts with today's daily note and the typed-object graph in the sidebar. You capture a meeting note as a Meeting object, link it to a Project object with the typed-relation picker, let Capacities AI summarize the meeting on the right panel, then review the dashboard of recent activity across object types. The pattern is plug-and-play and structurally constrained.

The two apps answer different questions. Obsidian answers "what system do I want to build?" Capacities answers "what does the system want me to capture?"

When You Should Run Both

Rare in practice. Both tools want to be the canonical knowledge base, and dual-writing notes wastes time. The only realistic split: Capacities for short-term project work (its typed objects accelerate setup) and Obsidian for the long-term reference vault (its plain-Markdown longevity protects 10-year archives). A monthly transfer ritual moves completed projects from Capacities into Obsidian. Most users pick one and commit.

Plugin Ecosystem Reality

Obsidian's community plugin store has 1,500+ plugins, covering everything from advanced Dataview queries to Excalidraw-style drawing canvases to AI integrations with any LLM provider. The downside is plugin sprawl. A vault with 30 plugins takes 5-10 seconds to open and can develop obscure interaction bugs. The discipline of installing only the 5-10 plugins you actually use is the difference between a fast Obsidian setup and a slow one.

Capacities has no third-party plugin ecosystem. The team ships features in batches, and users request features through the Capacities feedback portal. The advantage is no plugin-induced slowdown or breakage. The disadvantage is that features the team has not built do not exist. The bet is on the company's roadmap rather than on a community.

Mobile and Sync Reality

Obsidian mobile is full-featured on iOS and Android, with the same plugins, vault structure, and Markdown editor. The catch is sync. Without Obsidian Sync, users wire up iCloud Drive, Google Drive, Dropbox, or Syncthing themselves. Each free option has failure modes, from iCloud delays to Dropbox conflict-suffix files when two devices edit the same note. Obsidian Sync is the friction-free path and uses end-to-end encryption.

Capacities mobile has cloud-native sync, so no setup is required. Log in on the phone and the workspace appears. The mobile app is well designed for capture but does not expose every desktop feature, with some advanced object operations remaining desktop-only. For users whose capture moment is on the phone, Capacities is the lower-friction path.

Conflict resolution is where the two philosophies show. Obsidian's third-party sync paths are the most likely place for conflicts to appear. The standard advice is to close the vault on one device before editing on another, or to use Obsidian Sync. Capacities resolves conflicts server-side and rarely surfaces them to the user, with the tradeoff that you cannot always tell which version won if two devices edited the same field within seconds.

Final Take

Obsidian wins for users who want plain-text, plain-folder data ownership and a plugin ecosystem to extend the tool. Capacities wins for users who want a typed object graph out of the box with sync and AI included. The split is taste: build your own system or use someone else's. For AI-grounded synthesis with source citations across either tool's content, Atlas beats both.