Try it

Sample documents · open any of them in a tab

Each link below is an ordinary JSON URL. With Bonsai installed, opening one hands you the viewer — folding, the structure tree, real search. Without it, you get exactly what your browser has always shown you, which is rather the point. Open a couple of them both ways.

The documents

general.json 3 KB · 120 lines

Mixed content. Every kind of JSON value in one document: nested objects five deep, arrays, empty containers, null, unicode and right-to-left text, escaped quotes and newlines, keys containing dots, spaces and emoji. Also the numbers that most tools quietly ruin — an integer past 2⁵³ and a long decimal — which Bonsai shows back to you byte for byte.
array.json 6 KB · 12 records

A top-level array. The structure panel indexes the rows rather than naming them, so this is the one to try the copy-path actions on: any row gives you its JSONPath, dot or bracket path.
empty.json 3 bytes

The degenerate case. A single empty object. Small, but the kind of document a viewer can easily render as a blank page.
malformed.json 863 bytes

Deliberately broken. Missing commas, single quotes, a trailing comma, an unclosed bracket. It still renders, with the first error marked at its exact line and column — instead of the blank page you would otherwise be debugging.
long.json 1.9 MB · 79,059 lines

A long document. An event log of 2,000 records — the size at which a raw browser tab stops being usable and scrolling to find anything becomes hopeless. Fold the events array, then search the whole file for PaymentDeclined.
very-long.json 8.7 MB · 355,746 lines

A very long document. The same log with 7,000 records. Rendering is virtualized and search is time-budgeted, so folding, jumping through the tree and searching stay responsive at a size where a browser tab normally does not. This is the one to judge the extension on.

Things worth trying

Search past the fold — open very-long.json, collapse everything, then search. Matches inside folded and off-screen content still count, which the browser's own find cannot do.
Copy a path — right-click any row in the structure panel and copy it as JSONPath, dot or bracket notation, ready to paste into code.
Go back to the raw document — one click returns the tab to the original bytes, unchanged.
Save one and open it locally — these work just as well from file:// once you allow file access, or drop the file straight into the viewer.

The data is synthetic: no real people, orders or payments are described in any of these files.