A LITTLE CLARITY FOR YOUR DATA

JSON validator. A little confidence.

Find JSON syntax errors, see where they happen, and get a practical suggestion to fix them.

Your workspace

JSON

Input

Your JSON goes here

18 lines·376 BUTF-8

Output

JSON

{
  "project": "jsonformatkit",
  "description": "A little clarity for your data",
  "version": "1.0.0",
  "isAwesome": true,
  "tools": [
    "Format & validate",
    "Convert & explore",
    "Share something beautiful"
  ],
  "settings": {
    "indentation": 2,
    "sortKeys": false,
    "privacy": "Your data stays yours"
  },
  "madeWith": "care",
  "nextBigIdea": null
}

Formatted JSON376 B

Ctrl↵

Looking good. Your JSON is valid.

Object with 11 keys. All brackets, quotes, and commas are in their happy place.

VALID JSON

All done? Take it with you.

Copy your result or download it in a click.

GO A LITTLE FURTHER

More than a pretty print.

A QUICK FIELD GUIDE

Find JSON syntax errors and understand the fix

A missing comma, an unclosed string, or one extra bracket can stop an API payload or configuration file from parsing. This JSON validator checks standard JSON syntax and shows the first error with a line, column, and a suggested correction.

JSON property names and strings need double quotes. Allowed values are strings, numbers, objects, arrays, true, false, and null. Comments, undefined, NaN, and Infinity are not valid JSON values. Trailing commas are also invalid.

Select the error location to focus the input near the problem. Fix the reported issue and validate again to find any remaining errors. A syntax check confirms that a document can be parsed; use the JSON Schema validator when you also need to enforce field types or required properties.

How to use JSON validator

Paste or upload the JSON you want to check.
Select Validate JSON to check syntax.
Read the suggested fix, use the line and column link, and validate again after correcting the input.

Up to 2 MB of JSON and 100 nesting levels. URL imports require public HTTPS sources with CORS enabled.

A small example

INPUT

{"name" "Ada"}

RESULT

Missing colon after a property name.
Fix: {"name": "Ada"}

Frequently asked questions

Does valid JSON have to be an object or array?

No. A top-level string, number, boolean, or null is valid JSON too. An API may require an object, but that is a separate data-contract requirement that can be checked with JSON Schema.

Does the validator automatically repair my data?

No. It reports the issue and suggests a fix, leaving you in control of the document. Automatic repairs can change intended values, so the tool does not guess and overwrite invalid input.

Does syntactically valid JSON guarantee the correct types?

No. Both a number and a quoted numeric string can be valid JSON. Use a schema with type constraints to check whether a field has the expected type or whether a required property is missing.

Built around open standards: JSON (RFC 8259), JSON Schema, and YAML 1.2.