Format data without changing its tokens
A long tracking ID can lose digits when a formatter converts it to a JavaScript number. This tool reads JSON syntax without converting numeric values. It also leaves key order and duplicate entries intact, so formatting does not silently decide which value should win.
How to use it
- Paste your JSON and choose Pretty print or Minify.
- Select Validate and format. If an error appears, use its line and column or Go to error to select the source character.
- Review the output, then copy it or download a JSON file. Editing the input clears the old result; run the tool again.
What changes
A large-ID example
For {"id":9007199254740993,"ratio":1.2300e+02}, both number spellings stay unchanged. For {"a":1,"a":2}, both entries remain and a duplicate-key warning appears. Before importing the file, check how the receiving application handles these values.
Error positions and downloads
Lines and columns start at 1. Columns count UTF-16 code units, so an emoji can occupy two positions. Go to error selects the relevant character, or the end of input for an end-of-document error. Downloads contain UTF-8 JSON with no added BOM.
Questions and limits
Does valid JSON mean my API will accept it?
No. Required fields, schema types, business rules and authentication are not checked. JSONPath browsing, key sorting and automatic repairs are not currently provided.
Are comments or trailing commas accepted?
No. This strict JSON workflow rejects comments, trailing commas, single-quoted keys and a leading BOM. Process JSONL documents one at a time.
Will every program interpret the output identically?
No. Number limits and duplicate-key handling vary. Escaped unpaired surrogates remain as written and may cause interoperability problems. Passing this syntax check is not a compatibility guarantee.
Syntax reference: RFC 8259 · JSON Pointer · RFC 6901 · Feature and syntax reference checked: