Mind Map Maker on Windows runs entirely in a web browser, turning an indented text outline into a deterministic, downloadable SVG without uploading the outline.
That makes it useful when you have notes in a plain text editor and want a quick visual artifact without a separate Windows application. It is a browser-based workflow, not a native visual editor with draggable nodes, collapsible branches, or a saved project workspace.

What this Windows browser workflow provides
The Mind Map Maker workflow starts with text that already expresses your hierarchy. Paste a root and its branches, mark each nesting level with indentation, and the tool produces a left-to-right diagram. Parsing, layout, preview, and download all happen in the current browser tab, so the outline is not sent to a server.
The result is a standalone SVG containing simple rectangles, cubic paths, and text. It does not contain scripts, external images, remote fonts, network references, or foreignObject elements. That makes the downloaded file a self-contained vector artifact rather than a web page that depends on external resources.
The layout is deterministic: node positions are based on depth and source order rather than automatic force-directed movement. The same valid outline therefore produces a predictable arrangement, which is useful when you want a repeatable planning or communication graphic.
Make a mind map on a Windows PC
Complete the map in your usual Windows browser with this outline-to-SVG workflow:
- Open the tool in your browser. Go to the Mind Map Maker page on your Windows PC and copy the outline text you want to map. The input is plain text, so paste it into the tool rather than expecting it to import a Word, PowerPoint, or proprietary mind-map project.
- Enter the root on the first nonempty line. Leave that line free of leading whitespace. The first nonempty line becomes the root node, and every properly indented line beneath it becomes part of the hierarchy.
- Indent each child by one complete level. Start a child line with two ordinary spaces or one tab. Add another two spaces or one tab for each deeper level, and check that no indentation level has been skipped.
- Select Generate mind map and inspect the preview. Confirm that each child sits on the intended branch. Parent-child relationships are drawn as cubic SVG paths between the corresponding boxes.
- Download the standalone SVG and keep the outline. Save the SVG when the connections look correct. Retain the original text because the exported SVG is a presentation artifact, not a project file that can be reopened for structural editing.
Because hierarchy comes from leading whitespace, the indentation must survive the copy-and-paste process. Use spaces consistently or tabs consistently within each indentation prefix; do not combine the two in the same prefix.
Set branches with exact indentation
The first nonempty line becomes the root. Each indented line then connects to the nearest preceding node exactly one level above it. This source-order rule makes branch ownership predictable instead of depending on automatic visual grouping.
| Outline element | Accepted meaning |
|---|---|
| First nonempty line | The root node; it cannot have leading indentation. |
| Two leading spaces or one tab | One nesting level below the current parent. |
| Four leading spaces or two tabs | Two nesting levels below the root. |
| Hyphen, asterisk, or plus bullet | The bullet marker is removed from the label after indentation has been read. |
| Blank lines | Ignored and not turned into nodes. |
| Windows or other line endings | Normalized locally before parsing. |
Two rules are especially important. Indentation cannot skip a level, and a single indentation prefix cannot mix tabs with spaces. Bullets are only label decoration; they do not establish depth. Only the leading spaces or tabs determine which branch receives a node.
For a compact reference while you work, keep the Mind Map Maker syntax and limits cheat sheet nearby.
Check size and hierarchy limits
The parser is designed for bounded outlines, so check these values before generating a large map:
| Limit | Supported value |
|---|---|
| Outline size | Up to 12,000 characters. |
| Nonempty nodes | Up to 80; ignored blank lines do not become nodes. |
| Label length | Up to 120 characters per label. |
| Root indentation | None; the first node must be unindented. |
| Nesting structure | Two spaces or one tab per level, with no skipped levels or mixed prefixes. |
The 120-character cap protects the accepted input size, but it does not guarantee that every permitted label will fit perfectly inside its box. The tool does not measure text wrapping, so concise phrases still create the clearest results. If a long branch looks crowded, shorten its wording rather than assuming the SVG will wrap it automatically.
Inspect the preview and download the SVG
After selecting Generate mind map, inspect the local preview before saving the file. Deeper nodes move to the right by a fixed column distance, while rows follow the original outline order. The canvas expands to include every generated node, and cubic paths connect each parent box to its child boxes.
Every label is escaped for XML before it enters the SVG. Ampersands, angle brackets, quotes, and apostrophes therefore remain visible as text instead of being interpreted as markup. The downloaded file contains only the generated vector elements and text, with no embedded script or external resource dependency.
If you want background on the output format, MDN’s SVG tutorial explains how SVG represents shapes and text. Here, the practical benefit is that the downloaded map remains a standalone vector image that can accompany your planning or communication material.
The preview and download are generated from a revocable local Blob URL. If you edit the outline, the previous result is invalidated and its URL is released, so download the version you want to keep before making further changes.
Fix common outline problems
Most hierarchy issues come from the text structure rather than the Windows browser or the exported SVG:
- The root looks indented: Remove every leading space or tab from the first nonempty line. The root must begin at level zero.
- A branch is under the wrong parent: Check the source order and indentation of nearby lines. A valid child connects to the nearest preceding node one level above it, so moving a line can change its intended parent.
- The hierarchy changes after pasting: Inspect the copied prefixes for a mixture of tabs and spaces. Keep one indentation style throughout an outline and never jump from one depth directly to a deeper level.
- Bullets are being used to imply depth: Hyphens, asterisks, and plus signs are removed after indentation is read, but they do not create branches. Add the required leading spaces or tab instead.
- A long label extends beyond its box: Shorten the phrase. Labels can contain up to 120 characters, but the tool does not measure wrapping and cannot guarantee a perfect fit for every long label.
Blank lines are not a common source of errors because they are ignored. Likewise, Windows and other line endings are normalized locally. The important inputs to review are the first line, the leading prefixes, node count, label lengths, and total outline size.
Know what the SVG can and cannot do
The finished SVG is intended as a quick planning or communication artifact. It is useful for showing a hierarchy that has already been decided, but it is not a persistent visual editor. The tool does not save projects, provide real-time collaboration, support draggable nodes, collapse branches, or import proprietary mind-map formats.
You also cannot reopen the SVG as a round-trip project and expect its nodes to remain structurally editable. For large knowledge graphs, freeform spatial editing, accessible semantic documents, or long-term collaborative projects, a dedicated diagram application is more appropriate. This browser workflow is better suited to turning a prepared outline into a clean, portable visual deliverable.
Keep the outline as the editable source
Save the original outline in your own text file before or after generating the map. That text remains the authoritative source for later changes. To revise the diagram, update the outline, paste it again, regenerate the SVG, inspect the new connections, and download another copy.
This outline-first workflow is what makes the process repeatable on Windows: text controls the structure, the browser produces a predictable preview, and the SVG provides a portable presentation output. Keep both files when you need to continue developing the idea after the first export.
If you're weighing options, Table Chart CSV Table Maker: How to Decide If You Need One covers this in detail.