Markdown to Mind Map
Markdown heading hierarchy maps directly to mind map branch levels. H1 becomes the root, H2 becomes the main branches, H3 becomes the sub-branches, and bullet lists become leaf nodes. SpawnGraph reads this natively with no configuration — and exports back to Markdown so the round-trip is clean.
How it works
- 1Paste or drop the Markdown. Paste any text into the canvas, or drop a .md file from Obsidian, Logseq, Bear, VS Code, or anywhere else.
- 2Heading levels become branch depths. The parser reads # as the root, ## as branches, ### as sub-branches, and so on. Bullet lists become leaf nodes.
- 3Edit on canvas, export back to Markdown. Branch levels round-trip cleanly back to heading levels.
Why Markdown maps perfectly to mind maps
Markdown heading syntax encodes exactly the same hierarchy a mind map uses. # is the root, ## is a branch, ### is a sub-branch, - is a leaf. There is no impedance mismatch and no inference step — SpawnGraph reads this natively with no configuration. SpawnGraph uses client-side NLP — you can verify zero network calls during generation by opening DevTools → Network. The same parser handles setext-style headings (underlined with === or ---) for older Markdown documents.
Works with Obsidian, Logseq, and Bear
All three tools store notes as plain .md files. Export any note as .md and drop it onto SpawnGraph — the heading structure from your PKM tool becomes a visual map. Obsidian: drag the .md file directly from your vault into SpawnGraph. Logseq: use the export-as-markdown option. Bear: File → Export As → Markdown. Good for turning long notes into shareable overviews for someone who is not inside your vault, reviewing your own notes before a meeting, and sharing structured notes with collaborators who do not use the same PKM tool. See the Docs to Mind Map page for other document formats.
Technical documentation to mind map
README files, API docs, architecture decision records, and runbooks — any .md file with a clear heading structure maps cleanly. Useful for: onboarding new developers to a codebase (share the repo README as a map), reviewing specification documents, presenting technical content to non-technical stakeholders, and compressing a long contributing guide into a one-screen overview. See the developers use case for engineering-team workflows.
Export mind map back to Markdown
SpawnGraph exports any board as a Markdown outline. Branch depth becomes heading depth, leaf nodes become bullet items. Use this to convert a brainstormed mind map into a document structure ready for writing — a common workflow is to brainstorm on the canvas, export to .md, and paste into Obsidian or VS Code to flesh out the prose. The round-trip preserves the structure both ways, so you can move between visual editing and prose editing without losing the outline.
In short: SpawnGraph converts Markdown into mind maps in the browser, and exports any mind map back to Markdown. The cleanest format round-trip in the tool. No upload, no signup required.