Supported chart and diagram formats in ChartQuery

If you are choosing ChartQuery for reports, dashboards, documentation, or automation pipelines, the first question is simple: which formats are actually supported today?

This article is a codebase-verified overview of the formats currently available for both charts and diagrams in ChartQuery.

Chart formats (10 types)

ChartQuery supports the following chart types through the chart endpoint:

Type	Best for
Bar chart	For comparing values across categories
Line chart	For showing trends over time
Area chart	For visualizing cumulative trends or volume over time
Doughnut chart	For part-to-whole analysis with a center cutout
Pie chart	For simple part-to-whole comparison
Radar chart	For comparing multiple metrics across items
Polar area chart	For radial comparison of cyclical data
Bubble chart	For three-dimensional data (x, y, and size)
Scatter chart	For analyzing correlation between two numeric variables
Mixed chart	For combining multiple chart types on shared axes

These cover most day-to-day analytics use cases: KPI dashboards, performance tracking, trend analysis, and comparison visuals.

Diagram formats (28 languages)

ChartQuery also supports 28 diagram languages through the diagram endpoint:

• Mermaid
• PlantUML
• D2
• GraphViz
• DBML
• Nomnoml
• Structurizr
• ERD
• TikZ
• Svgbob
• Excalidraw
• C4 with PlantUML
• BPMN
• BlockDiag
• SeqDiag
• ActDiag
• NwDiag
• Vega-Lite
• WaveDrom
• Ditaa
• Pikchr
• Vega
• WireViz
• UMlet
• Symbolator
• PacketDiag
• RackDiag
• Bytefield

This range lets you cover everything from software architecture and UML modeling to data visualization specs and low-level hardware-style diagrams.

How to choose quickly

• Use bar, line, or area for most business analytics.
• Use scatter or bubble when you need relationships and distributions.
• Use Mermaid for lightweight docs and markdown-native workflows.
• Use PlantUML or C4 with PlantUML for architecture and software design.
• Use GraphViz for dependency graphs and directed relationships.
• Use BPMN when you need business-process notation.

One API, same workflow

Both chart and diagram rendering follow the same pattern:

1. Send a request to the right endpoint.
2. Pass either a chart config or a diagram source.
3. Receive a rendered image you can use in docs, apps, reports, or emails.

That consistency is what makes ChartQuery practical for both manual workflows and automated generation pipelines.