# JSON Studio — Formatter & Validator

Paste JSON to format, minify or validate it instantly. Errors are shown with the exact line, column and cause, and comments or trailing commas can be auto-repaired. Your data never leaves your device.

- URL: https://tools.itlibra.com/en/json-studio
- On-device・No upload
- Last updated: 2026-10-31

## How to use

1. Paste JSON into the input pane, or click “Open file” to load a .json file (drag & drop works too).
2. Choose a mode: Format, Minify, Tree view, String escape or JSON Lines. The result updates as you type. JSON Lines (one JSON value per line) is checked line by line, and broken lines are listed by number.
3. Adjust indentation, key sorting or non-ASCII escaping if needed.
4. If there is an error, check the reported line and column, use “Go to error” to jump there, and try “Auto-repair and retry” if appropriate.
5. Copy the result or download it as a file.

## Use cases

- Make an API response or config file readable
- Find the exact cause of an “Unexpected token” error
- Turn JavaScript objects or commented JSONC into valid JSON
- Format JSON containing 64-bit IDs without losing digits
- Embed text with line breaks and quotes as a JSON string

## What it does

### Lossless number handling

Tools built on JSON.parse round integers above 9,007,199,254,740,991 (2^53 − 1) and long decimals. Our own parser keeps every number exactly as written, so order IDs and other large values never change.

### Precise error reporting

Syntax errors show the line, column, what was expected and what was found, with a marked excerpt. “Go to error” selects the exact spot in the editor.

### Auto-repair for JSONC / JSON5-style input

Converts comments, trailing commas, single quotes, unquoted keys and NaN/Infinity into valid JSON — and lists every repair it made.

### Tree view with path copy

Explore large documents in a collapsible tree and copy the JSONPath of any value (e.g. $.items\[0\].sku) in one click.

### Duplicate key detection

Flags repeated keys, which JSON technically allows but which often cause subtle bugs.

### Stays responsive with big files

Processing runs in a background Web Worker, so multi-megabyte JSON does not freeze the page.


## Supported formats

### Input

- JSON
- JSONC (comments)
- JSON5-style syntax (auto-repair)
- JSON Lines (.jsonl / .ndjson)
- .json
- .geojson
- .webmanifest
- .map
- UTF-8 / UTF-16 (with BOM)

### Output

- Formatted JSON (2 / 4 spaces, tab)
- Minified JSON (one line)
- JSON string literal
- JSON Lines (one value per line)
- JSON array


## Capability matrix

| Feature | Support | Notes |
| --- | --- | --- |
| Format & minify (2 / 4 spaces, tab) | Supported | — |
| Syntax validation with line/column | Supported | — |
| Exact large numbers (integers above 2^53, long decimals) | Supported | Output exactly as written |
| Auto-repair comments, trailing commas, etc. | Supported | Repairs are listed |
| Sort keys alphabetically | Supported | Applied to nested objects |
| Tree view & JSONPath copy | Supported | — |
| Duplicate key detection | Supported | — |
| JSON Schema validation | Not supported | Syntax only |
| JSON Lines (one JSON per line) check & format | Supported | Each line is checked; broken lines are listed by number and reason. Converts to and from JSON arrays |
| Offline use | Supported | Works without a connection once loaded |

## Limits & notes

- Files up to 50 MB can be loaded. Above one million characters, auto-run pauses and you press “Run”.
- Nesting is limited to 1,000 levels to keep the browser from hanging on pathological input.
- The tree view shows 200 entries per level at a time (use “Show more”).
- Key sorting uses code-point order, not numeric order.
- Auto-repair involves guesses — always review the repaired output.
- JSON Lines is limited to 200,000 lines. LF and CRLF line breaks are supported; a CR-only file is read as one line. Non-UTF-8 encodings (such as Shift\_JIS) are not read correctly.

## Privacy & safety

Your JSON and files are processed only inside your browser. Nothing is sent to or stored on any server, so you can safely format data that contains API keys or personal information. Closing the page discards everything.

## FAQ

### How do I fix an “Unexpected token” JSON error?

It is usually a missing or extra comma, a missing closing bracket, or an unclosed string quote. Paste the JSON here to see the line, column and expected character. If comments or trailing commas are the cause, “Auto-repair and retry” fixes them.

### Why do large numbers (IDs) change in other tools?

JavaScript numbers are exact only up to 9,007,199,254,740,991 (15–16 digits), so tools using JSON.parse round values like 9007199254740993. This tool keeps numbers as text, so formatting never changes them.

### Can it handle JSON with comments (JSONC)?

Yes. Turn on “Auto-repair” and // or /\* \*/ comments are removed, producing valid JSON — handy for files like tsconfig.json.

### Is my data sent to a server?

No. Everything runs in your browser; your input is never sent to LIBRA Works or any third party.

### What is the difference between formatting and minifying?

Formatting adds line breaks and indentation for readability; minifying removes unnecessary whitespace to make the file smaller. The data itself does not change.

### Where are the broken lines in a JSON Lines (.jsonl) file?

Switch to the “JSON Lines” mode. Each line is checked, and broken lines are listed with their line number, column and reason. Turn on “Output without broken lines” to write only the valid lines; the number of lines left out is shown.
