Int64 and exact decimals
IDs beyond 2^53 survive paste → view → edit → copy → download with every digit intact. Nothing is coerced to a float, ever.
Five-million-element arrays open instantly. Int64 IDs and exact decimals survive paste → edit → copy without a single rounded digit. Diff, query, decode Zstd payloads, export CSV — all inside your browser tab.
0 bytes uploaded · no account · MIT
IDs beyond 2^53 survive paste → view → edit → copy → download with every digit intact. Nothing is coerced to a float, ever.
Virtualized tree with chunked expansion — [0 … 9999] range rows — and parsing, diffing, search and compression all off the UI thread.
Raw .zst, Base64-Zstd, or PostgreSQL \x… bytea is detected, decoded in the worker, and opened with a transformation trace.
Arrays align by identity, so reordering does not drown you in false changes. Ignore noisy fields by key or path prefix.
Copy any node as JSONPath, JSON Pointer, or JS accessor. Epoch → local date, lat/lng, uuid flags, and byte weight on collapsed nodes.
Any array becomes a sortable table; export the table or a query result as exact-digit CSV in the current sort order.
Filter, pluck, group and count across the whole document — evaluated in the worker, never on the main thread.
$.tasks[?(@.status == 'FAILED')]
| group(@.failureReason)
| count()
Align arrays by id, a composite key, or automatic detection — then read what actually changed instead of a wall of index shifts.
Parsing, diffing and querying run in a web worker; documents are stored in IndexedDB on your own disk. There is no server to send them to. Ask — the optional English-to-query feature — stays off until you add your own API key, and even then it sends only the document's shape: field names and types, never values, shown to you in full before anything is sent.