How to use colors in a mind map

Give every branch one hue

Color earns its place by answering a question the text cannot: which part of the map am I looking at? The cheapest answer is one hue per top-level branch. Six branches, six colors, and every child inherits the color of the branch it hangs from.

Canvasola's palette is deliberately small: eight Coggle-style colors, plus a recent colors row so the hues you use often stay one click away. A palette this size is not a limitation to work around, it is the point. A map drawing on eight colors stays readable in a way that twenty never does.

Choose the hue per branch, not per node. If every node gets its own color, the map becomes a bag of labels where nothing groups. If each top-level branch owns one color, the shape of the argument shows up as bands of color before you read a word. Get the structure right first, and the branching rules guide covers that part.

• One hue per top-level branch
• Eight palette colors, so the map never looks like a paint box
• Keep the recent colors row for the hues you actually use
• Reuse a hue only when two branches mean the same thing

Note: Color is a second channel, never the only one. A reader who prints your map in grayscale should still be able to find the branches.

Let children inherit the parent color

Canvasola handles inheritance for you, and the rule matters because it changes how much coloring you do. The first child of any node takes the parent's color, and each additional sibling cycles through the palette from there. A branch you never touch still arrives in the map already coordinated.

That behavior makes your job much narrower than it sounds. You choose the color of the top-level branches and leave the subtree alone. The only time you need to recolor a child is when you are deliberately breaking the pattern, and that exception belongs on the legend.

Inheritance also makes the map self-correcting. When you add a new branch next to an existing one, the new branch picks up the next color in the cycle rather than arriving in a random color that you now have to go and fix.

• The first child inherits the parent color, siblings cycle the palette
• Set the color once, on the branch you care about
• A new sibling arrives in a coordinated color by default
• Recoloring a child is a deliberate exception, not a routine step

Note: Colors apply to the node itself. If you recolor a parent after its children exist, check that the descendants still read as part of that branch.

Reserve a color for meaning

Once hue means branch, a second meaning can ride on it. A common system reserves one color for a status: a node that is blocked, a decision that is made, a question that is still open. The rule is that status colors are reserved, so a branch never borrows a color that already carries status.

The value of a reserved color is that it survives a rescan. Come back later and a single red node anywhere in the tree pulls your attention before you read anything, because the rule says that color means one specific thing. A map where every node is colored has no such signal left.

Keep the system small enough to hold in your head. Two status colors are usually enough for a working map. If you need a third, write it into the legend, because a color code that lives only in your memory is not a code at all.

• Pick one or two status colors and reserve them
• Never use a reserved color for a branch
• Node icons can carry the same status as a second signal
• If a color needs a paragraph to explain, drop it

Keep a legend in the root note

A color rule that exists only in your head breaks the first time someone else opens the map. Put the legend in the root node's note: a short list where each color is named and given its meaning. It travels with the map, it is searchable, and it costs one node to store.

Rich notes hold formatted text, so the legend can be a bulleted list rather than a run-on sentence. Open the note for the root node, type the list, and the map now explains its own color system. The mind map notes guide covers the note panel and its formatting controls.

Put the legend in the root rather than beside the map. A legend sitting next to the map is one more thing to lose when the file is emailed, exported to Markdown, or opened on another machine. The root note travels with the data, which is exactly what a legend should do.

• One bulleted list, one line per color
• Name each color in words rather than pointing at a swatch
• Keep the legend in the root node's note
• Update the legend when you add a hue, in the same sitting

Recolor fast without breaking the map

Pressing C on a selected node cycles it through the palette, and that is the whole recoloring tool. Select a node, press C until the color you want appears, and move on. There is no color picker dialog to open and dismiss, so a pass over a map is a series of select-and-press actions.

Plan the recolor as one deliberate pass rather than an ad-hoc change. Work down the map in order, and after each branch check that the descendants still read as part of it. A map where a green branch contains a stray blue child looks like two overlapping categories.

Two things save you when a recolor goes wrong. Undo with Ctrl/Cmd+Z takes back the last change, and the version history panel keeps 20 snapshots with timestamps, so a bad color pass is never a dead end. The shortcut cheat sheet lists the other map keys, including C and F.

1. Select the node. Click the branch root you want to recolor, so the selection is unambiguous.
2. Cycle the palette. Press C until the node reaches the hue you assigned to that branch.
3. Check the descendants. Look down the branch and confirm every child still reads as part of it.
4. Record the change. If you introduced a new hue, add a line to the legend in the root note.

Check the map without color

The honest test of a color system is what the map looks like when color stops doing the work. Export it or print it in grayscale and read it. If the branches are still findable, the color was reinforcing a structure that already existed. If the map falls apart, color was carrying information you had written down nowhere else.

Canvasola exports a mind map to PNG and to vector SVG, and both are quick ways to check a map outside the editor, where you see it the way a reader will. The mind map image export guide walks through the steps for both formats.

Per-node typography gives you a second channel that survives grayscale better than hue does. Any node can have its font family set, a size between 10 and 96, plus bold, italic and alignment. Changing the weight of a top-level label adds a grouping signal that does not depend on color at all.

• Read the map in grayscale once before you rely on the color
• Use bold or a different size for a second grouping signal
• Node typography runs from size 10 to 96, with 42 as the default
• A map that only works with color has a structure problem

A checklist you can reuse

• Every top-level branch has exactly one hue
• The eight palette colors and the recent colors row are the only colors in use
• Children were left to inherit the parent color rather than painted individually
• Any status color is reserved and never used for a branch
• The legend lives in the root node's note as a bulleted list
• Each recolored branch was checked so its descendants still read as part of it
• The map was read once in grayscale and still made sense

Common mistakes to avoid

• Coloring every node. When each node has its own color, nothing groups and the map turns into a scatter of labels. Color the top-level branches and let the rest inherit.
• Using a branch color for status. A red branch and a red blocked node mean two different things, and the reader has no way to tell them apart. Reserve the status colors and keep branch hues separate.
• A legend that lives on a separate page. A legend beside the map is lost the moment the file is emailed or exported. Put it in the root note so it travels with the data.
• Recoloring children by hand. Painting every descendant overrides the inheritance rule and buries the grouping it was meant to show. Set the color once, at the branch.
• More than eight colors. The palette holds eight colors and the recent colors row. A map that needs more hues than that has too many categories, so merge branches rather than inventing shades.

Frequently asked questions

What happens to the children when I recolor a parent?

The color belongs to each node, and the inheritance rule applies as branches are created, where the first child takes the parent color and siblings cycle the palette. After you recolor a parent, check the descendants yourself and adjust them if they no longer read as part of that branch.

Can I use a custom color instead of the palette?

You pick from the eight Coggle-style colors, and the recent colors row keeps the ones you use often close at hand. There is no arbitrary color picker and no mind map theme presets beyond that palette, so a hue you need has to be mapped onto one of the eight.

Is color a substitute for good structure?

No. Color groups a map, but the tree still carries the argument. If a map only makes sense in color, the branch labels and their parallelism are not doing enough work, and no palette will fix that. Structure first, color second.

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.