Format, beautify, minify and validate JSON online. Drop or select a file to load it, download the result as .json or .csv, and nothing is uploaded - your file never leaves the browser. We impose no size limit: a single 5 MB file took 47.6 seconds in our test.
Drop several .json files here, or
Each file is processed in this browser. Nothing is uploaded.
| # | File | Size | Result |
|---|
Yes. Switch to Batch - multiple files, then drop or choose several files. Each one is processed in your browser, and the results can be downloaded together as a .zip. When we tested it, 40 files were processed in 0.2 seconds and packed into the .zip in 0.4 seconds.
No. Every operation runs as JavaScript on your own device. We watched the network activity while formatting and while building the .zip: the page sent nothing to any third party.
We do not set one. In our test a single 5 MB file was formatted in 47.6 seconds in this browser. Whether larger files work depends on how much memory your device has, so we do not promise a number we have not measured.
Yes, when the JSON is an array of objects or a single object. Columns are written in first-seen order, nested objects and arrays are kept as JSON text inside their cell, and a UTF-8 BOM is added so Excel reads accented and CJK characters correctly. If the JSON cannot be tabulated, the page says so instead of writing a file that looks fine but means something else.
Yes. In batch mode choose Merge into one JSON file. If every file holds an array, those arrays are joined into one array. If they do not all hold arrays, each file becomes one element of the output array. Either way the status line tells you which rule was applied.
The page reports the line and column, shows the offending line with a caret pointing at the problem, and quotes the parser's reason. In batch mode a file that fails is listed as Invalid and left out of the download, while the rest still go through.
No account, no sign-up, no watermark. There is no server counting your requests, so there is no usage limit to hit.
Yes. Files written by Windows tools such as Notepad and PowerShell often begin with a byte-order mark, which the browser's own JSON parser rejects. The BOM is removed before parsing, so those files open normally. Nesting depth is the one limit we ran into: 1,000 levels was fine, but at 10,000 levels the browser ran out of call stack - the page reports that and clears the output instead of leaving an old result on screen.