Where columns come from
Keys that appear on objects are collected. Extra fields on later rows join the header; earlier rows stay blank in those cells.
JSON Tools for AI Developers · Runs locally
Natural language generation · Schema · Zod · OpenAPI · Function Calling · MCP · 30+ tools
User lists and order lists are easier to scan as a table than as raw JSON.
Paste an array, click To table, and the right pane shows text you can copy into a doc.
Columns come from object keys. Missing keys leave empty cells. Deep nesting is not split into multiple tables.
Preview stays local. Convert to CSV when you need Excel.
Keys that appear on objects are collected. Extra fields on later rows join the header; earlier rows stay blank in those cells.
No sort, filter, or charts. Export CSV for analysis. This page answers "how many columns do I have?"
An object array works best. A single object is readable, but Tree view is a better fit.
Keys are collected in the order they appear. Clean the sample if you need a fixed column set.
This page is a static preview. Export CSV for real pivots.
No.
Usually as text or a JSON snippet. They are not split into child tables.
There are no rows to show. Confirm you pasted a list, not a wrapper object.
Preview here; import or export files there.
Monospace text can shift with mixed scripts. Trust columns, not spaces.