About JSON Loomly
JSON Loomly is a workbench for JSON documents: paste one, drop a file, or load the sample, and then format, sort, flatten, convert, inspect or compare it. It exists because most of those jobs are one-liners in a terminal and awkward everywhere else — and because the browser is already a perfectly good place to run them.
Nothing you paste or open is uploaded. The page is a static export with no backend, no API routes and no analytics; parsing and every transform run in a Web Worker on your own machine. You can confirm it the blunt way: load the page, switch off your network, and keep working — everything still runs, because there was never a round trip to make.
The three guides on this site are written by the same people. They cover the parts of the job a formatter cannot do for you: which JSON rules break files, what flattening does to arrays and nulls, and when a CSV is the better answer than a JSON.
It is built and maintained by Interhive OÜ, a small studio in Tallinn that makes tiny, dependable web tools.
What it does
- Read and repair
- A CodeMirror editor with line numbers, folding, bracket matching and search, plus a validator that reports the line, the column and the reason in plain language. A JSONC toggle accepts comments and trailing commas from configuration files.
- Reshape
- Format with two spaces, four spaces or tabs; minify to one line; sort object keys alphabetically and recursively without touching array order; flatten nested data into dot or bracket paths and unflatten it back.
- Convert
- JSON to CSV with a choice of delimiter and path style for nested columns, CSV to JSON with optional type inference, a JSON Schema draft 2020-12 inferred from the document, and TypeScript interfaces with optional properties marked.
- Inspect and compare
- A collapsible tree where clicking a key copies its path, a stats panel with size, depth, key counts and the most frequent keys, and a structural diff of two documents that ignores key order and formatting.
Get in touch
Found a bug, hit a document the parser mishandles, or want a transform that is missing? Email us and include the input if you can share it.
support@interhive.org