TL;DR verdict

Foam and Dendron are both free, open-source VS Code extensions for personal knowledge management, making this a head-to-head comparison for developers who live in VS Code. Foam takes inspiration from Roam Research — freeform linked notes with a graph view, minimal structure imposed. Dendron goes the opposite direction with a strict hierarchical note system using dot-notation (e.g. project.meeting.2024), schemas, and refactoring tools for large vaults. Foam is better for exploratory, connected thinking. Dendron is better for managing large, structured technical knowledge bases where you need predictable organization.

Quick comparison

FeatureFoamDendron
Starting priceFree planFree plan
Free planYesYes
Open sourceYesYes
Self-hostableYesYes
G2 ratingNot listedNot listed
Best fordevelopers who want a free, graph-based PKM tool inside VS Codedevelopers managing large, structured knowledge bases with hierarchical organization
Starting priceFree plan available; paid tiers depend on usage and plan limits.Free plan available; paid tiers depend on usage and plan limits.
Free planYesYes
Open sourceYesYes
Self-hostableYesYes
Deployment modelopen-sourceopen-source
Best forself-hosted productivity software teamsself-hosted productivity software teams
Primary riskRequires internal ownership for hosting, upgrades, and security.Requires internal ownership for hosting, upgrades, and security.

Note-taking and linking model

Winner: Foam

Foam wins for natural, freeform note-taking. You write Markdown, create wiki-style links with double brackets, and a graph emerges organically from your connections. There's almost no learning curve if you already know Markdown — just write and link. Dendron's hierarchical model is more rigid: every note lives in a dot-notation hierarchy, and new notes inherit schemas that enforce structure. This is powerful once internalized but creates real friction when you want to capture a quick idea without deciding where it belongs in the hierarchy. For natural, link-as-you-think note-taking, Foam feels lighter. For teams who want discipline enforced by the tool itself, Dendron's structure pays off long-term.

Offline and local-first access

Winner: Foam

Both tools are fully local-first — your notes are Markdown files on disk, and neither requires internet access to function. This is a genuine shared strength compared to cloud-based tools. Foam has a slight edge here because it has fewer background processes and VS Code extension operations than Dendron, which runs a workspace daemon for indexing and hierarchy management. In practice, both work offline without meaningful limitations. If you're choosing between them on offline capability alone, pick the one whose organizational model suits your workflow — local-first is a given for both.

Knowledge graph and backlinking

Winner: Foam

Foam is named for Roam-style networked thought and the graph view is its signature feature. Bidirectional links, backlink panels, and a visual graph of connected notes are all first-class in Foam. Dendron has a graph view too, but it's secondary to the hierarchical tree structure — Dendron's primary navigation is the note tree, not a graph. For users who want to visually explore how their ideas connect and discover unexpected relationships, Foam's graph-first design is more satisfying. Dendron's hierarchy gives you a different kind of navigation power — you always know exactly where a note is — but it doesn't replicate the serendipitous discovery that Foam's graph enables.

Database and structured content

Winner: Dendron

Dendron wins this category clearly. Its schema system lets you define templates for note types — every meeting note, every project note, every RFC follows the same structure automatically. Frontmatter is first-class in Dendron and the engine can query notes by their metadata. Foam has no equivalent schema or template system beyond basic Markdown; structure is entirely self-imposed. For developers managing documentation, technical specs, or any structured knowledge that benefits from consistency, Dendron's schema enforcement saves substantial cognitive overhead. The hierarchy plus schemas makes Dendron closer to a lightweight structured database than a free-form note tool.

AI and smart search

Winner: Foam

Neither Foam nor Dendron has native AI features built in — they're VS Code extensions that leverage VS Code's ecosystem. Both users get access to GitHub Copilot and other VS Code AI extensions. Foam's search relies on VS Code's built-in search, which is full-text and fast. Dendron has a more powerful lookup interface — its fuzzy note lookup uses the hierarchy as context and can be faster for navigating large vaults. For AI assistance, both tools are equal since they both inherit whatever VS Code AI extensions you install. For structured search across a large vault, Dendron's lookup gives slightly better results when your notes are well-organized hierarchically.

