Diagrams for articles, slides and blogs: styles and exports that look right

How to make a Mermaid diagram look right wherever it goes: pick a style for the page or the screen, set the layout, and export PNG, SVG, animated GIF or MP4, Markdown, or an interactive page.

Updated November 19, 2026 · 4 min read

A diagram that looks good in the editor can look wrong on a printed page, blurry in a slide, or out of place next to a blog's body text. This guide covers the choices that decide how a diagram looks where it ends up: the style, the layout, and the export format.

Choose a style for where it's going

Every diagram in Flowgraph Studio keeps its own style, set in the Style tab. One click restyles every node, connection, and group, with text colours chosen to stay readable.

Destination Good styles Why
Articles, papers, PDFs, print Print Ready Black on white, no shadows or gradients; prints cleanly
Slides and screen shares Slide Deck Strong blue on white; readable on a projector
Blogs and documentation Sage Notebook, Warm Editorial Soft colours that sit calmly next to body text
Product pages and launches Stripe Glass Light, polished, with soft shadows
Dark-mode docs and dashboards Linear Dark, Vercel Monochrome Built for dark backgrounds
Talks with personality Blueprint CAD, Cyberpunk Neon, Forest Canopy, Ember Workshop Distinctive dark looks

Fine-tune any of them: canvas, node, text, edge and group-title colours, corner radius, border width, gradients and shadows, a clean or hand-drawn look, and one of four fonts. Your presets saves a look by name to reuse on other diagrams.

Get the layout right

The Layout tab changes the arrangement without touching the text:

  • Engine: ELK layered for clean hierarchies (the default), ELK tree, ELK stress for networks, ELK radial for a hub, a grid of boxes, or Mermaid's own Dagre.
  • Direction: left to right for a request path, top to bottom for layers.
  • Spacing between nodes and between ranks: tighter for a slide, looser for a poster.
  • Lines: smooth curves, S-curves, right angles, or straight.

The same flowchart, drawn left to right, reads like a pipeline:

flowchart LR
  src[Sources] --> ingest[Ingest] --> clean[Clean] --> model[Model] --> serve[Serve]
  clean -.->|bad rows| quarantine[(Quarantine)]

and top to bottom, like a stack:

flowchart TB
  ui[Web and mobile apps] --> api[API layer]
  api --> svc[Domain services]
  svc --> data[(Databases and queues)]

When the automatic layout is almost right, switch to Manual and drag the last few boxes; see editing on the canvas.

Pick the export that fits the destination

Export in the top bar offers:

Format Best for Notes
PNG Slides, chat, social posts 1×, 2× or 4×, on the canvas colour or transparent; looks exactly as on the canvas
SVG Documents, design tools, print Sharp at any size; the file carries its font and plain SVG text, so it opens the same in PowerPoint, Google Slides, Figma, or a browser
GIF, MP4, WebM LinkedIn, talks, READMEs Build-up (parts appear along the arrows), Flowing lines, or a captioned Story
Mermaid code Repositories and wikis .mmd, or a .md file with a mermaid block that GitHub and GitLab draw
Interactive HTML Email attachments, offline docs One page to zoom, pan, and step through the diagram's story; loads nothing from the internet
Theme JSON Consistency The style as a file, to apply to other diagrams or to API renders

Copy SVG in the top bar copies the web version of the SVG, to paste straight into a web page.

Which size for a slide?

For a 16:9 slide, export PNG at 2× from a left-to-right diagram, or use SVG if your slide tool supports it (PowerPoint, Keynote and Google Slides all do). For a printed page, SVG with Print Ready keeps lines crisp and ink light.

Watermarks

Free accounts include 10 watermark-free image exports a month; after that, exports carry a small "Made with Flowgraph Studio" line. Pro and Pro Max have no watermark.

Animate it when the order matters

A static diagram shows structure; an animation shows sequence. Build-up reveals nodes and connections in the order the arrows go, which is ideal for a talk. For a captioned walkthrough, a Story splits the diagram into steps; see explaining a flowchart step by step.

flowchart LR
  req([Request]) --> gw[Gateway] --> auth{Signed in?}
  auth -->|yes| app[App server] --> res([Response])
  auth -->|no| login[Sign-in page]

A checklist before you publish

  • Light style for light pages. A dark diagram in a white article looks like a hole in the page.
  • Fewer than about 15 boxes. Past that, split the diagram, or link an overview to detail diagrams.
  • Label the arrows that aren't obvious.
  • Check it at the size it'll be read: a phone screen for social posts, the back row for slides.

Publishing on the web rather than as a file? Share it as a link or embed it, and it updates everywhere when you change it.

More guides