DiagramPreview
Basic parserServer SVGText diagramsExport ready

PlantUML Preview

Paste a complete PlantUML document to preview the diagram, download SVG or PNG, and keep an editable .puml source file. Rendering uses the public PlantUML service through this site’s API.

Examples
PlantUML previewReady
Your PlantUML preview will appear here.

Continue with a related tool

Compatible tools can carry your current source or converted XML. Other tools open separately.

PlantUML handoff workflowplantuml-previewplantuml-to-drawiodrawio-preview
PlantUML to Draw.io

Convert PlantUML sequence, component, class, and activity diagrams into editable draw.io / diagrams.net XML.

Continue with current source
Mermaid Preview

Preview Mermaid diagrams online with a live editor, syntax checks, examples, and SVG/PNG export.

Open
AI PlantUML Generator

Generate PlantUML diagrams from natural language with DeepSeek.

Open

AI Review beta

Review the diagram before publishing

Run a local heuristic check for syntax, readability, failure paths, and handoff risk. Source is not uploaded; remote AI Review requires explicit submission.

Local beta review does not send source, prompt, or diagram content.

Verify the result with real files

Support and limits

Source is sent through this site's API to the public PlantUML service. Use public examples. Requests are limited to 64 KiB including JSON, SVG to 2 MiB, and upstream rendering to 10 seconds. The original .puml remains downloadable when rendering fails.

Minimal example

Two participants and one message. SVG and PNG preserve the rendered sequence; .puml preserves exact source.

@startuml
Alice -> Bob: ping
@enduml
Minimal example: Two participants and one message. SVG and PNG preserve the rendered sequence; .puml preserves exact source.
Example output exported by this site's tool.

Business example

A sign-in sequence with four participants and six messages. Review request and reply directions before adding it to a runbook.

@startuml
actor Customer
participant Web
participant API
database DB
Customer -> Web: Sign in
Web -> API: POST /session
API -> DB: Find account
DB --> API: Account
API --> Web: Session token
Web --> Customer: Signed in
@enduml
Business example: A sign-in sequence with four participants and six messages. Review request and reply directions before adding it to a runbook.
Example output exported by this site's tool.

Failure example

The extra line is invalid PlantUML syntax and should produce a rendering error. Retry or repair the source; SVG/PNG must stay unavailable until a successful render.

@startuml
Alice -> Bob: ping
this is invalid syntax ???
@enduml

How to use

  1. 1Paste a complete PlantUML document that includes @startuml and @enduml.
  2. 2Choose a sequence, class, use case, or activity sample when you need a known-good starting point.
  3. 3Review the rendered SVG for missing participants, unreadable labels, styling that hides meaning, and remote include dependencies.
  4. 4Reduce failing diagrams to a minimal source before adding skinparam, notes, sprites, or complex blocks back.
  5. 5Use SVG or PNG after checking the result, or Download file to save the original .puml source. Retry a failed render after checking syntax or simplifying the diagram.

Common use cases

Sequence diagramsUML class sketchesUse case diagramsActivity flow reviewArchitecture decision recordsCode review documentation

FAQ

How does PlantUML rendering work?

Your source is sent through this site’s API to the public PlantUML renderer. A successful SVG is cleaned for static preview and image export. Requests are not cached by this site. Use a trusted private renderer for sensitive diagrams.

Can I download SVG, PNG, and PlantUML source?

After successful rendering, use SVG or PNG to download the image. Download file saves your exact current source as .puml, including when rendering fails. PNG uses the image’s actual dimensions; very large images may require SVG instead.

What should I check before publishing a PlantUML diagram?

Confirm the source is complete, labels are short enough, remote includes are intentional, and the rendered SVG still matches the system or workflow being documented.

Is server-rendered PlantUML suitable for private diagrams?

Use a trusted private renderer for sensitive diagrams. Server rendering can send PlantUML source to the renderer that creates the SVG.

