Convert Markdown to a mind map

If you already think in Markdown, you may not want to draw a map by hand. You can write the outline as text, paste it into a tool and get the map. This guide explains which parts of Markdown become topics, how to write text that converts cleanly, and how to go back to Markdown afterwards.

Why start from Markdown

Typing an outline is fast, because your hands stay on the keyboard and you do not think about layout. A Markdown outline is also plain text, so it lives happily in notes, repositories and documents. A map made from it is a different view of the same material: the text is for writing and the map is for seeing the shape.

This is useful when you have meeting notes you want to review (the meeting notes template shows one shape for them), a draft of an article you want to check for balance, or an AI-generated outline you want to rearrange. Moving a branch is far easier on a map than in a long list.

How Markdown becomes topics

The Markdown to mind map tool follows a few simple rules:

• Headings become topics. A heading with a deeper level goes under the heading above it.
• List items become topics too, nested as they are indented.
• A paragraph under a topic becomes that topic’s note.

So this text:

# Spring newsletter
## Audience
- Existing subscribers
- New readers
## Content
- Lead story
  - Interview
  - Photos

becomes a map with “Spring newsletter” in the centre, two branches called Audience and Content, and topics nested beneath them, with Interview and Photos under Lead story.

Write Markdown that converts well

A few habits make the result cleaner.

Use one top-level heading. The first heading is the natural centre of the map. If your text has several top-level headings, they become siblings, so decide which one is the real subject.

Do not skip heading levels. Go from a level-one heading to level two, then three. Jumping from one to four leaves the structure unclear.

Indent consistently. Nest list items with two spaces per level, and do not mix tabs and spaces. Inconsistent indentation is the most common reason a topic lands in the wrong place.

Keep topics short. A topic is a label. If an item runs to a full sentence, consider moving the detail into a paragraph underneath, where it becomes a note.

Leave out decoration you do not need. Bold, links and inline code are text styles, and they add nothing to the shape of the map. Plain words are the most predictable.

Step by step

First, write or collect your outline. If it is in a document, copy the text as Markdown, or save it as a .md file.

Next, open the tool. You can paste the text straight in, or choose Open file to load a .md file of up to 50 MB. The same Open file button also takes .xmind and OPML files.

Then read the map. Check each branch against your intent. The usual problems are a topic that nested under the wrong parent, because of a stray space, and a branch that is much longer than the others. Fix them by editing the map or by changing the text and pasting again, whichever is quicker.

Finally, decide what to do with it. Export a PNG to share a picture. Export a .xmind file to continue in XMind or in another app that reads it. Export Markdown or OPML to put the structure back into a text tool.

Going back to Markdown

The conversion works in both directions. When you export Markdown from a map, you get an outline of its topics and notes. That makes a good loop: draft as text, rearrange as a map, and return to text for the final document.

If you start from a .xmind or OPML file instead, mind map to Markdown turns it into an outline directly.

What does not travel is layout. Markdown holds the order and nesting of topics, but not where you dragged a branch, nor its colours. If the look of the map matters, keep a .xmind file or a PNG as well.

Privacy

Everything happens in your browser. The text you paste is not sent to a server, and the same goes for files you open. Autosave is in this browser only, so clear your browser data and the saved copy goes with it. Export what you want to keep.

When Markdown is not the right starting point

If your material is a tangle of ideas with no hierarchy, Markdown asks you to impose a tree before you have thought it through. A blank map is better for that early stage. See how to make a mind map. And if you are unsure whether a map or a plain outline suits your material, mind map vs outline sets out when each wins.

For apps that save outlines rather than Markdown, the OPML guide covers the other common route in.