Turn raw JSON into a readable table
Open arrays as rows and columns in one step instead of mapping fields by hand.
Turn JSON into a readable table, scan rows and nested nodes more easily, and make changes without fighting raw braces. Everything stays local in your browser.
Turn raw JSON into a readable table, move through nested data more easily, and work with a clearer structure than raw text.
Open arrays as rows and columns in one step instead of mapping fields by hand.
Nested branches stay visible, so deeper payloads remain easy to follow without losing context.
Use the built-in navigation to move directly to the branch you want to inspect and keep the current node in view.
Scan records by column, narrow the view quickly, and find the rows that matter without reading raw blocks.
Everything runs locally, so private records stay on your machine while you review them.
Move the result into Excel, Sheets, or the next step in your workflow when you're done.
Import the payload, focus the right node, update rows, and copy the final result without switching back to raw JSON text.
From raw JSON to an editable table
This page works especially well for array-based lists, config objects, and API responses. Import the JSON, click into the relevant node, and the editor breaks the structure into a table or key-value view that is faster to scan.
After switching to table view
When you click the `users` array in the tree on the left, the right side becomes a column-based table instead of showing the whole JSON block.
Object nodes appear as key-value tables, array nodes appear as row-based tables, and you can keep drilling into nested objects when needed.
These are not abstract descriptions. They are the JSON shapes you run into most often when building products, running operations, or cleaning datasets. Each one shows both the raw JSON and how it becomes easier to inspect in table view.
Useful for admin lists, members, subscriptions, or any response shaped like an array. Once imported, you can sort, filter, and search by field immediately.
If you want to find disabled users, filter by `active = false` first and then edit the matching rows one by one.
Useful for service config, feature flags, retry policies, and other object-shaped JSON. Opening the object node makes typos and type mismatches easier to catch than in raw text.
Object-shaped JSON is displayed as key-value pairs, which is ideal for checking settings and boolean values quickly.
Useful for order lists, transaction logs, and other operational arrays. Open the array node first, then sort the rows to surface outliers faster.
If a specific order is more complex, start from the list view and then drill into that single record to inspect nested fields.
Tutorial Step
Step 1 – Load your JSON
Paste or import valid JSON and the editor immediately turns raw text into rows, columns, or a key-value grid that is easier to read.
Tutorial Step
Step 2 – Use the tree to find the right branch
Once the data is loaded, use the hierarchy first so you can focus the correct branch before making changes.
Tutorial Step
Step 3 – Edit the table view
Once the right node is open, you can edit cells directly instead of fixing commas and braces by hand.
Tutorial Step
Step 4 – Export the final result
Once you finish the local edits, validate the result and take the cleaned-up JSON back into your workflow.
A simple workflow
Start with the JSON validator so malformed input does not interrupt your import step.
Open the table view and use the tree first to find the exact business node you need instead of editing from the root immediately.
Use search, filtering, and sorting in the grid to isolate the right records before changing field values or structure.
Return to the root after editing so you can confirm the array length, object nesting, and key fields still look correct.
Copy or download the final JSON; if you still need to rename fields, restructure data, or generate a new output shape, continue with JSON Transform and let AI draft the conversion logic.
This approach is faster and safer than editing raw JSON by hand when you want a readable table, quick checks, and local changes that stay under control.
Quick tips
A table view turns arrays into rows, keeps objects readable as key-value data, and makes nested content much faster to scan than raw text.
Yes. The tool runs in your browser, so you can inspect, edit, and export data without sending it to our servers.
Arrays, records, config objects, and API responses work especially well. Lists become row-based tables, while objects stay readable as key-value pairs.
Yes. You can click into cells, update values inline, and add, delete, or duplicate rows and fields as needed. Changes stay synced with both the table and the tree.
Start with search, filters, and column sorting. That is usually much faster than reading raw text and helps you isolate the rows you actually need.
Yes. Paste your own JSON, import a file, or start from sample data. The editor detects the structure, opens the right view, and lets you jump back to the root whenever you need a full check.