How to use Database Query Plan Visualizer
- Paste a supported JSON EXPLAIN document copied from your own database tool.
- Choose PostgreSQL JSON or MySQL JSON as the source format.
- Inspect nesting and the explicitly labelled estimated or actual measurements.
- Download the CSV node inventory and standalone SVG diagram.
Example: Database Query Plan Visualizer
View supplied plan nesting with estimates and actuals distinguished.
Supported inputs and limits
- JSON input up to 2 MiB, 30,000 values and 40 nesting levels.
- The rendered plan is limited to 500 nodes and 30 plan levels.
- Supports PostgreSQL single-array EXPLAIN FORMAT JSON and MySQL EXPLAIN FORMAT=JSON table estimates.
- MariaDB ANALYZE JSON, MySQL TREE/ANALYZE and text plans are unsupported.
- PostgreSQL actual rows and times remain per-loop source values.
More details
Costs are not milliseconds; timings are never invented or summed into a query duration.
No database connection or tuning execution occurs.
JSON numeric literals are limited to 128 characters and must retain their decimal value through browser Number conversion; integers outside the safe integer range and unsupported precision are refused.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Questions about Database Query Plan Visualizer
Why are actual rows and time empty?
Ordinary EXPLAIN can provide estimates without running the query. The report leaves actual measurements blank when they were not present in the supplied plan.
Can I add timings from all nodes to obtain query duration?
Node timings can include children and repeated loops. Adding them can double-count work, so the viewer displays the supplied node measurements without presenting their sum as query duration.
Does this viewer connect to my database?
It reads pasted JSON only. Copy a supported plan from your database tool yourself; no hostname, password or live connection is requested.