Note: We make Atlas. This is a comparison written by the team that built it, not a neutral third-party review. Where Craft has the better answer for a given research job, the article says so plainly. See the table rows where Craft wins and the "When to choose Craft" section below. The goal is to give you the data you need to choose the right tool for the kind of work in front of you, not to convince you Atlas is the answer to every research job.

Atlas is a visual research workspace for people whose work depends on understanding a body of papers: a thesis, a treatment decision, a major-purchase teardown, a literature review. Craft is a note-taking app for Apple devices: beautiful typography, block-based pages, document export, collaboration, and AI features, designed for users who care about the writing experience. Both tools touch a researcher's daily work. The wedge is what happens after the first answer. Atlas deconstructs each paper into a Knowledge Map (a visual map of the argument), projects a whole corpus into a Semantic Map, runs every answer through claim-source-justification (the citation-grounded surface that explains why a passage supports a claim), and compounds prior work into a persistent knowledge graph so projects get smarter the longer you use Atlas. Craft's brand, design, and integration with the Apple ecosystem are widely admired, the block-based page editor and the document export quality are genuinely best-in-class for Apple writers. If you need to trust the answers (for a thesis, a treatment plan, a brief, a hire), the visual maps, claim-source-justification, and compounding graph are where Atlas earns the comparison.

How is Atlas different?

Craft and Atlas overlap at the surface: both touch the work of reading and reasoning over sources. But they diverge on three capabilities that decide whether the output is shareable, defensible work. This section walks through the three differences, in order.

1. Visual maps of every paper and project

Atlas builds two kinds of visual map automatically as you read. A Knowledge Map deconstructs each paper into its argument structure: claims, evidence, definitions, and labeled relations between them (motivates, causes, enables, contradicts), laid out as a multi-level zoom. You see the paper's spine at the top level and drop into the supporting passages with a click. A Semantic Map projects your whole project (sources, notes, chats, citations) into a spatial canvas where related items cluster by topic, and you can re-project the same canvas under a new topic angle without re-reading anything. The Semantic Map is how 200 papers stop being a folder and start being a corpus.

"It's like an ultimate GPT. I can finally see what I've read." Kyle Lao, NUS researcher

Craft does not have a per-paper claim-evidence deconstruction or a topic-angle re-projection across an entire project. If you've ever spent an afternoon trying to recover the structure of a paper you read three weeks ago, the Knowledge Map is the surface that pays for itself first. Visual maps make a body of papers legible at a glance, and the multi-level zoom of the Knowledge Map is the surface Atlas is built around.

2. Every claim traces to a source, and Atlas explains why the source supports it

The hallucination problem in AI research tools isn't "the model made something up." It's "the model put a citation next to a claim that the cited passage doesn't justify." Atlas renders every answer as a claim-source-justification triple: the claim, the passage, and a one-sentence explanation of why the passage supports the claim. You can click into the source paragraph and read the highlighted sentences in context.

The benchmark Atlas runs internally is the H/V ratio: the proportion of generated sentences whose citation does not survive a passage-level re-check, divided by the proportion that does. Atlas targets H/V < 0.1 on the citation-grounding benchmark, and we publish how the benchmark is constructed in Verifiable AI Research (2026): What It Actually Means. Craft's answers may include citations or links to sources, but they're grounded at the sentence-citation level (or not at all), not at the claim-justification level. For most casual question-answering the gap doesn't matter. For a thesis sentence, a legal brief paragraph, or a treatment-decision summary, it does. The wedge in one sentence: every claim traces to its source, and Atlas explains why the source justifies it.

3. Your projects compound: the second month is 10× the first

Craft treats each session (or project, or workspace) as a separable container: work goes in, an answer comes out, and the next session starts fresh. Atlas builds a persistent per-user knowledge graph across projects: every citation you jump to, every annotation you make, every Knowledge Map and Semantic Map you generate accumulates into a four-layer graph (citations + mentions + KMs + SMs) that the next chat can draw from. Open a new project on a related topic and Atlas can pull in the relevant sources, prior annotations, and chat history without re-ingesting.

