Free JSON Viewer for Large Files (Tree, Graph, Search)

To view a large JSON file, open it in the free JSON viewer instead of a text editor. Drop in a .json file up to 20 MB and you get a collapsible tree with counts for every object and array, a search box for keys and values, and a graph view of how the pieces connect. Click any field to copy its path, like $.items[2].sku. Nothing is uploaded, so production dumps and customer data stay on your device.

A 5 MB API response is roughly 5 million characters on one line. Scrolling through that in an editor tells you nothing. A tree shows you the shape first, then lets you drill into just the part you care about.

Open the file

1. Go to the free JSON viewer.
2. Drop your file on Open a .json file, or paste JSON into Your JSON. Files up to 20 MB open.
3. Wait a moment for "Reading your JSON…" to finish. Very large files take a second or two.
4. Read the four numbers at the top: Values, Keys, Depth and Size. They tell you what you're dealing with before you open anything.

Files over about a million characters aren't put into the edit box (editing that much text in a browser gets slow). You'll see "too big to edit here, but you can explore all of it below", and the tree and graph work as normal.

If the JSON is broken, you get the line and column of the first mistake, the line itself with a ^ under the problem, and a plain reason such as a missing comma. That matters with big files, where finding the error by eye is hopeless. Truncated downloads are the usual cause: the file just stops mid-object.

Explore the tree

The Tree view opens the first few levels of a normal file. For a very large one (over 50,000 values) it opens only the top level, so the screen isn't flooded. Each object shows {n} and each array [n], the number of entries inside. That alone answers questions like "how many orders came back?".

• Click + to open one level, or use Open to level to open everything down to level 2 or 3 at once.
• Expand all and Collapse all do what they say. On a large file, Open to level is usually more useful than Expand all.
• With the tree focused, the arrow keys move up and down, right opens and left closes.

A good routine for an unknown API dump: press Collapse all, then open to level 2, find the big array (the one with [5000] next to it), open its first item, and you now know the shape of every record.

Search keys and values

Type in Search keys and values. Matching rows are highlighted and the counter shows "1 of 37". Press Enter (or the down arrow button) for the next match and Shift+Enter for the previous one. The tree opens to show each match.

Search is case-insensitive and matches part of a key or value, so email finds email, billing_email and any value containing "email". It's useful for:

• Finding where a specific ID appears: paste ord_8f3a21 and step through every place it's referenced.
• Checking whether a field exists at all in a 10,000-record export.
• Spotting nulls: search null to jump between empty values.

Copy the path to any value

Click a row and its path is copied, for example $.customer["loyalty points"]. Keys with spaces or symbols use the bracket form; array items use [0], [1] and so on. Paths start with $, the JSONPath convention.

Below the tree, the selected value panel shows the path, a preview of the value, and buttons for Copy path, Copy value and, for objects and arrays, Show as graph.

Copied paths drop straight into code with small edits. $.items[2].sku is data.items[2].sku in JavaScript, and data["items"][2]["sku"] in Python.

See the structure as a graph

Switch to Graph to see each object or array as a box listing its fields, with lines to the boxes nested inside. Drag to move around, use + and − to zoom, and Fit to see it all.

On a big file the graph draws the first 2,000 boxes, and long lists show their first 25 items per box, with a note telling you so. To see one branch in full, select it in the Tree view and choose Show as graph. Show the whole document takes you back. In practice the graph is best for understanding nesting (which object holds which), and the tree is best for reading values.

JSON viewer, formatter or something else?

You want to...	Use
Explore, search, copy paths	JSON viewer
Pretty-print or minify the text, then copy it	JSON formatter; see how to format and validate JSON
Open it in Excel	JSON to CSV; see JSON to CSV for Excel
Read what's inside a token	JWT decoder
Start from an XML export	XML to JSON converter, then view it here

A note on big numbers

Like nearly every browser-based tool, the viewer reads numbers with JavaScript, which can't hold whole numbers above 9,007,199,254,740,991 exactly. A 19-digit ID stored as a number will show slightly wrong last digits. If your API returns IDs that long, ask for them as strings. The original file is unchanged; only the display is affected.

Open yours now

Drop your file into the free JSON viewer, open it to level 2, and search for the field you need. It works on files up to 20 MB, entirely on your device.