On-device AI — professional-grade, fully private.

Documents

How to View a JSON File Online (Open, Explore and Search Big or Nested JSON)

Open a .json file or paste JSON and read it as a collapsible tree or table. Search, copy a path, filter with JSONPath, and open files up to 100 MB on-device.

Updated November 7, 20269 min read

To view a JSON file online, drop it onto the JSON Tree Viewer or paste the text into the box. It appears as a tree you can open and close one branch at a time, so you can read a file that would be a wall of brackets in a text editor. Searching, copying a path and a table view for lists of records are built in. The file is read on your device, and the free plan opens files up to 100 MB.

Viewer, formatter or validator?

Three tools sit close together and people pick the wrong one. They answer different questions about the same text.

Your questionToolWhat you get
What is in this file and where is the field I need?ViewerA tree or table you can open, search and filter
Can I read it as plain text with proper indentation?FormatterThe same JSON as tidy, indented text
Is it valid, and where exactly is the mistake?ValidatorA pass or fail with the position of the error
How is this file different from that one?DiffA list of added, removed and changed values

If you only want the text tidied up, formatting JSON is the faster route. If you have two versions and want the differences, read comparing two JSON files. The viewer is for the moment when you do not yet know the shape of the data and need to explore it.

Open a JSON file and read it, step by step

1

Add the file or paste the text

Open the JSON Tree Viewer. Drop a file on the drop area, use Browse files, or paste into the box under Or paste JSON and choose View this JSON. The page accepts .json, .jsonl, .ndjson, .geojson, .har and .map files.

2

Read the summary line

Once the file opens you see how many nodes it has, how many levels deep it goes and its size. If the file repeats a key inside one object, or holds numbers with more digits than most tools keep, a badge says so. These often explain a bug before you look for it.

3

Open only what you need

Each object and array shows how many keys or items it holds. Click the arrow to open a branch. Open to depth with 1, 2, 3 or All sets the whole tree at once, and Collapse all takes you back to the top.

4

Find the field

Type in Find a key or value. You can search keys, values or both, turn on Match case or Regular expression, and step through the matches. Each step opens every branch above the match.

5

Copy what you came for

Select a row and use Copy path, Copy key, Copy value or Copy subtree. Or download the whole file, or just the selected branch, as formatted, minified, original or NDJSON.

Open any JSON as a tree or table, search it and copy any path. Free: one file at a time, up to 100 MB, with no limit on nodes or nesting depth. Pro: files as large as your device can handle and up to 10 files open at once. It all runs on your device, not our servers.

View a JSON file

Finding things in a large or deeply nested file

There are two different questions behind a search. One is where a piece of text appears. The other is what lives at a particular path. The viewer answers both.

Search is for the first question. Type a name, an ID or an error message and choose whether it matches keys, values or both. Matches are listed in document order and the count shows as, for example, 3 of 41. If you use a regular expression and it is not valid, the viewer says so rather than showing nothing.

The JSONPath filter is for the second. It narrows the tree to the nodes a path selects. A few expressions cover most needs:

  • **$.store.book[*].author** gives the author of every book.
  • $..price finds every key called price at any depth.
  • $.rows[0:10] shows the first ten items of an array.
  • $['odd key'] reaches a key with spaces or symbols in its name.

You can search inside a filtered view. That is useful when a path selects a thousand records and you want the three that mention one customer. If a path matches nothing, the viewer tells you so, which usually means a key is spelled differently from what you assumed.

When the JSON is a list of records: the table view

Most JSON that people open is a list of similar records, such as an API response, a database export or a log. In a tree that is hundreds of identical branches, and you can only compare them by opening each one. Switch View from Tree to Table and each record becomes a row, each field a column.

Columns are collected from all the records, not just the first one, so a field that only some records have still gets a column and the others show an empty cell. A value that is itself an object or array shows what it is and how much it holds. If the document has no list of records the Table option is unavailable and says so. If you want the rows in a spreadsheet, JSON to CSV converts them, and viewing a CSV file covers the other side.

Big files and how far the viewer goes

