Atlas vs Capacities (2026): An In-Depth Research Comparison

Atlas is a visual research workspace for people whose work depends on a body of papers. That may be a thesis, a treatment choice, a purchase teardown, or a literature review.

Capacities is an object-based note app for personal knowledge management, or PKM. Instead of pages, you create typed objects: notes, ideas, people, and books. Those objects link to daily notes and a graph view.

Both tools touch a researcher's day. The wedge is what happens after the first answer.

Atlas can generate a Knowledge Map for each paper, an editable map of its main ideas and labelled connections. It places a project's sources and notes on a Semantic Map. For how document-based maps compare across tools, see mind maps from documents.

Atlas answers carry citations. Each citation's hover card shows the source passage and a short reason the passage supports the claim. Sources, notes, maps, and chats share context inside the active project.

Capacities is the better PKM database. Its typed objects and daily notes are strong when you want more structure than a flat note graph. If you need to trust the answers for a thesis, treatment plan, brief, or hiring call, Atlas earns the comparison.

Quick verdict: Atlas or Capacities?

For this 2026 update, we used one rule: start from the job, then ask which tool owns it. Atlas wins when the job is reading, mapping, citing, and revisiting a source set inside one project.

Capacities wins when the job is keeping typed PKM objects across daily notes, people, books, projects, and recurring records.

Decision criteria

Use the job you need to complete as the deciding factor. These 4 criteria expose the practical boundary between the products:

• Choose by source proof when an answer must trace back to a passage.
• Choose by workspace structure when typed objects and custom properties organize the workspace.
• Choose by visual recovery when you need to revisit a paper's argument or a project's themes.
• Choose by context boundaries when one source set should support later questions without mixing in unrelated work.

Feature comparison table

Read each row as a pair: the bold label marks the side that leads on that need, and the other cell states what the second tool offers instead.

Table 1: Atlas leads on cited answers and paper maps; Capacities leads on typed objects, properties and saved queries.

How is Atlas different?

Atlas and Capacities overlap at the surface. Both help with reading and source review. They split on 3 points that decide whether the output can be shared and defended.

The screen below shows how Capacities keeps object types, a page outline, linked image and note objects, and their properties together.

Capacities's official product view shows typed objects and their links in one workspace. This is the structure side of the comparison; the table above describes Atlas source maps.

Visual maps for papers and projects

Atlas offers two kinds of visual map. A Knowledge Map is generated from one paper: an editable map of its main ideas with labelled connections between them. Open the paper itself when you need the exact wording.

A Semantic Map places a project's sources and notes in one view, with related items near one another. Search narrows the view, and Classify colors items by categories you describe.

This is how a large stack of papers stops being a folder and starts being a source set.

Capacities does not generate a map of each paper. It also does not color a project's items by categories you describe.

If you have spent an afternoon trying to recall a paper from three weeks ago, the Knowledge Map pays off first. Visual maps make a body of papers legible at a glance, and the Knowledge Map is the surface Atlas is built around.

Cited answers with justification

The hallucination problem in AI research tools includes a subtle failure: the model can put a source next to a claim that the passage does not prove.

Atlas attaches citations to its answers. Each citation's hover card shows the passage and a short reason the passage supports the claim, and you can open the source to read the passage in context. For more on checking citations, see Verifiable AI Research.

Capacities can link notes to sources, but it does not show a reason connecting a claim to a passage.

For casual Q&A the difference may not matter. For a thesis sentence, legal brief, or treatment note, it does. Check the passage behind a claim before you reuse it.

Project-scoped research context

Capacities connects typed objects across its PKM workspace. Atlas uses a narrower project boundary for research evidence.

Atlas keeps cited passages, notes, maps, chats, and sources together inside the project where they were created. Later questions in that project can use the same bounded corpus.

A separate project starts with its own evidence base. Add a source to each relevant project rather than expecting another project's notes or chat history to appear automatically.

Capacities is broader for reusable typed objects. Atlas is deeper for source-grounded synthesis inside a focused research project.

Comparing Atlas and Capacities: feature comparison

Both tools touch a researcher's day, but they live in different categories. Atlas covers paper maps, project maps, source-cited answers, and context within a source set.

Capacities covers typed objects, daily notes, and a graph view. Its object model is broader for general PKM. Atlas goes deeper at the source-proof layer.

The next sections cover paper maps, project maps, cited answers, source annotations, project context, and price. Each table includes at least one row where Capacities wins or ties.

Paper deconstruction (Knowledge Map)

The Knowledge Map is Atlas's per-paper surface. It generates an editable map of a paper's main ideas with labelled connections between them.

The map text summarizes the paper, so open the source when you need the original wording. You can edit nodes and export the map as PNG, JPG or SVG.

Table 2: Paper map rows beside Capacities object notes.

Good to know: The bottom row belongs to Capacities. Atlas does not ship that surface. The Knowledge Map's payoff is recovering a paper's main ideas weeks after you first read it.

Try Atlas: Use the Free plan (10 sources and 5 AI messages) to generate a Knowledge Map for one of your own papers. Review the cited-answer method before checking the result.

