Semver Comparator
Compare two semantic versions and test them against a range.
Check JSON syntax and get the exact line, column and cause of any error.
The JSON Validator checks a document for syntax errors and reports the exact line, column and cause of the first failure, with the offending line reprinted and a caret under the character that broke it. Valid documents get their structure measured instead.
Paste a document and the validator tells you one of two things: that it parses, or exactly where it stops parsing. The error is reported with a line number, a column number and the offending line reprinted with a caret under the character that broke it.
Most invalid JSON fails for one of five reasons, and the validator names which one: a trailing comma after the last item in an object or array, keys or strings wrapped in single quotes, an unquoted key, an unescaped line break inside a string, or a bracket that was never closed. When the document is valid you also get its statistics — key count, nesting depth, node count and a breakdown of how many strings, numbers, booleans and nulls it holds.
The failing line is reprinted with a marker under the exact character, so you fix the problem instead of hunting for it.
Trailing commas, single quotes, unquoted keys and unclosed brackets are named as such rather than reported as a generic parse error.
A valid document reports its key count, node count, maximum nesting depth and a breakdown of value types.
The verdict updates on every keystroke, so fixing an error and confirming the fix is one continuous action.
Validation uses the browser's own JSON parser, so tokens and personal data inside a payload never leave your machine.
Drop in an API response, a config file or any string you believe is JSON.
A green note means it parses. A red one names the line, the column and the likely cause.
Correct the character the caret points at. The verdict updates as you type.
Once valid, check the depth and key count to see whether the structure is what you expected.
A trailing comma. JavaScript object literals allow one after the last item and JSON does not, so anything copied out of a code editor tends to carry one.
JSON only recognises double quotes around keys and string values. Single quotes are valid JavaScript but not valid JSON, so a parser rejects them immediately.
No, this one checks syntax only. Use the JSON Schema Validator when you need to confirm that the shape and the value ranges are also correct.
No. Parsing happens in your browser with the built-in JSON parser, so tokens and customer records inside a payload never leave your machine.
What people who use the JSON Validator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the JSON Validator. It takes half a minute and no account.
Write the first reviewCompare two semantic versions and test them against a range.
Build text shadows, outlines and glows with a live preview.
Convert between px, rem, em, pt, %, vw and vh with the right context.
Render Markdown to clean HTML, with tables, task lists and fenced code.
Convert a name between camelCase, snake_case, kebab-case and the rest.
Generate Java POJOs or records with Jackson annotations from JSON.
Turn a .env file into JSON, with quotes, exports and comments handled.
Percent-encode URLs and query strings, or decode them back to plain text.