The free plan opens a JSON file up to 100 MB, one file at a time. There is no cap on the number of nodes or on how deeply the data nests. The viewer scans the file once and keeps an index of where everything is, then decodes only the rows you can see. That is why a large export scrolls smoothly instead of freezing the page.

FreePro
File sizeUp to 100 MBAs large as your device can handle
Files open at once1Up to 10
Nodes and nesting depthNo limitNo limit
Tree, table, search, JSONPath, exportIncludedIncluded

If a file is over 100 MB on the free plan, the viewer tells you its size and offers to minify it first. Minifying removes spacing and line breaks, which can shrink a heavily indented file a lot, though it cannot shrink data that is large on its own. Very big files also depend on your device. A phone with little free memory will cope with less than a desktop, whatever the plan.

Opening a JSON file someone sent you

A file that arrives by email or chat is often not quite what its name says. These are the situations that come up most.

  • One record per line. Files ending in .jsonl or .ndjson hold a separate JSON document on every line. The viewer presents them as one array, so you can browse, search and export the whole stream together.
  • A .har or .map file. A network capture or a source map is ordinary JSON with a particular shape. Both open like any other file.
  • Comments or trailing commas. Configuration files often have // comments, trailing commas, single quotes or keys without quotes. None of that is valid JSON. If a strict read fails, the viewer offers Tolerant mode and lists exactly what it changed, with the line of the first occurrence.
  • A different encoding. UTF-8, UTF-16 and Windows-1252 files are read, and a byte order mark at the start is handled instead of being treated as an error.
  • Not JSON at all. If the file looks like another format, the viewer says what it looks like and, for XML, YAML or CSV, links to the converter for it.

What the viewer shows that others hide

Many viewers turn the file into programming-language values before showing it, and that quietly changes some content. A number such as 12345678901234567890 can come back as 12345678901234567000, because ordinary numbers keep only about 15 significant digits. This viewer shows each number as the file wrote it and marks the ones that would not survive that kind of round trip. That matters for IDs, order numbers and anything money-related.

The same goes for repeated keys. JSON allows an object to contain the same key twice, and most tools keep only the last one, so a file that is quietly wrong looks fine. Here both entries are shown and flagged, and the summary gives the count. Exporting only changes whitespace, so your numbers, keys and escape sequences stay as they were.

Privacy and sharing

The file is opened, indexed, searched and exported on your device, not our servers, and nothing is kept after you close the tab. That makes it suitable for production exports, logs and other data you would not paste into a service that stores it. Once the page has loaded it keeps working without a connection.

When you need to show a problem to someone, copy the subtree instead of sending a 40 MB file. A single branch is much easier for a colleague to read.

Frequently asked questions

How do I open a JSON file?

Drop the .json file onto the JSON Tree Viewer, or choose Browse files, or paste the text into the box and choose View this JSON. It shows as a tree you can open branch by branch. Double-clicking the file on your computer usually opens a text editor instead, which gives you the raw text without the tree.

How large a JSON file can I view for free?

Up to 100 MB, one file at a time, with no limit on the number of nodes or how deeply they nest. Pro removes the size cap in favour of what your device can handle and keeps up to 10 files open at once.

Is my JSON uploaded anywhere?

No. The file is read, searched and exported on your device, not our servers, and nothing is stored after you close the tab.

Why does it say my file is not valid JSON?

The message gives the line and column and shows the text around the problem. Common causes are a trailing comma, a comment, single quotes or a file cut off in the middle. For comments, trailing commas and quote problems, Tolerant mode can read the file and report what it changed. A truncated file has to be fixed at the source.

How do I find one value in a huge JSON file?

Use Find a key or value to search keys, values or both, with Match case or a regular expression if you need them. Or use the JSONPath filter, for example $..price, to list every price at any depth. Then use Copy path on the row you need.

What is the difference between a JSON viewer and a JSON formatter?

A viewer lets you explore the structure by opening and closing branches, searching and filtering. A formatter only re-indents the text. Use the viewer to find your way around an unfamiliar file and the formatter when you want clean text to paste somewhere.

Keep reading

More in Documents →