Colors
Diagrammo uses named colors throughout. There are two ways colors appear in diagrams: inline annotations directly on elements, and tags that map metadata values to colors across many elements at once.
Named Colors
Eleven color names are available everywhere colors are accepted:
| Name | Swatch (Nord) |
|---|---|
red | |
orange | |
yellow | |
green | |
blue | |
purple | |
teal | |
cyan | |
gray | |
black | |
white |
black and white are theme-stable — each palette picks near-darkest / near-lightest values that stay distinct from the canvas.
Swatches above use Nord values. The actual color rendered depends on your active color scheme — see Color Schemes below.
Color Schemes
Diagrammo includes ten built-in color schemes. Change yours in Settings. The same eleven color names resolve to different hex values in each scheme. Swatches show all eleven colors (red → white) for light / dark mode.
| Scheme | Light | Dark |
|---|---|---|
| Bold | ||
| Catppuccin | ||
| Dracula | ||
| Gruvbox | ||
| Monokai | ||
| Nord | ||
| One Dark | ||
| Rosé Pine | ||
| Solarized | ||
| Tokyo Night |
Editor vs Export Palette
Your editor palette and your export palette don’t have to match. You might prefer a dark scheme like Dracula or Tokyo Night while working — easier on the eyes during long sessions — but switch to a light scheme for exports that will end up in presentations, documentation, or shared links.
Diagrammo lets you set a separate Export Color Scheme in Settings. When configured, all exports (PNG, SVG, clipboard, share links) use that palette instead of your editor palette. The export theme (light, dark, or transparent background) is also independent and can be set in the Export dialog.
If no export palette is set, exports use whatever palette and theme you’re currently editing in.
Inline Color Annotations
Place a color name in parentheses directly on an element to color it explicitly.
Flowchart nodes and edges
Append (color) inside the node definition or on an edge label:
flowchart Request Pipeline
(Start(green)) -> [Parse Input] -> <Valid?(blue)>
-yes(green)-> [Process(teal)] -> (Success(green))
-no(red)-> [Error Handler(red)] -> /Log Error(orange)/ -> (Failure(red))
Every node shape supports inline color — rounds (), rectangles [], diamonds <>, parallelograms //, and more.
Timeline eras and markers
timeline Project Roadmap
era 2025-01 -> 2025-06 Foundation (blue)
era 2025-07 -> 2025-12 Growth (green)
marker 2025-03 Beta Launch (orange)
marker 2025-09 GA Release (purple)
Tags: Color by Metadata
Tags let you define named groups of values, assign a color to each value, then annotate your diagram elements with metadata. When a tag group is active, every element is colored by its matching value — without scattering color names throughout the diagram.
This is the primary way to color sequence diagrams, org charts, infrastructure diagrams, and timelines.
Declaring a tag group
tag GroupName alias g
Value1(blue)
Value2(green)
Value3(orange) default
alias g— a short alias you use when assigning metadata (optional but recommended)(color)— the color for that valuedefault— the fallback value applied to elements that have no explicit tag assignment
You can define multiple tag groups in one diagram. Only one group is “active” (coloring the diagram) at a time — the active group is selected in the diagram legend.
Assigning metadata to elements
Use | key: Value after any element to attach metadata:
Gateway | t: Platform
Redis | c: Caching, t: Platform
Multiple metadata keys are separated by commas. Use the tag alias as the key.
Sequence diagrams
Tags color participant boxes, self-messages, and message arrows. Use active-tag to set which tag group is shown by default.
sequence API Gateway — Infrastructure Concerns
active-tag Concern
tag Concern alias c
Caching(blue)
Auth(green)
RateLimiting(orange)
BusinessLogic(purple) default
tag Team alias t
Platform(teal)
Product(orange)
Security(red)
Mobile is an actor
Gateway is a gateway | t: Platform
Redis is a cache | c: Caching, t: Platform
[Backend | t: Product]
UserAPI is a service
OrderAPI is a service
DB is a database
== Authentication ==
Mobile -POST /orders-> Gateway
Gateway -verify token-> Gateway | c: Auth
Gateway -check rate limit-> Redis | c: RateLimiting
== Business Logic ==
Gateway -POST /orders-> OrderAPI
OrderAPI -INSERT order-> DB
OrderAPI -201 Created-> Gateway
== Response ==
Gateway -cache response-> Redis | c: Caching
Gateway -201 Created-> Mobile
Elements that share a tag value with the active group are highlighted in that color. Elements with no matching tag are shown in a neutral gray.
Org charts
Org charts use tag groups to color nodes by any metadata field — location, seniority, status, team, etc. Switch between views using the legend.
org Acme Corp
tag Location
NY(blue)
LA(yellow)
Remote(purple)
tag Status
FTE(green)
Contractor(orange)
Jane Smith
role: CEO
location: NY
status: FTE
Alex Chen
role: CTO
location: LA
status: FTE
[Platform Team]
Alice Park
role: Senior Engineer
location: NY
status: FTE
Bob Torres
role: Junior Engineer
location: Remote
status: Contractor
Infrastructure diagrams
infra Production Traffic Flow
tag Team alias t
Backend(blue)
Platform(teal)
CloudFront | t: Platform
-> CloudArmor
CloudArmor | t: Platform
-> ALB
ALB | t: Platform
-/api-> [API Pods]
[API Pods]
APIServer | t: Backend
instances: 3
latency-ms: 45
Timeline diagrams
Tags in timelines sort and color swim lanes. Use sort tag:GroupName to arrange items by tag value.
timeline Product Roadmap 2025
tag Team alias t
Engineering(blue)
Design(purple)
Product(green)
era 2025-01 -> 2025-06 Phase 1 - Foundation
2025-01->2025-03 Core API Development | t: Engineering
2025-01->2025-02 Design System v1 | t: Design
2025-02 Competitor Analysis | t: Product