What diagram types does Kroki! support?

Updated

Kroki! creates diagrams from textual descriptions. Instead of drawing a diagram by hand, you write a plain-text definition in a specific syntax, and Kroki renders it into an image. The site organizes this around a Diagram types list and a Cheat sheet, plus an Examples section and a Try area where you can test a definition directly.

If you already know which syntax you want to use (for example, you have a Mermaid or PlantUML definition), the practical question is whether Kroki supports that type. If you are starting from scratch, the question is which diagram type fits your content. Both are answered by the same list.

How the diagram types are organized

Kroki groups its supported types by the text syntax or tool that produces them. Each diagram type corresponds to a different textual language, so choosing a diagram type is really choosing a syntax. The site presents this as a browsable list of diagram types, with a cheat sheet for quick reference and examples you can look at before committing.

The main categories you will encounter on the list include:

  • Flow and process diagrams — for step-by-step logic, pipelines, and decision paths.
  • Sequence diagrams — for interactions between actors or systems over time.
  • Class and structure diagrams — for object models, relationships, and hierarchies.
  • Other specialized types — the list is broader than these three, and each entry links to its own syntax and examples.

Because the list is the authoritative source, treat it as the place to confirm whether a specific type is available rather than assuming from a tool name.

Choosing a diagram type for your content

The right choice depends on what you are trying to communicate, not on which syntax looks nicest.

If you need to show… Look for a type in the…
Steps, branches, and decisions Flow / process diagram category
Messages passed between parties in order Sequence diagram category
Objects, attributes, and their relationships Class / structure diagram category
Something not covered above Scan the full Diagram types list

A useful check: if you can describe your content as a sentence with a clear subject and a clear order of events, a sequence or flow type is usually the closer fit. If your content is mostly about what things are and how they connect, a structure type fits better.

Where to verify and try a type

  1. Open the Diagram types section to see the full list of supported types.
  2. Pick the type that matches your content and open its entry to see the syntax.
  3. Use the Cheat sheet for a condensed reference of that syntax.
  4. Check the Examples section for a working definition you can adapt.
  5. Use the Try area to paste a definition and confirm it renders as expected.

The expected result at step 5 is a rendered diagram image from your text. If it does not render, the usual cause is a syntax error in the definition rather than an unsupported type — so first confirm the type appears in the Diagram types list, then compare your text against the cheat sheet or an example.

Common sticking points

  • Mixing syntaxes. Each diagram type has its own syntax. A definition written for one type will not render under another, even if the two types look similar.
  • Assuming a type exists. The supported set is defined by the site's list. Check the list before writing a long definition in a syntax Kroki may not accept.
  • Skipping the examples. The examples are the fastest way to see the exact expected structure of a definition, including required opening and closing lines.

For a first diagram, the lowest-risk path is to copy an example from the Examples section, change its labels to your own, and confirm it renders in Try before expanding it.