What is a JSON to table converter?
A JSON to table converter presents JSON values as rows and columns. Arrays of objects become record tables, ordinary objects become Key, Type, and Value tables, and other arrays show their indexes, types, and values.
This tool keeps nested data in its original hierarchy. Objects that contain only primitive fields appear as compact JSON by default and open a formatted read-only inspector when selected. Objects with deeper containers and arrays remain navigable instead of being flattened into long path-based column names.
How to view JSON as a table
- Paste strict JSON into the editor, open a
.jsonor.txtfile, or select Example. - Select Convert to Table to validate the source. By default, the viewer opens the first array it finds and displays leaf objects as values; both behaviors can be changed in Settings.
- Use object, array, or record-index links to browse deeper levels. The breadcrumb and Back or Forward buttons show where you are.
- Search the current table, select a column header to sort it, or change the number of rows per page.
- Open Export current table to copy the filtered and sorted rows as CSV or download them as a
.csvfile.
Select Edit JSON when the source needs a change, then run it again to rebuild the tables. The table itself is read-only.
JSON to table example
The built-in example uses a wrapped API response:
{
"data": {
"users": [
{
"id": 101,
"name": "Alice",
"orders": [
{ "id": "A-1001", "total": 79.5 }
]
}
]
}
}
The default settings open users immediately, with id, name, and orders as columns. A leaf object such as address appears as compact JSON and opens a formatted inspector when selected. Open the orders cell to view that user’s orders as a separate table.
How nested JSON tables work
Each JSON level uses one predictable table shape:
| Current value | Table shape |
|---|---|
| Object | Key, Type, and Value rows |
| Array of objects | One record per row and the first-seen union of direct fields as columns |
| Primitive or mixed array | Index, Type, and Value rows |
| Root string, number, boolean, or null | One Type and Value row |
Objects with direct object or array fields and all arrays show a compact item or field count and remain navigable. Leaf objects, including {}, appear as compact JSON by default; select one to view its formatted value in the read-only inspector. Turn off Show leaf objects as values to make those objects navigable again. Missing fields, JSON null, empty strings, false, and 0 remain distinct.
The leaf-object display setting applies after a 300 ms pause, so consecutive changes rebuild the current table only once.
Filtering, sorting, and pagination
Search and sorting apply only to the table at the current breadcrumb path. Sorting cycles through ascending, descending, and original order. Missing fields and null stay at the end, while equal values retain their source order.
Pagination controls only what is rendered on screen. Choose 25, 50, 100, or 250 rows per page without changing the underlying JSON.
Exporting the current JSON table as CSV
CSV export includes all rows that match the current search in their current sort order, not only the visible page. A record table exports its data columns without the navigation index.
Nested objects and arrays are preserved as compact JSON inside one CSV cell. To export a nested collection as its own rows and columns, open that collection first and export its table. Copy as CSV produces plain CSV text; Download CSV adds UTF-8 compatibility information for spreadsheet software.
This current-level export is intentionally different from JSON to CSV, which is designed to flatten an entire record set into a final CSV file.
JSON Table vs JSON Viewer and JSON Editor
| Tool | Primary purpose |
|---|---|
| JSON to Table | Compare values at one level, then browse nested levels as related tables. |
| JSON Viewer | Inspect the complete hierarchy as a collapsible tree. |
| JSON Editor | Make focused changes in Code or editable Tree views. |
| JSON to CSV | Convert a chosen record set into a flattened CSV file. |
Use this table viewer when rows and columns make same-level records easier to compare. Use the JSON Viewer when the overall tree structure matters more than tabular comparison.
JSON to table FAQ
Does JSON have to contain an array?
No. An object becomes a Key, Type, and Value table, and a root primitive becomes a single row. Arrays of objects produce the most familiar record table.
How are nested objects and arrays displayed?
Leaf objects appear as compact JSON and open a formatted read-only inspector when selected. Objects with deeper containers and arrays appear as navigable cells with their type and size; selecting one opens it as the current table and adds it to the breadcrumb.
Why are some cells empty?
An empty cell means that record does not contain the field. JSON null, an empty string, false, and 0 use explicit values so they remain distinguishable.
Does sorting or filtering change my JSON?
No. Both operations affect only the read-only current table. The source text is not reordered or rewritten.
Does CSV export include every nested level?
No. It exports only the current table. Nested values stay in one CSV cell as compact JSON unless you open that value and export its own table.