Mermaid state diagram editor
Model state machines with Mermaid syntax and export clear, presentation-ready transitions for workflows, checkout flows, and feature logic.
Use this page to connect a high-intent search query to the right problem-solution narrative.
A Mermaid state diagram page for teams modeling finite-state behaviour of a feature or user journey.
View Mermaid sourcePlain-text diagram syntax — copy or edit directly.
1stateDiagram-v22 [*] --> Draft3 Draft --> Submitted: submit4 Submitted --> Paid: pay5 Submitted --> Cancelled: cancel6 Paid --> Fulfilled: ship7 Fulfilled --> [*]8 Cancelled --> [*]What Mermaid state diagrams capture
State diagrams show how a single entity moves between states in response to events. They work well for order flows, feature toggles, and UI modes.
- Start and end states
- Events that trigger transitions
- Composite (nested) states
When a state diagram is the right fit
Use a state diagram when the important question is 'what can this entity do next, given where it is?' — not the call order between services.
Pairs well with
State diagrams pair naturally with sequence diagrams. Use state to describe possible modes, and sequence to describe how a single happy path walks through those modes.