This is the capability we hear about most from long-term users: the second month is 10× the first because the graph has something to work with. John Tan, a postdoc using Atlas for a multi-year literature review, describes it as "the only tool where the work I did last semester is still doing work for me this semester." Put plainly: projects get smarter the longer you use Atlas. Craft does not have an equivalent persistent compounding graph across projects, which is the wedge for sustained, multi-month research.

Try Atlas: Sign up for an evaluation sample (10 sources · 5 lifetime AI chats) and run a Knowledge Map on one of your own papers. Used by researchers at NUS, NTU, SMU, and eight other universities.

Comparing Atlas and Craft

Both Atlas and Craft touch a researcher's daily work, but they live in different categories. Atlas spans paper deconstruction, project navigation, source-cited AI answers, and compounding context across a research corpus. Craft spans beautiful block-based pages with collaboration and AI features. Craft's integration with the Apple writing experience is broader. Atlas's research depth at the citation surface is deeper. The rest of this article walks through the five capability surfaces where the two tools differ: per-paper deconstruction, project-level navigation, source-cited answering, literature-grounded annotations, and compounding context across projects. Each section is a two-column table where every row is a real capability, and at least one row in each table is one where Craft wins or ties.

Paper deconstruction (Knowledge Map)

The Knowledge Map is Atlas's per-paper surface. It deconstructs a single paper into a multi-level argument structure with labeled relations between claims, faithful-to-source nodes (the node text comes from the paper, not from a generated summary), and hierarchical breadcrumbs that let you read down from the high-level thesis to a specific paragraph.

Good to know: The bottom row belongs to Craft. Atlas does not ship that surface. The Knowledge Map's payoff is recovering a paper's argument three weeks after you first read it, when topic chips alone are no longer enough.

Project / corpus view (Semantic Map)

The Semantic Map is Atlas's per-project surface. It projects all the sources, notes, chats, and citations in a project into a spatial embedding where related items cluster by topic. Re-project the same canvas under a different topic angle without re-ingesting anything.

Good to know: Craft's strength on that row is genuine. If your work depends on it, that's the boundary. The Semantic Map's payoff is when 200 papers stop being a folder and start being a corpus you can re-project under different topic angles without re-reading.

Citation-grounded answers

Atlas produces claim-source-justification triples: the claim, the passage, and a one-sentence explanation of why the passage supports the claim. You can jump to the source paragraph, read the highlighted sentences, and check whether the reasoning holds.

Good to know: Both tools have a citation surface. The wedge is whether the surface explains why a passage justifies a claim, not just which passage was cited. For everyday Q&A the gap is invisible. For a thesis sentence or a brief paragraph it's the whole game.

Literature-grounded annotations

Atlas auto-annotates each paper on ingest. Citations inside the paper become first-class objects: Atlas resolves the cited source (when open-access), pulls the relevant passage, and lets you see how a citation in the paper builds up its argument across multiple sources without leaving the document.

Good to know: Literature-Grounded Annotations resolve citations inside the paper you're reading. When a paper cites a source that's open-access, Atlas pulls in the cited passage. It is not a web-grounding feature. It is a way to see how a single paper builds its argument across the sources it cites.

Compounding context across projects

Atlas builds a four-layer persistent graph (citations + mentions + KMs + SMs) across all your projects, so chats, annotations, and maps from one project become context for the next.

Good to know: Compounding is the slowest capability to demonstrate in a demo and the biggest payoff in week eight. If your work is many small, unrelated projects, Craft's session-isolated design is the right choice. Isolation is a feature, not a gap. Compounding pays off for sustained, multi-month research.

Price comparison

Atlas is a paid product. There is no perpetual no-cost plan. You get a short evaluation sample (10 sources · 5 lifetime AI chats), and after that you pay $20/mo or $204/yr for Atlas Pro. At the paid tier, Atlas is the only tool with Knowledge Map, Semantic Map, claim-source-justification, and compounding graph. You aren't paying for chat tokens. You're paying for capabilities that Craft doesn't have at any tier.

When to choose Atlas vs Craft

