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

Obsidian vs Capacities: Quick Answer

The Obsidian vs Capacities question is whether you want a plain-text vault or a typed object graph. Obsidian gives you raw parts and asks you to build the system yourself.

Capacities gives you named object types from day one. Choose between them based on whether long-term file ownership and customization matter more than built-in structure and managed sync.

How We Tested

For the broader test across eight second-brain apps, see our second-brain apps guide. It covers load, lock-in, and graph density.

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

Disclosure: we make Atlas, one of the products discussed in this post. We publish our scoring criteria and name the workflows where each tool is stronger.

Feature Comparison

Pricing

Obsidian is free without limits for personal use per its pricing page in May 2026. Add-ons are paid. Sync costs $4/user/month annual or $5/month monthly. Publish costs $8/site/month annual or $10/month monthly.

Work use needs a $50/user/year license, and Catalyst is a one-time $25 tier. The free tier has no feature limits, which is rare in 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 tier is the unusual move. Pay once and keep updates for years. Only a few indie PKM tools ship that model.

The free vault wins for solo users who do not need first-party sync. Pro is the cheaper all-in tier when you want sync, AI, and mobile built in. If you want simpler defaults, see simpler Obsidian alternatives.

Data Model

Obsidian stores notes as plain Markdown files. Structure comes from folders, tags, front matter, and links, so you design the system. Mueller & Oppenheimer 2014 framed a related problem as "external storage." Notes reworked by the writer beat notes that merely sit in a database. Markdown's friction can help because you must choose tag names and link targets.

Capacities uses typed objects. Every note has a type, such as Page, Person, Book, Idea, Place, Project, Quote, Image, or Tweet. Each type carries its own fields. The system gives you rails, which removes the blank-page problem many vault users cite.

Official Capacities product page screenshot showing the app's object graph view.

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

Daily Notes and Backlinks

Capacities ships daily notes as a core feature. Backlinks and two-way links are first-class. Obsidian has Daily Notes as a default plugin. Backlinks and two-way links are also first-class there.

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

Plugins and Extensibility

Obsidian has 2,000+ community plugins. Common picks include Dataview, drawing tools, templates, AI search, calendars, and mind maps.

Karpicke & Roediger's 2008 research on retrieval practice maps well onto Dataview. A query such as "show notes touched in the last 14 days" brings old material back at a useful review point.

Capacities has no plugin system. It offers built-in features only, and the team ships updates. The closed system means fewer add-ons break during upgrades. That tradeoff matters to users who left Obsidian to escape plugin churn.

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

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.

The vault app also has iOS and Android apps, but sync requires Obsidian Sync at $4/user/month annually or a service such as iCloud Drive, Syncthing, or Git.

A 1,000-note vault opens in 2-4 seconds on a 2024 iPhone per public benchmarks. Large 10,000-note vaults can take 6-8 seconds, creating friction for people who switch devices often.

Capacities wins for mobile users who want zero sync setup. Apple-only Markdown writers should also see Bear vs Obsidian.

AI Features

Capacities Pro includes an AI Assistant for summaries, rewrites, and Q&A inside the app. Obsidian reaches AI through Smart Connections, Copilot, or local models through Ollama. The vault route is more flexible but needs more setup.

The Ahrefs study of 600,000 pages shows how common AI-assisted work has become. The practical choice is built-in convenience in Capacities or configurable AI in Obsidian.

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.

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 Web Clipper clips pages to Markdown. The output is a .md file in your vault, so clips remain portable and work with the rest of the vault.

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

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. Markdown does the long-term work.

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

Obsidian wins portability. For the source-synthesis layer that sits above either tool, compare Atlas with Capacities or review the broader smart notes app field.

Use Cases for Each Tool

When to Choose Obsidian

You want plain-text data ownership. You build a long-term knowledge base and worry about lock-in. You want plugins for queries, drawing, and AI search. You're fine with upfront system design. You're on Linux or want offline-first behavior.

When to Choose Capacities

You want structure without plugin tinkering and think in typed objects such as Books, People, Projects, and Concepts. You want daily notes, backlinks, mobile sync, and an AI assistant included, and you accept cloud-first storage.

