Static documentation sites
Use SVG when docs are built with frameworks that safely serve vector assets and benefit from resolution-independent diagrams.
SVG export · scalable vector output
Save Mermaid diagrams as scalable SVG files for static documentation sites, design handoff, vector editing, and code-based publishing workflows. Use SVG when you need crisp resizing or want to inspect the markup.
No signup · No watermark · Save SVG · Local browser rendering · Scalable vector output
Export controls activate after your diagram renders locally.
SVG is ideal when the diagram needs to remain sharp at any size, fit into a static site pipeline, or pass through a vector-aware workflow. It is less universal than PNG, so keep a raster fallback for platforms that block SVG uploads.
Use SVG when docs are built with frameworks that safely serve vector assets and benefit from resolution-independent diagrams.
SVG is inspectable text, which makes it useful for design reviews, asset pipelines, and versioned documentation.
Save SVG when you need to resize diagrams without blur or pass them into tools that understand vector graphics.
Use PNG when the diagram must work everywhere, including email, issue trackers, and office tools.
Save SVG when you want a text-based vector file that can be inspected or transformed downstream.
SVG is a text-based format, so some browsers or platforms treat downloads cautiously. Use HTTPS or export PNG as a fallback.
FAQ
It is best for scalable vector workflows, but PNG is safer for broad sharing. Use SVG when the destination accepts vector files.
Yes. The Mermaid render and SVG export run in your browser for the core workflow.
SVG is text/XML and can contain active content in some contexts. This tool renders with strict Mermaid settings, but some local or insecure environments still show cautious browser messaging.
PNG is usually safer for README compatibility. Use SVG when your publishing workflow explicitly supports it and you want scalable vector output.