Project map (Semantic Map)

The Semantic Map is Atlas's per-project surface. It places the project's sources and notes in one interactive view.

Items with related text tend to appear near one another. Classify colors items by categories you describe, without uploading files again.

Table 3: Project map rows beside Capacities object links.

Good to know: Capacities's strength on that row is genuine. If your work depends on it, that's the boundary. The Semantic Map pays off when a large stack of papers stops being a folder. It becomes a corpus you can classify by new categories without re-reading.

Source-backed answers

Atlas citations pair a claim with its passage and a short reason the passage supports it.

You can open the cited source, read the passage, and check whether the reasoning holds.

The NotebookLM alternatives guide shows how this proof step differs from another source-chat workflow.

Table 4: Cited answer rows beside Capacities note templates.

Good to know: Both tools have a citation surface. Atlas also explains why a passage justifies a claim. For everyday Q&A that difference is easy to miss. For a thesis sentence or a brief paragraph, it determines whether you can audit the answer.

Reference lookup in uploaded papers

Atlas resolves the reference list of an uploaded paper. Hovering over an in-text citation shows the cited paper's title, authors and abstract.

When an open-access copy exists, the hover card links to it. You can see what a paper cites without leaving the document.

Table 5: Source note rows beside Capacities query exports.

Good to know: This feature resolves citations inside the paper you're reading. The hover card shows the cited paper's details, not the passage it cites. It is not web grounding.

Project-scoped context

Atlas keeps citations, notes, Knowledge Maps, Semantic Maps, and chats inside one project. A separate project starts with its own sources and context.

Table 6: Atlas project context beside Capacities object history.

Good to know: Atlas keeps one project's evidence together across sessions. Capacities has the broader reusable object graph, while separate Atlas projects preserve distinct evidence boundaries.

Price comparison

Atlas has a Free plan. It includes 10 sources and 5 AI messages. Atlas Plus costs US$20/month or US$192/year, and Atlas Pro costs US$40/month or US$384/year.

Plus includes hundreds of AI messages a month and up to 1,000 sources; Pro doubles Plus's AI usage and holds up to 10,000 sources. The Capacities pricing page should be checked before purchase because its packages can change.

Table 7: Atlas paid plan beside Capacities free and paid plans.

When to choose Atlas vs Capacities

Choose Atlas when a research answer must be checked against source passages. Choose Capacities when typed objects and daily notes are the main organizing system.

Keep both when general PKM and passage-level research proof matter in the same week. Move only the source-heavy project into Atlas.

• Want a generated map of each paper's main ideas? Go with Atlas. (Knowledge Map)
• Want answers that explain how each citation justifies the claim? Go with Atlas. (cited answers with reasons)
• Want one focused evidence base for maps, notes, and cited chat? Go with Atlas. (project-scoped context)
• Want typed objects and daily notes for PKM? Go with Capacities.
• Tied: keeping a typed-object database of papers you have read**: both work fine for different jobs. The wedge only opens up once you're building a corpus you'll return to.

Recommendations by user type

• PhD researchers: Atlas. The Knowledge Map helps you recall each paper's main ideas, while citations tie thesis sentences to passages. Capacities works for one-off tasks. Atlas keeps the selected sources, maps, and cited chats together inside the thesis project.
• Students doing literature reviews and thesis research: Atlas, scoped to the thesis or lit-review workflow. The Knowledge Map helps most during reading. Later questions in the same project can use its selected sources and Semantic Map.
• Knowledge workers (consultants, analysts, PMs, journalists): Atlas when reading and citing papers is the core work. Capacities when typed PKM objects are the daily need.
• Personal researchers with high-stakes questions: Atlas. Use it for medical, legal, major-purchase, or deep self-study research where you need to defend the answer. Capacities is a fine starting tool. Atlas is the tool you graduate to once the source trail matters.

Capacities is built for object-based PKM: people, books, meetings, ideas, and projects connected by typed notes. Atlas is built for source-heavy research where each answer needs a passage trail and each paper benefits from a Knowledge Map.

Pick Capacities when the object model is the organizing system. Pick Atlas when the source set is the organizing system and the same evidence will be queried again.

When Capacities is right

Capacities is a good fit for several jobs Atlas does not do. If each day links to people you met, books you started, ideas you had, and tasks you opened, its connected-object views are strong.

Its daily note plus typed-object model is clean. Atlas does not have a daily-note surface and does not try to be a PKM database.

A personal CRM use case is exactly where Capacities's typed objects pay for themselves. Think notes on 80 people you stay in touch with, with object types for "contact," "company," and "interaction."

The links between objects are the value. The AI answering layer is secondary. Atlas is built for research corpora and would feel awkward stretched over a CRM workflow.

Podcast and book tracking is another Capacities sweet spot. You want custom object types with fields for rating, status, recommender, and themes. You want a query for "all unread books from people I met this year."

You also want the daily note to surface those queries as you write. Atlas's project-and-source model has no good answer for this workflow. Its focus is defending a research claim from a body of sources.

Capacities is a strong general PKM tool with daily notes and typed objects. Atlas is a research corpus tool with Knowledge Maps and source proof. Each product serves a different category of work.