Choose Capacities when reaching a working system in the first session matters more than deep customization. If your notes later turn into research PDFs, add a separate source-grounded layer only when cited answers become necessary.

When to Choose Atlas

Neither does AI synthesis with source citations well at scale. Atlas turns notes, PDFs, and research into a mind map. It answers cross-source questions with citations to the exact passage. Pair Atlas with Obsidian by reading your vault, or export Markdown from Capacities.

Comparison Table

Read this table as the short version. Choose Obsidian when ownership and plugins matter most. Choose Capacities when built-in structure and sync matter most.

Table 1: Feature comparison for Obsidian and Capacities.

Costs, Privacy, and Daily Operation

Three-Year Cost in Real Numbers

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

Table 2: Three-year cost totals for common Obsidian and Capacities setups.

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 five years, or about $80/year.

Casual personal use can be free in both tools. For work use, Obsidian's commercial fee can surprise teams because it often appears after staff have already chosen Obsidian individually.

Privacy and Data Handling

Table 3: Privacy and data rules for both apps.

Local files give the vault app the strictest privacy stance: by default, data never leaves your device. With Sync, notes are locked with a passphrase you hold, so the servers cannot read them. Capacities is cloud-first and stores data in the EU, which helps European users with GDPR needs. For medical, legal, or journalism work, local files without Sync are the strongest answer.

Migration Between the Two

Moving from the vault app to the object app starts with Markdown import. Capacities tries to map folders to object types, and wikilinks usually convert to backlinks. Dataview queries do not transfer because Capacities has its own query language.

A 1,000-note vault takes 3-6 hours to clean up after import. Plugin-heavy features such as Templater, QuickAdd, and custom Dataviews have no direct match.

Moving from the object app to the vault app starts with JSON export. Obsidian does not import JSON on its own, so you need a script or community template to turn each object type into a Markdown file with front matter. The typed-object structure becomes Obsidian properties.

A 5,000-object database takes 8-15 hours to move cleanly. The Capacities export documentation says the JSON export is complete, but the conversion work remains 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 and link to project notes with [[wikilinks]]. At lunch, you tweak a Templater snippet. In the afternoon, a Dataview query surfaces open action items. Then you save the vault to Git for version history. The pattern is do-it-yourself and deeply 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. You link it to a Project object with the relation picker. Capacities AI summarizes the meeting on the right panel. Then you review recent activity across object types. The pattern is plug-and-play and more 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

Running both is rare because each tool wants to be the canonical knowledge base, and duplicating notes wastes time. The combination makes sense only when Capacities handles short-term projects and Obsidian holds the long-term archive.

In that setup, finished projects move from the object app into the Markdown vault once a month. Most users should pick one system and commit to it.

Plugin Ecosystem Reality

Obsidian's community plugin store has 1,500+ plugins. They cover queries, drawing canvases, and AI links to many LLM providers. The downside is plugin sprawl. A vault with 30 plugins takes 5-10 seconds to open and can develop odd bugs. A fast setup usually keeps only the 5-10 plugins you use weekly.

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 must configure iCloud Drive, Google Drive, Dropbox, or Syncthing themselves.

Each free option has failure modes, from iCloud delays to Dropbox conflict files when two devices edit the same note. Obsidian Sync is the smoother path and encrypts notes before upload.

The object app has cloud sync, so no setup is required. Log in on the phone and the workspace appears. The mobile app is strong for capture but does not expose every desktop feature. Some object controls remain desktop-only. For users whose capture moment is on the phone, Capacities is the lower-friction path.

Conflict handling exposes the tradeoff. Obsidian's third-party sync paths are the most likely place for conflicts to appear, so close the vault on one device before editing on another or use Obsidian Sync.

Capacities resolves conflicts on its servers and rarely shows them to the user. The tradeoff is that you cannot always tell which version won when two devices edit the same field within seconds.

Which App Should You Choose?

Choose Obsidian if you want plain-text data ownership, full offline access, and plugins that let you build your own system. Choose Capacities if you want a typed object graph, managed sync, and AI without plugin setup.

Choose Atlas only for the separate job of asking source-grounded questions across research documents and tracing answers to cited passages.