PlantUML Preview helps teams review UML-style diagrams without leaving the browser. It is useful for sequence flows, classes, activities, and use case diagrams that belong beside engineering documents.

Rendering uses a fixed public PlantUML service through a same-origin API. The request limit is 64 KiB of JSON and the SVG response limit is 2 MiB. Timeouts and syntax errors show a retry option; failed renders do not enable image downloads.

Because the editor uses plain text, diagrams can move cleanly between code review, wikis, issue trackers, and exported SVG assets.

Preview and image exports contain static SVG content: hyperlinks, embedded images, and external resources are omitted. Download .puml to preserve the original source and its dependencies. SVG and PNG downloads use the same cleaned diagram shown in the preview.

Demo: document a login sequence with PlantUML

PlantUML is strong when a diagram needs to live beside code. A compact sequence source can explain authentication, token exchange, and failure handling without drawing by hand.

  • Name participants exactly as they appear in the system boundary.
  • Keep messages short enough for review comments and wiki pages.
  • Use alt blocks for expected failure paths instead of writing them only in prose.
@startuml
actor User
participant Web
participant Auth
database SessionDB
User -> Web: submit credentials
Web -> Auth: verify password
Auth -> SessionDB: create session
Auth --> Web: token
Web --> User: signed in
@enduml

Troubleshooting: isolate server-rendered PlantUML failures

When PlantUML rendering fails, the fastest path is to reduce the source until the server accepts it, then add styling, notes, and complex blocks back gradually.

  • First test @startuml and @enduml with two nodes only.
  • Check whether remote includes, sprites, or skinparam blocks depend on unavailable resources.
  • Keep private diagrams on trusted renderers because server rendering can send source to that renderer.
@startuml
Alice -> Bob: ping
Bob --> Alice: pong
@enduml

Review pattern: keep PlantUML source maintainable

PlantUML diagrams work best when the text source remains readable in code review. Heavy styling, large includes, and dense diagrams can make the rendered image look polished while the source becomes hard to maintain.

  • Keep participant and class names close to the terminology used in code or docs.
  • Use notes for assumptions instead of hiding them in long message labels.
  • Split unrelated class, sequence, and activity views into separate diagrams.
@startuml
participant Client
participant API
note over API: Validate token before reading orders
Client -> API: GET /orders
API --> Client: 200 OK
@enduml

Review checklist for PlantUML Preview

Use PlantUML Preview when you need to inspect source content visually before it becomes documentation, a pull request note, an incident write-up, or a handoff artifact. Preview PlantUML online and download SVG, PNG, or the original .puml source.

Before exporting, check that labels are readable, relationships match the source, generated examples do not contain private data, and the preview still makes sense after you edit the input.

Limits and troubleshooting

If the preview fails, reduce the input to the smallest complete example, confirm the format syntax, and then add sections back one at a time. Many rendering failures come from partial files, indentation mistakes, missing diagram headers, or copied snippets that depend on hidden context.

Treat the preview as a review surface rather than a source of truth. Generated diagrams, converted files, dashboards, and rule examples should be checked before they are used in production documentation or operations.

Example inputs to test

  • Sequence: @startuml actor User participant App participant Service User -> App: Submit diagram App -> Service: Render Service --> App: SVG App --> User: Preview @enduml
  • Class: @startuml class Diagram { +source: string +render(): SVG } class PlantUMLDiagram Diagram <|-- PlantUMLDiagram @enduml
  • Use case: @startuml left to right direction actor Developer rectangle DiagramPreview { Developer -- (Preview PlantUML) Developer -- (Export SVG) } @enduml

Tool maturity

Basic parser

Basic parser

This tool focuses on fast structure inspection. Use it for review and debugging, then verify critical output before production use.

The maturity label is not a quality score. It tells visitors whether the tool is best for stable export, deeper debugging, quick parsing, or AI-assisted generation.