A trailing comma
{
"name": "Ann",
"age": 31,
}Invalid JSON — line 3, column 12: Trailing comma before “}”. Remove the comma after the last property.Paste JSON and know immediately whether it is valid. If it isn’t, the validator shows the exact line and column, highlights the problem and explains how to fix it — including the classic mistakes like trailing commas, single quotes, comments and unquoted keys.
{
"name": "Ann",
"age": 31,
}Invalid JSON — line 3, column 12: Trailing comma before “}”. Remove the comma after the last property.After fixing the quotes, the validator then flags True and None and suggests the lowercase JSON values true and null.
{'active': True, 'tags': None}Property names must use double quotes. Replace single quotes with double quotes.JSON (RFC 8259) is stricter than JavaScript. Keys and strings must use double quotes; the only literal values are true, false and null; numbers can’t have leading zeros, a leading plus sign or trailing decimal points; and comments and trailing commas are not allowed. The validator follows the standard exactly, so JSON it accepts will be accepted by any compliant parser.
No. Validation runs entirely in your browser; your data never leaves your device.
The JSON standard has no comment syntax. Some tools accept “JSON with comments” (JSONC) for configuration files, but standard parsers and APIs reject it.
The standard doesn’t forbid them, so the JSON is reported as valid, but you’ll see a warning: most programs keep only the last value, which usually isn’t what was intended.
No — it checks syntax, which is what most errors are. Schema validation (checking required fields and types) is a separate step done by your application.
Everything you need. One simple place.
Free, fast online tools for text, PDFs, images, data and everyday maths. Every tool runs entirely in your browser, so your files stay on your device.
© 2026 Toolora. All rights reserved.
Built for speed and privacy