Alternatives and migration

Obsidian, Notion, and Anytype

The broader search results usually bring in 3 nearby tools: Obsidian, Notion, and Anytype. Each one solves a different version of "connected knowledge." The second-brain app guide covers the wider field. None is a one-for-one Capacities swap inside this article.

• Obsidian: Choose it for local markdown files, backlinks, plugins, and graph views. It is closer to a personal knowledge base than to Atlas. The Obsidian and Capacities comparison covers that narrower PKM decision.
• Notion: Choose it when the workspace is shared with a team. Docs, wikis, projects, and databases sit in one place. Notion AI works across that shared space, while passage-level proof for a paper corpus is a different job.
• Anytype: Choose it when ownership, privacy, and object structure are the deciding constraints. It also uses objects, templates, graph/database views, and a local-first posture.

Choose Capacities when its object experience and daily-note workflow fit your PKM habits better. Choose Atlas when you need to defend a research claim from its source passage.

Migrating from Capacities

Capacities organizes work around typed objects. A "paper" object can hold authors, year, journal, custom fields, linked authors, linked tags, and markdown notes.

Daily notes link back to those objects. Queries can surface objects that match a filter. It is a clean model. When you move to Atlas, the practical question is what survives.

Start with the Capacities export documentation. Open the collection you want to move. A literature review usually starts with the "Paper" collection plus any linked "Author" and "Tag" collections.

Export to markdown and you get one .md file per object, with frontmatter for the properties and a body for the notes. Attached PDFs export alongside the markdown when you include attachments.

The PDF files and the markdown body of your notes move across. Check other attachment formats against Atlas's supported source types before you rely on them.

Upload the PDFs to a new Atlas project as sources and open each one's Knowledge Map view to generate a map. Import the markdown files and they become Atlas project notes.

Custom object types, typed links between objects, and saved property queries do not migrate as native concepts. Atlas's main unit is the project. A "Paper" object becomes a source inside a project.

Linked "Author" and "Method" objects become notes or tags. They do not carry over as typed records. If your setup depends on multi-hop queries, Atlas does not replace that surface. The Semantic Map instead groups related sources and notes within one project.

A practical migration approach is to move one active project first. Start with 10 to 30 sources. Generate a few Knowledge Maps, then run a few cited chats and compare the source trail.

Decide whether the rest of the corpus belongs there after that trial. You can keep Capacities for daily notes and general PKM while moving paper-heavy projects to Atlas.

Worked example: a literature-review section

Suppose you are writing a related-work section on RAG. You have 18 papers. They cover sparse search, dense search, hybrid methods, and recent end-to-end systems. Here are the steps in Atlas and Capacities.

In Atlas, the steps would look like this:

1. Create a project and add the 18 PDFs as sources.
2. Open the foundational DPR paper's Knowledge Map view. Atlas generates an editable map of its main ideas with labelled connections. Open the PDF for the passage that defines in-batch negatives.
3. Repeat that review for the other 17 papers, so you can scan main ideas before deciding which PDFs to re-read in full.
4. Open the project's Semantic Map. Papers with related text tend to sit near one another, which helps you spot the sparse, dense and hybrid groups.
5. Use Classify with a category such as "training-data strategy" to color the papers by how each one builds its training set.
6. Ask Atlas which approaches to out-of-domain queries are best supported across these papers. Each citation in the answer shows the source passage and a short reason it supports the claim.
7. Open a cited claim, read the passage in the source, and keep, rewrite or discard it before you draft.

In Capacities, you create a "Paper" object for each PDF. You paste the abstract and notes, link each paper to "Method" and "Author" objects, then tag the relevant ones.

To draft the related-work section, scroll through your manual notes and hand-pick useful lines. Write the prose and place citations from memory or by checking the source object.

Capacities stores the paper as an object. You still recover its argument structure from the PDF when you write. The linking is hand-typed, and the source proof depends on your own process. For 18 papers it is workable. For 80 it becomes the bottleneck.

Common objections and edge cases

"I already have hundreds of typed objects in Capacities. Will I lose all that structure if I switch?" The typed structure does not migrate as a first-class concept because Atlas does not have typed objects. You keep the source PDFs and markdown note content, but the schema and saved queries remain in Capacities.

The practical path is to keep Capacities for the structured PKM you have built. Use Atlas beside it for literature-heavy work where maps and source proof earn their keep. Sources must be uploaded to each tool separately.

"My research is short bursts of 10 to 20 sources. Does project context matter?" It matters when those sources need to support cited answers, maps, and notes in one bounded workspace.

For self-contained bursts, the Knowledge Map and cited answers can still help. If typed objects and daily notes matter more than source-grounded synthesis, Capacities fits that pattern better and the upgrade case for Atlas is weaker.

"What about privacy and where my papers are stored?" Atlas runs on cloud infrastructure. Your uploaded papers and chats are private to your account; read Atlas's current privacy policy for retention and provider terms.

If you need local-only storage, that is a real trade-off. Review the Capacities privacy policy and your organization's cloud requirements before choosing either tool.