Draw a diagram from a few lines

Write a flowchart, a state diagram or a sequence diagram as text in a note, and Soundings draws it.

Updated Sun, Nov 15, 2026

Some things are easier to see than to read: what happens on a request, the states a machine moves between, who calls whom. Write a few lines in a note and Soundings draws them.

The lines are written in the way other note apps and code sites already understand, so a note you export still draws its diagrams where you take it.

The quickest start

Under the capture box, select Add a diagram. A flowchart skeleton is written into the box with the cursor inside the first box, ready for you to name it. Fill in the two boxes, and the drawing appears when you save.

Before you begin

The three kinds

The first lineWhat it drawsA line under it
flowchart LR or graph TDBoxes joined by arrowsA[Request] --> B{Cached?}
stateDiagram-v2States and what moves between themIdle --> Running: start
sequenceDiagramWho sends what to whom, in orderBrowser->>Server: GET /page

Write a flowchart

  1. Start the block with flowchart LR.

  2. Name each box as you use it: A[Back up], B{Restored?} for a choice, C(Done) for a rounded box.

  3. Join them with an arrow: A --> B.

  4. To write on the arrow, put the words in bars: B -->|no| C, or in the middle: B -- no --> C.

Soundings draws from left to right, whichever direction you write after flowchart.

Write a state diagram

  1. Start the block with stateDiagram-v2.

  2. Write [*] --> Idle for where it starts, and Running --> [*] for where it ends.

  3. Name what moves it along after a colon: Idle --> Running: start.

Write a sequence diagram

  1. Start the block with sequenceDiagram.

  2. Write who asks whom, and what: Browser->>Server: GET /page.

  3. Use -->> for the answer coming back: Server-->>Browser: 200 OK. It is drawn as a dashed line.

  4. To fix the order they stand in, name them first: participant Browser.

Read it as words

Under every diagram is What this diagram says. Open it for the same thing in sentences, one for each arrow. A screen reader reads this list; the drawing itself is named but not read.

When it is not drawn

If a line cannot be read, nothing is drawn and the whole block stays as code, so you never see half a diagram. Check that:

Note: a diagram wider than your notes column scrolls sideways inside its frame. Your diagrams are plain text in your entry, so they are in every export and backup, and nothing is sent anywhere.

Try it: Open Courses, then a session

Related articles

Something missing or unclear? Tell us on the contact page.