Mermaid is a text-based syntax for describing diagrams in code.
Whimsical turns Mermaid code into editable diagrams on your board, from flowcharts and sequence diagrams to kanban boards and architecture diagrams. Many of them turn back into Mermaid when you need the code.
Command + V (Mac) or Control + V (PC) on a board. You get editable shapes and connectors, not a picture.```mermaid code block or inside a longer answer from an AI chat. Each diagram becomes a board nested in the doc. Undo once to turn it back into code. Mermaid in a doc's code blocks also gets syntax highlighting.
Start your code with any of these keywords. Each type becomes native Whimsical shapes, tables or stacks that you can edit like anything else on the board.
flowchart or graph - Shapes and connectors, with subgraphs as groupsswimlane-beta - A flowchart whose top-level subgraphs become lanessequenceDiagram - A sequence diagram with notes, frames and activationsstateDiagram-v2 - States, start and end dots, choices, forks, composite states and noteserDiagram - A table per entity, joined by crow's foot connectorsclassDiagram - A table per classrequirementDiagram - A table per requirement and elementC4Context, C4Container and the other C4 diagrams - People, systems, containers and components inside their boundariesarchitecture-beta - Each service as its icon, in dashed groupsblock-beta - Blocks, groups and block arrows on the grid you writeusecase-beta - Actors as figures and use cases as ellipses inside their system boundarieseventmodeling - Frames in time order, each in the lane and color of its kindtimeline - Periods along arrows, with their events under themmindmap - A Whimsical mind mapkanban - A stack per column, with its cards in itPasted flowcharts come out much closer to how Mermaid draws them:
```mermaid code block, frontmatter included. A frontmatter title shows above the chart.A@{ shape: doc }. Each one becomes the closest Whimsical shape.---) have no arrowhead, thick links (==>) are drawn as normal lines, and invisible links (~~~) only position their nodes. x and o ends work too.direction.classDef, class, :::, style and linkStyle. Colors snap to the closest color in your board's palette.Whimsical honors all of Mermaid's flow directions:
Without a direction, the chart is laid out top to bottom. For a horizontal chart, put "flowchart LR" at the top of your code:
If you're generating a flowchart with Whimsical AI, you can specify the layout direction in your prompt. For example, "Create a left-to-right flowchart of the user onboarding process."
[text] - Rectangle (so are (text), [[text]] and >text]){text} - Diamond (decision)([text]) - Pill((text)) - Circle{{text}} - Hexagon[(text)] - Cylinder[/text/] and [\text\] - Parallelogram[/text\] and [\text/] - TrapezoidA@{ shape: name } - Mermaid 11 shapes, matched to the closest Whimsical shape--> - Arrow--- - Line with no arrowhead-->|Label| or -- Label --> - Labeled arrow==> - Thick arrow (drawn as a normal line)<--> - Arrowheads at both ends-.- - Dashed line; -.-> - Dashed arrowx--x - Diamond ends; o--o - Circle ends~~~ - Invisible link (positions its nodes, no connector is drawn)A & B --> C & D - Multi-node connectionsclassDef className fill:#hex,stroke:#hex - Define a style class:::className or class A,B className - Apply a class to nodesstyle A fill:#hex - Style a single nodelinkStyle 0,1,2 stroke:#hex - Color specific connectors (0-based index)linkStyle 3 stroke:#hex,stroke-dasharray:5 5 - Dashed connectorNote: :::className only works with a matching classDef. Without one, it's ignored, and the rest of the diagram still pastes.
Paste an erDiagram and you get tables joined by crow's foot connectors:
PK, FK, UK) and comments.classDef, class and style color the table headings, and subgraphs become groups around their tables.It also forgives common mistakes, like a relationship without a label or an attribute block that's never closed. Try it: copy this and paste it onto a board.
Paste a kanban and you get real Whimsical stacks and cards, not shapes:
ticket, assigned and priority go into its description. High priority cards are orange and Very High ones are red.Try it: copy this and paste it onto a board.
You can copy flowcharts, ER diagrams, sequence diagrams, class diagrams, requirement diagrams and kanban stacks back out as Mermaid code for GitHub, Notion, GitLab or any other tool that renders Mermaid.
To copy a diagram as Mermaid code:
erDiagram.| in labels are kept, so the code pastes back exactly as it was.kanban, with each stack as a column and its cards in order.For flowcharts, text colors come across too. Every styled shape carries an explicit text color in the exported code, so filled and outlined shapes (including subgraphs) keep readable labels in whatever tool you paste into. Shapes with no fill leave the text color out on purpose, so their labels follow the destination renderer's own light or dark theme.
Flowchart exports also set label wrapping on the whole diagram, so long labels that Whimsical reflows onto several lines reflow in other renderers instead of overflowing or getting clipped.
Nodes are output in topological order, so the code flows in the same direction as your diagram. This ensures compatibility with how tools like GitHub use text ordering to influence layout.
Paste a sequenceDiagram and you get everything Mermaid draws, not just participants and messages:
loop, alt, opt, par, critical and break.rect backgrounds and box groups of participants.autonumber numbers your messages, and the diagram's title shows above it.Cross, async and half arrowheads are drawn as plain arrows.
If you use a coding agent like Claude, Cursor, or Windsurf, you can connect it to Whimsical via the Whimsical MCP server. Then your coding agent can generate Mermaid diagrams and build them directly in your Whimsical workspace, without any copying and pasting.
It's a quick way to turn code, specs or prompts into any of the diagram types above. For example, you could ask your coding agent to: