# Mermaid visual editor

This is the answer to the most common objection to text diagrams: that not everyone on the team will write syntax. The visual editor produces ordinary Mermaid source, so the diagram stays diffable even though nobody typed it.

![image-20260907-090521.png](https://help.gocapable.com/images/d8bebfca-01c3-47a6-95e8-6a0bde6d40f7.webp)

---

## Why it matters

A team that adopts Mermaid usually splits: the engineers write source happily, and everyone else stops contributing. That is how a diagram goes stale. The visual editor removes the split without giving up the benefits of text.

## What you can build

Flowcharts, sequence diagrams and the other common Mermaid types, edited by adding nodes and connections directly.

ℹ️

**The source is the record either way.** Switch to the text editor at any point and you will find ordinary Mermaid, editable by hand.

---

## A few things that catch people out

* Not every Mermaid feature has a visual control. The rarer syntax still needs the text editor.
* Round-tripping is safe: hand-written source opens in the visual editor, and visual edits stay readable as text.
* It writes Mermaid, so everything in the Mermaid reference applies unchanged.

---

## Related

[Text editorThe same diagrams, written by hand.](https://help.gocapable.com/diagrams/editors.html)

[Text or visual diagramsThe wider trade-off.](https://help.gocapable.com/diagrams/overview.html)

[ExamplesMermaid worth copying.](https://help.gocapable.com/diagrams/examples.html)

---

_Mermaid for the people who will not write Mermaid._