Pricing for individuals and teams

Winner: Foam

Both Foam and Dendron are completely free and open-source. There is no paid tier, no subscription, and no premium features behind a paywall for either tool. Foam is a VS Code extension you install for free. Dendron is the same. The cost comparison is purely about your own time to set up and maintain each system, plus whatever you're already paying for VS Code (which is also free). This is a genuine tie on pricing, but Foam edges out Dendron because it's simpler to get started with — lower setup investment for the same zero dollar cost.

Pricing deep-dive

Foam

  • Free plan: available for evaluation or limited production use.
  • Entry paid tier: starts from free with feature or usage upgrades on paid tiers.
  • Pricing model: open-source; license is open-source; deployment type is open-source.
  • Open-source: subscription cost may be replaced by hosting, upgrades, and internal maintenance.

Dendron

  • Free plan: available for evaluation or limited production use.
  • Entry paid tier: starts from free with feature or usage upgrades on paid tiers.
  • Pricing model: open-source; license is open-source; deployment type is open-source.
  • Open-source: subscription cost may be replaced by hosting, upgrades, and internal maintenance.

Pricing verdict: Both Foam and Dendron are completely free and open-source. No paid tiers, no subscriptions. The only cost is your time. Foam is faster to get running; Dendron takes more time to configure but rewards that investment with more powerful organization at scale.

How to migrate from Foam to Dendron

Data export
Foam notes are plain Markdown files in a folder on your disk — there's nothing to export. Your entire vault is already portable files you control. Copy the folder and you're done.
Import support
Dendron can initialize a new vault from an existing Markdown folder. Run 'Dendron: Initialize Workspace' pointing to your Foam notes directory. Your existing wiki-links will work, though you'll want to rename files to follow Dendron's dot-hierarchy convention for full benefit.
Does not migrate
Foam's wiki-link format is compatible with Dendron, but the organizational approach differs fundamentally. You'll want to spend time restructuring flat Foam notes into Dendron's hierarchical naming convention to get the full value of Dendron's lookup and schema system.
Time estimate
Plan two to five days for a small team with simple configuration, one to three weeks for a mid-size team, and longer if compliance review, custom fields, or external users are involved.

What real users say

Foam: Foam users love the simplicity and the fact that notes are just Markdown files with no vendor overhead. Common complaints are the lack of active maintenance — Foam's development pace has slowed significantly — and limited features compared to dedicated apps like Obsidian. Users often note that Foam works best if you already live in VS Code.

Dendron: Dendron users praise the hierarchy system for managing large technical knowledge bases — developers with hundreds or thousands of notes cite it as uniquely scalable. Common complaints are the steep learning curve, the overhead of naming conventions, and the fact that Dendron's development also slowed after the company pivoted. Both tools carry maintenance uncertainty as smaller open-source projects.

Sources: Pattern synthesized from catalog data, vendor positioning, and public review themes; verify on G2 or Capterra before quoting directly.

Final verdict

Choose Foam if...

  • Choose Foam if you want a minimal, graph-oriented PKM that gets out of your way and lets you write Markdown freely.
  • Choose Foam if you prefer organic link-based organization over imposed hierarchical structure.
  • Choose Foam if you have a smaller, more exploratory vault where hierarchy would feel like overkill.

Choose Dendron if...

  • Choose Dendron if you're managing a large technical knowledge base with hundreds of notes that need consistent, queryable structure.
  • Choose Dendron if you want schema-enforced templates so every note type (meeting, project, RFC) is consistent without effort.
  • Choose Dendron if you've already outgrown Foam and find the flat link-graph approach too chaotic for your vault size.

Consider neither if: Consider neither if you want a dedicated PKM app with active development and a rich plugin ecosystem — in that case Obsidian is the better VS Code-adjacent alternative that doesn't require VS Code itself. Both Foam and Dendron have slowed in active development as of 2025.