Format JSON without rounding a large ID

A formatted API response should be easier to read without changing its identifiers. JavaScript numbers cannot represent every large integer exactly, so a parse-and-stringify shortcut can change data even when it looks like a whitespace operation.

Keep numeric tokens intact

Consider {"id":9007199254740993}. The formatter retains the exact numeric token rather than converting it to a JavaScript number and back. Pretty print adds two-space indentation; Minify removes structural whitespace. String escapes, number spelling and object property order stay as written. Use quoted strings for identifiers in new API designs when you control the format.

Resolve syntax problems first

Paste a complete value or import UTF-8 JSON/TXT, up to 100,000 characters / 400 KB. Check the reported line and column if validation fails. Comments, duplicate keys and trailing commas are rejected rather than fixed by guessing. A syntax pass is not a JSON Schema or API contract check.

Select a precise subtree

For {"users":[{"name":"Ada"}]}, the pointer /users/0/name extracts the JSON string "Ada". A slash inside a property name is ~1 and a tilde is ~0. An empty pointer selects the root; / selects an empty-string property. Array indexes are zero-based. Missing paths produce an error rather than an empty result.

Download and compare the final source

Inspect the full result and download JSON. Both scalar roots and nested objects are valid outputs. There is a 100-level nesting limit and 4 MB output cap. Changing the input or pointer discards the previous result, so format again after the last edit. The tab keeps no persistent document history.