Obsidian vs Heptabase: plain files or whiteboard thinking?

Obsidian Canvas vs Heptabase whiteboards

The comparison people actually want is Heptabase vs Obsidian Canvas, and it’s not close. In Heptabase, the whiteboard is the primary surface: cards live on boards, group into sections and mindmaps, connect with drawn relations, and — the long-standing Obsidian sore point — everything on a board is searchable. PDFs open beside your cards with highlights that become cards themselves. Journals, tags with table views and backlinks mean it still works as a complete note system off the board.

Obsidian’s Canvas is a good feature on a file-first app: infinite boards that embed your existing notes. But it’s a place you put notes, not the place you think — search inside a canvas has been a feature request since 2023 (a community plugin fills the gap), and study workflows (PDF → cards → map) need plugin assembly. If that sentence made you nod, you’re the Heptabase user — and if your other candidate is an object-based daily driver rather than files, that leg is Heptabase vs Capacities.

One point for Canvas that Heptabase cannot match: the file format. Obsidian saves every board as a .canvas file in JSON Canvas, an open, MIT-licensed spec the Obsidian team published so other apps can read and write the same boards. A Heptabase whiteboard exists only inside Heptabase. If the maps you draw are meant to last as long as the notes on them, that asymmetry matters more than any feature on the board.

Obsidian vs Heptabase for students and research notes

The threads that rank for this pairing are students and researchers asking which to use for in-depth study notes, so take that case on its own. Heptabase’s study loop is built in: open a PDF beside a whiteboard, highlight, and each highlight becomes a card you can arrange, connect and annotate; the journal and tag tables hold the day-to-day; on the paid tiers an AI tutor and whole-library AI context sit on top. It is the workflow for sense-making from sources — a literature review, a course you are trying to understand rather than memorize.

Obsidian covers the same ground by assembly: PDF annotation and Zotero integration through community plugins, the Spaced Repetition plugin for recall, Canvas for the occasional map, and plain Markdown notes that will still open when the course is a memory. Both have apps for lectures — Heptabase on Mac, Windows, Linux, iPhone, iPad and Android (plus a web app its own import guide refers to), Obsidian on desktop, iOS and Android, no web app. Price for a student is the sharpest difference: Obsidian is free, and Heptabase’s pricing page shows no student discount as of October 24, 2026 — Pro is $8.99 a month billed yearly for everyone.

The verdict for this group: maps and PDFs → Heptabase; written notes you will keep for decades → Obsidian. If the real need is flashcards and recall rather than boards, that leg is Obsidian vs RemNote.

Obsidian vs Heptabase price: free forever vs subscription-only

This is the starkest pricing gap in the category. Obsidian: free, including commercial use, with optional Sync at $4/month. Heptabase: no standalone free plan and, as of October 24, 2026, no trial listed anywhere on its pricing page — Pro at $8.99/month billed yearly (the page’s toggle reads “Yearly (Save 25%)”; the monthly rate was $11.99 when we last saw it displayed, in September 2026), with Premium ($17.99/month) and Premium+ ($53.99/month, added March 2026) tiers that mainly buy more AI credits — 100, 1,800 and 8,100 a month respectively — and unlimited PDF parsing.

Two footnotes people search for. “Is Heptabase free?” has a narrow yes: since February 2025 a paid user can invite you as a collaborator, and that invited account is a free plan limited to editing the shared whiteboards — no journal, personal library, tag databases or AI. It is a way to work on someone else’s board, not a free Heptabase. And the pricing page shows no student discount or promo code as of October 24, 2026 — if one exists it isn’t published there. The honest framing stands: you’re not paying Heptabase for note storage but for the whiteboard engine and, increasingly, the AI layer. If you won’t use either, the subscription buys polish you can live without.

AI and agents — opposite bets, again

Heptabase has invested harder in AI than almost anyone in the category: whole-knowledge-base AI context (late 2025), an AI agent that edits and organizes cards (2026), an AI tutor for learning workflows, a model picker spanning OpenAI, Anthropic and open-source models — plus an official MCP server in public beta since December 2025 and a CLI (April 2026) for agent access. All of it metered by the AI credits that differentiate its pricing tiers.

Obsidian ships no built-in AI by principle; you bring your own via community plugins, filesystem MCP servers over the vault, or the official CLI (February 2026) designed for coding agents. Same trade as everywhere in 2026: AI as a bundled, metered feature vs AI as something external working on files you control. (If the AI-native candidate on your list is an outliner rather than a whiteboard, that leg is Obsidian vs Tana.)

Switching between Obsidian and Heptabase: what migrates

Obsidian → Heptabase. Heptabase has a dedicated Obsidian importer (its import guide, updated September 22, 2026): zip your vault’s root folder and upload it, or pick individual Markdown files. Image attachments are uploaded, wikilinks and relative Markdown links are rewritten as links Heptabase understands (resolved against the files you imported), and inline tags land in Heptabase’s tag system. Plain Markdown, text and Word files import the same way, and the guide warns that another app’s structure and formatting are not guaranteed to survive exactly. We found no documented import for Obsidian’s .canvas boards — a canvas you want in Heptabase is a board you rebuild by hand.

Heptabase → Obsidian. The full-workspace Markdown export gives you one file per card with its properties; drop the folder into a vault and the text and tags are usable at once — check how your card-to-card links came through before deleting anything. What does not travel is the whiteboard itself — positions, sections and mindmap structure exist only in Heptabase, so you arrive with your notes and without your maps.

• Survives both ways: note text, images, tags, links between notes.
• Changes shape: Obsidian’s folders become a flat card library with tags; Heptabase’s card properties arrive as text in the exported files.
• Doesn’t travel: Obsidian Canvas boards into Heptabase; Heptabase whiteboard layout, sections and mindmaps into Obsidian.

Ownership, offline and the export question

Heptabase is offline-first in architecture (edits land locally and sync in the background) but cloud-resident in fact: your data syncs through its servers, encrypted in transit and at rest but not end-to-end. Export is real — full-workspace Markdown with per-card files, plus whiteboard image export — and honest about its limit: the spatial layout is the product, and positions, sections and mindmap structure don’t survive as Markdown. Your words leave cleanly; your maps don’t.

Obsidian’s answer is the usual one: the vault already is the export. If longevity-of-thinking-artifacts matters — maps you’ll want in ten years — that asymmetry is worth sitting with before committing deep visual work to any proprietary canvas, Heptabase’s included.