How to open a large JSON file without crashing your browser or editor

A big JSON response or export — tens or hundreds of megabytes — will freeze most text editors, lock up a browser tab, or get truncated by online formatters. Here are practical ways to actually read it.

1. Inspect it from the command line

If you just need to peek at the structure or pull out part of it, the terminal is fastest because it streams instead of loading everything into a UI.

# pretty-print and page through it
jq . big.json | less

# see just the top-level keys
jq 'keys' big.json

# pull one slice (e.g. the first 5 items of an array)
jq '.items[0:5]' big.json

jq handles large files well and lets you extract exactly what you need. less opens even multi-gigabyte files instantly because it doesn't read the whole thing at once.

2. Split it into smaller pieces

If the file is a giant array and you want chunks you can open normally:

# one object per line, then split into 10k-line files
jq -c '.[]' big.json | split -l 10000 - chunk_

3. Open it in a viewer built for large files

When you want to actually browse the data — expand and collapse the tree, search keys and values, jump around — most online JSON formatters fall over because they try to render the entire document into the page at once. A viewer that renders the tree incrementally (building each level only as you expand it) stays responsive even on very large files.

The free JSON viewer on this site is built exactly for this: it loads the tree in chunks, so multi-megabyte files open without freezing. It runs entirely in your browser — the file is never uploaded anywhere — and includes instant search across keys and values. Open it, paste the JSON or choose the file, and start exploring.

4. Extract or convert instead of opening the whole thing

Often you don't need the entire file — you need a table or a subset. Two quick options:

Turn an array of objects into a spreadsheet with the JSON → CSV converter.
Pull a specific path out with the JSONPath tester (e.g. data.items[*].id).

Which should you use?

For a quick look or scripted extraction, reach for jq. To read and navigate the data by hand, use a chunked browser viewer. To hand the data to a spreadsheet or another tool, convert the part you need. All three avoid the core problem: never force the whole file into a UI that wasn't built for it.