Short answer: Tree layout puts the root on one side with branches running to the other, so deep, long-branched outlines read in order. Radial layout puts the root in the middle with branches around it, which suits short, even branches. Switch between them with L and press A to let auto-arrange rebuild the spacing.
What a tree layout emphasizes
The tree layout in Canvasola is horizontal: the root sits at one side and the branches run toward the other, with each level indented from the last. That shape matches how an outline is read. A person follows a tree map the same way they follow a bulleted list, from the top item down to the detail underneath it.
Its strength is depth. When branches run four or five levels deep, the horizontal layout keeps every level in a vertical stack you can scan down, and long labels have room to the right instead of being squeezed into a narrow column. A tree map of a long process is very legible.
Its cost is width. A tree map with many top-level branches grows very wide, and you end up panning or zooming out to see all of it. If your map is a list of eight or nine equally weighted sections, a tree diagram of that list is wider than it is useful.
- Root on one side, branches running to the other
- Matches the reading order of an outline
- Best when branches are deep and labels are long
- Grows wide when there are many top-level branches
What a radial layout emphasizes
The radial layout puts the root in the center and radiates the first-level branches around it, with each branch's children growing outward from there. The shape is compact and roughly circular, so a wide map stays inside a square of screen instead of running off the edge of it.
What radial emphasizes is the relationship between siblings. Because every branch sits the same distance from the center, branches of equal importance look equal, and a reader can compare them without tracing a line back to the root. It suits a set of options, a set of themes or a set of periods.
Its cost is a crowded middle. The root and its immediate children occupy the center, and anything beyond that is pushed toward the edge, where the branches thin out and begin to crowd each other. Deep maps look cramped in radial, and long labels get cut short by the curve.
- Root in the center, branches radiating outward
- Compact and roughly circular, so it fits a square of screen
- Siblings sit at equal distance and compare easily
- Deep maps get crowded in the middle
Match the layout to the branch depth
The choice follows from the shape of your content, not from preference. Count the levels first. If the map is three levels deep with five to seven top-level branches, radial fits. If it is five levels deep, or the branches are long phrases, tree fits. If neither suits it, the structure is what needs fixing first.
Screen shape matters as well. A wide monitor suits the horizontal tree, because the extra width is exactly what a tree needs. A narrow window or a tablet held in portrait suits radial, which stays roughly square and does not force a constant pan. The mind map size guide looks at how many branches a map should carry.
There is one more factor: what you will show. A tree map photographed on a phone screen in landscape works, and a radial map photographed in portrait works too, because it stays square. Decide which device the map will be read on, and let that settle the tie.
- Deep map with long labels: tree layout
- Even, shallow branches: radial layout
- Wide monitor favors tree, narrow screen favors radial
- If neither fits, the branch count is the problem
Switch layouts without losing content
Press L and the map switches between tree and radial. It is the same map either way: the same nodes, the same labels, the same colors, the same notes and the same links. Only the arrangement changes, which makes the switch a cheap experiment rather than a rebuild.
Switch on a real map and judge it at the zoom you will actually read. A layout that looks tidy in the minimap can still force you to pan around at the size you will read at. The collapsing branches guide helps here, because a folded map shows the shape of a layout more clearly.
If you switch often, make a habit of it. Keep one layout for thinking and another for showing, and note which you use for what. Because the switch is a single keystroke, there is no cost to trying the other one for a minute.
- L toggles between tree and radial
- Nodes, labels, colors, notes and links all stay put
- Judge the layout at the zoom you will read at
- Keep a thinking layout and a showing layout if that helps
Let auto-arrange fix the spacing
Press A and Canvasola releases every manual position and lays the map out again from the tree structure. That is a heavier action than it sounds: anything you dragged by hand is released, and the spacing is recomputed from scratch. It is the right tool when spacing has drifted, not when you want to fine-tune one branch.
Manual dragging has its uses. You can move a node to a position that suits the way you think and leave the rest of the map alone. The trouble is that a hand-edited map slowly goes lopsided, because the node you moved keeps its position while everything around it re-flows. Auto-arrange puts that right in one keystroke.
Run A after a batch of structural edits: a big move, a rename, a branch re-parented under a different node. Then check the result. If the rebuilt map looks worse than the one you had, undo with Ctrl/Cmd+Z. The shortcut cheat sheet has the rest of the map keys, including F.
- A releases manual positions and rebuilds the layout
- Use it after structural edits, not for small nudges
- Undo with Ctrl/Cmd+Z if the new spacing is worse
- F fits the content to the view after the rebuild
Export the layout you want to keep
Canvasola exports a mind map as SVG and as PNG, and both capture the layout exactly as it is on screen. If the tree version reads better, export the tree version, because the file records what you saw. PNG is rasterized from the SVG and is limited to a 4096-pixel maximum side, so SVG is the better file if you plan to enlarge it.
Text formats ignore the layout on purpose. Markdown, OPML 2.0 and the plain-text outline describe the tree rather than the picture of it, which is exactly what you need when the output is going into a document, a note app or another mind map tool. If someone asks for the structure, export Markdown.
Both are worth keeping, because they answer different questions. The Markdown export guide covers the text path, and a PNG is what you paste into a slide. A map you present and reuse later usually needs one of each.
- Export SVG when the file may be enlarged or edited
- PNG is rasterized from the SVG, up to a 4096-pixel side
- Markdown, OPML and plain text describe the tree, not the picture
- Export the layout you actually want to keep
A checklist you can reuse
- The branch depth was counted before a layout was chosen
- Tree layout is used for deep maps with long labels
- Radial layout is used for shallow maps with even branches
- The layout was judged at the zoom and device it will be read at
- L was used to try the other layout before committing
- Auto-arrange was run after the last round of structural edits
- The export format matches the job: SVG or PNG for the picture, Markdown for the structure
Common mistakes to avoid
- Judging a layout from the minimap. A layout can look balanced in a tiny overview and still force you to pan at full size. Check it at the zoom you will read at, on the device you will read it on.
- Running auto-arrange to fix one node. Auto-arrange clears every manual position on the map, not just the node you were aiming at. Use it after structural edits and undo straight away if the result is worse.
- Keeping both layouts in one file. Canvasola holds one layout mode at a time, so keeping a tree version and a radial version side by side means duplicating the map. Pick one and export the other if you need it.
- Exporting a layout you never looked at. A quick switch plus an immediate export produces a picture nobody checked. Read the map in the layout you are about to export, and then export it.
- Using a text export for a visual job. Markdown, OPML and the plain-text outline carry structure, not layout. If the map has to look like a map, export SVG or PNG instead.
Frequently asked questions
Which mind map layout is better for long branches?
Tree. The horizontal layout gives long labels room to run to the right and keeps each level in a stack you can scan down, so a branch with several long children stays readable. Radial is a poor fit for long branches because the circle squeezes labels near the edge.
Does switching layouts change my map?
No. Pressing L changes the arrangement only. Nodes, labels, colors, notes, links and layers all stay where they are in the data. The one thing to remember is that auto-arrange with A releases manual positions, so do not run it expecting to keep a hand-placed node.
What is the highest quality export for a mind map?
SVG is a vector export, so it stays sharp at any size and can be edited in a vector tool. PNG is rasterized from that SVG and is capped at a 4096-pixel maximum side, which is enough for slides but not for a large print.
Try both layouts on your next map.
Open a mind map, press L to switch between tree and radial, then press A to let the layout rebuild itself around your structure.
This guide is part of the mind mapping guides collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.