JSON Navigator

Open one node at a time and see its children as a table of keys, types, values and full paths.

JSON
Node contents
Runs locally in your browser

About the JSON Navigator

A tree view that expands everything becomes unreadable once a document passes a few thousand lines. This navigator shows a single node and its immediate children instead: one row per key with its type, a short preview and the exact path you would write in code to reach it. Nothing below that level is drawn, so a response with fifty thousand records opens as quickly as a small one.

Type a path such as $.zones[1].items into the box to move the view. Dot notation, bracket indexes and quoted keys with spaces all work, and the breadcrumb above the table shows where you are. If a segment does not exist the error names the level that failed and lists the keys that were available there, which is usually enough to spot a typo or a renamed field.

The path column is the reason to reach for this tool over a formatter. Copy a row path straight into a JavaScript expression, a jq filter or a test assertion without counting brackets by hand. Sorting keys makes a wide object easier to scan when the producer emits them in insertion order.

Copy sends the focused node as formatted JSON rather than the table markup, so you can lift one branch out of a large document. For a collapsible view of everything at once, use the JSON Viewer, and to list every path in the file try the JSON Path Finder.

How to use

  1. Paste a JSON document, or press Sample to load a warehouse report.
  2. Read the table of children: key, type, value preview and full path.
  3. Type a path such as $.zones[1] into the Path box to move down a level.
  4. Press Copy to take the focused node out as formatted JSON.

Common questions

What path syntax does the box accept?
Dot notation, numeric indexes in brackets and quoted keys, for example $.zones[1].items or $["order id"]. A leading $ is optional.
Why does the view not expand everything?
Showing one level keeps large documents fast and readable. Move down by typing the path of the child you want to inspect.
Does Copy return the table or the data?
The data. Copy hands back the focused node as formatted JSON, ready to paste into an editor or a test fixture.
What happens if the path points at a plain value?
The value is shown in full instead of a child table, which is handy for reading one long string out of a deep structure.