• Want paper structure deconstructed multi-level? Go with Atlas. (Knowledge Map)
• Want answers that explain how each citation justifies the claim? Go with Atlas. (claim-source-justification)
• Want your projects to compound over months? Go with Atlas. (4-layer graph)
• Want beautifully designed block-based pages for documents and collaboration on Apple devices? Go with Craft.
• Tied: writing a document that references your research notes**: both work fine, with Craft for the writing surface and Atlas for the citation grounding. The wedge only opens up once you're building a corpus you'll return to.

Recommendations by user type

• PhD researchers: Atlas. Lit-review-heavy years 1–2 benefit most from the Knowledge Map (deconstruct each paper without re-reading). Thesis-writing years 3–4 benefit from claim-source-justification (every thesis sentence anchored to a passage). Craft works for one-off tasks. The multi-year compounding graph is what makes Atlas the right tool here.
• Students doing literature reviews and thesis research: Atlas, scoped to research workflows (dissertation, thesis, literature review). The Knowledge Map is the largest time-saver in the lit-review phase, and the compounding graph keeps prior work accessible across semesters.
• Knowledge workers (consultants, analysts, PMs, journalists): Atlas when reading and citing papers is the core work. Craft when document writing and Apple-ecosystem collaboration are the daily need.
• Personal researchers with stakes (medical, legal, major-purchase, deep autodidact): Atlas. Burst-usage research where the stakes are high (medical, legal, major-purchase, deep autodidact) is exactly where citation-grounded reasoning earns its keep. Craft is a fine starting tool. Atlas is the tool you graduate to once you realize you'll need to defend the answer.

The honest one-liner across all four segments: if the research compounds, Atlas is the bet. If each session is self-contained and the next one starts fresh, Craft's form is genuinely the better fit, and we'll say so plainly. The expensive mistake is using a session-isolated tool for compounding work (every project pays the re-ingestion tax) or using a corpus tool for one-off questions where simpler tools are faster. A useful diagnostic: ask whether you expect to come back to the same corpus in three months. If yes, the project-graph approach carries its weight. If no, lighter tools win on friction. Most research workflows we hear from at universities (Cambridge, Harvard, MIT, Stanford) sit firmly on the "yes" side: the corpus is the same corpus across semesters, advisors, and grant cycles, which is the cohort Atlas is built for. The corollary is that picking the right tool is mostly a question about your work pattern, not a question about which feature list is longer. Both tools do their job well within the form they're built for.

Migrating from Craft to Atlas

If you've been keeping research in Craft, the migration path is mechanical rather than magical, and it's worth being precise about what comes across and what doesn't before you spend an afternoon on it. Craft's documents are block-based, so each page is a sequence of typed blocks (text, headings, toggle blocks, code, images, embedded PDFs, sub-pages) rather than a single flat document. Craft exports to Markdown, PDF, TextBundle, and Word, and the Markdown export is the format that hands cleanly to Atlas.

The practical sequence is: export the relevant Spaces as Markdown (TextBundle if you also want the inline images preserved alongside the prose), then gather any PDFs you embedded or attached as separate files. Upload the PDFs to Atlas first, since that is where the compounding work happens. Atlas ingests each PDF, builds a Knowledge Map of the argument, and registers the source in your per-user knowledge graph. The Markdown prose can come in as separate uploaded notes per project, where it sits alongside the deconstructed papers and is referenced by chats and Semantic Maps the same way a paper would be.

