Frequently asked questions
What counts as valid JSON?
JSON follows a strict standard (RFC 8259). Property names and text values must use double quotes, items are separated by commas with no comma after the last one, and comments are not allowed. Values can be objects, arrays, text, numbers, true, false or null. JavaScript habits such as single quotes, unquoted keys, trailing commas, NaN and undefined are errors in JSON.
Will formatting change my data?
No values are changed. Numbers are kept exactly as you wrote them, so a large ID such as 9007199254740993 stays intact (many tools silently round it), and 1.10 stays 1.10. Properties stay in their original order unless you turn on Sort keys. Text may be re-escaped, for example \u00e9 becomes é, which means the same thing.
How do I find what is wrong with my JSON?
When the JSON is invalid, the tool shows the line and column, the line itself with a marker, and a short explanation such as a missing comma, a trailing comma, single quotes or an unclosed bracket. The most common causes are a missing or extra comma, single quotes instead of double quotes, and a missing closing bracket.
Does it warn about duplicate keys?
Yes. JSON allows the same key twice in an object, but most programs keep only the last value and silently drop the others. The tool keeps both in the output and lists the duplicate keys so you can decide.
Is my JSON uploaded or stored?
No. Everything runs inside your browser, so your data never leaves your device. Our server only records that one operation was formatted, along with your network address, so the daily limit shown above the tool can be applied.