What migrates cleanly: the underlying PDF attachments, the plain-text prose of each page, headings, and inline links. What does not migrate as a native object: Craft's block-level styling (toggles, callouts, decorations), the nested sub-page hierarchy (Atlas organises by project and source rather than by nested document tree), and Craft's shareable document links (Atlas's sharing surface is project-scoped, not page-scoped). Embedded media survives as files. The visual document layout does not. Most researchers we hear from end up keeping Craft for the documents they were already writing there and using Atlas as the dedicated research corpus those documents will eventually cite, rather than treating the migration as a clean cut. The two tools sit alongside each other comfortably for the months it takes to wind a Craft workspace down naturally, and the PDFs only need to be uploaded once.

A worked example: literature-review section from 8 papers

Pick a concrete shape for the work: you've gathered eight papers for the methods section of a literature review, and you need to write roughly 1,200 words covering what the papers collectively say about a sampling approach, where they disagree, and which of the disagreements you intend to follow in your own design. This is the kind of section that takes a week of evenings to do by hand and is the cleanest comparison between the Craft workflow and the Atlas Knowledge Map workflow.

In Craft, the workflow looks like this: create a new document, drop in headings for each paper, paste your notes underneath, write toggle blocks for the key quotes, then start a separate "synthesis" document where you handwrite the comparison paragraph by paragraph. You re-read each paper at least once to pull the exact quotes. You copy-paste the citation strings. You maintain the prose alignment across the eight sources manually. The document looks beautiful when it's done. The labour of holding eight papers in your head simultaneously is yours.

In Atlas, the workflow looks like this: upload the eight PDFs into a project. Atlas ingests each one and builds a Knowledge Map per paper (the argument structure with labeled relations) plus a Semantic Map of the project (the eight papers projected as clusters by topic). Open the Semantic Map, re-project under the angle "sampling method," and the relevant nodes from each paper cluster into a single region of the canvas. Open a chat, ask "where do these papers agree and disagree on sampling, with passage-level citations," and the answer comes back as claim-source-justification triples: each claim ("Papers A, C, and F use stratified sampling on the demographic axis") is anchored to the passage that justifies it with a one-sentence reasoning trace.

The synthesis prose is still yours to write, that part doesn't change. What changes is what you bring to the writing desk: instead of eight papers and a stack of paper notes, you bring a Semantic Map showing where the eight papers land on the sampling question, a list of claim-source-justification triples with the exact passages already pulled, and a Knowledge Map of each paper for the moments when you need to drop back into a paper's broader argument to check whether you're representing it fairly. The week of evenings compresses into an afternoon of writing because the holding-in-your-head labour is the part Atlas takes. Craft, used the same way, gives you a beautifully laid-out document at the end of that week of evenings. Atlas gives you the same finished writing earlier, with every sentence anchored to a passage you can defend.

When Craft is the right call

There are three patterns where Craft is the better recommendation and we'll say so plainly. First, when the deliverable is a beautifully designed document for a client, a presentation handout, or a stakeholder-facing brief: Craft's block-based pages, typography, and PDF export are genuinely best-in-class for that surface, and Atlas does not ship a comparable document editor. If the audience for your work is going to read the document itself (not interrogate the citations behind it), Craft wins on form.

Second, when you're writing inside the Apple ecosystem and the writing experience itself matters: Craft on macOS and iPad with iCloud sync, Apple Pencil annotations, and the keyboard shortcuts an Apple writer expects is a polished daily-driver writing tool. Atlas runs in the browser and is not optimised for the long-form writing flow Craft is built around.

Third, when you need a lightweight team wiki for a small group that wants pretty pages rather than database-style structure: Craft's Spaces, sharing links, and real-time collaboration on documents are designed for that use case. Atlas's sharing surface is project-scoped and built around the research corpus, not around shared editable documents. For design-led documentation where the document is the artifact, Craft is the right call, and "writing the finished document in Craft using citations anchored back to Atlas sources" is a pattern many researchers settle on.

Common objections and edge cases

"I've only got 12 papers and a deadline next week. Is Atlas overkill for that?" Honestly, at 12 papers and a one-week horizon you can go either way. Atlas pays off faster than its long-term framing suggests (the Knowledge Map is useful on the first paper), but if you genuinely will not return to these papers, Craft's lower setup cost is reasonable. The threshold where Atlas pulls ahead inside a single project is roughly the point where you need to defend a specific claim to someone other than yourself.

"Can I keep my Craft documents and just use Atlas for the citation surface?" Yes, and this is the pattern most researchers we hear from settle into. Atlas does not try to replace the document editor. It builds the corpus, deconstructs the papers, and produces claim-source-justification triples you paste (with citations intact) into whichever writing tool you prefer. Craft is a fine destination for that prose.

"My team uses Craft for shared Spaces. Does Atlas have an equivalent?" Not directly. Atlas's sharing is project-scoped: collaborators see the project's sources, Knowledge Maps, and chats, not editable shared documents. If shared editable documents are the daily collaboration surface for your team, Craft remains the right tool for that layer, with Atlas sitting underneath as the research corpus the documents reference.