How to Validate JSON: Syntax, Schema, and Real-World Checks

Two Levels of JSON Validation

There is a big difference between "is this valid JSON?" and "does this JSON match the shape my API expects?". Both matter.

Syntax validation catches trailing commas and mismatched braces. Schema validation catches missing fields, wrong types, and business-rule violations. Ship both in production pipelines.

Syntax Validation: Quick and Easy

The fastest check is a JSON parser. If parse fails, your JSON is invalid.

try {
  const data = JSON.parse(text);
} catch (err) {
  console.error("Invalid JSON:", err.message);
}

import json
try:
    data = json.loads(text)
except json.JSONDecodeError as e:
    print("Invalid JSON:", e.msg, "line", e.lineno, "col", e.colno)

jq . data.json > /dev/null && echo OK || echo BAD

Schema Validation with JSON Schema

JSON Schema is a small JSON vocabulary that describes what valid JSON looks like. It powers OpenAPI, Ajv, and most production validation.

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "required": ["order_id", "email", "amount"],
  "properties": {
    "order_id": { "type": "string", "pattern": "^[0-9]+$" },
    "email":    { "type": "string", "format": "email" },
    "amount":   { "type": "number", "minimum": 0 }
  },
  "additionalProperties": false
}

import Ajv from "ajv";
import addFormats from "ajv-formats";
const ajv = new Ajv({ allErrors: true });
addFormats(ajv);

const validate = ajv.compile(schema);
if (!validate(data)) {
  console.error(validate.errors);
}

from jsonschema import validate, ValidationError

try:
    validate(instance=data, schema=schema)
except ValidationError as e:
    print("Invalid:", e.message)

Common JSON Errors You Can Prevent

The same three culprits produce most parse errors.

• Trailing commas inside objects and arrays.
• Single quotes instead of double quotes.
• Unquoted keys (a JavaScript object literal habit).
• Unescaped newlines inside strings.
• Duplicate keys inside the same object.

Validating CSV-Derived JSON

When JSON comes from a spreadsheet or CSV export, expect these headaches: string "true" instead of boolean true, IDs that are strings and numbers in the same file, and missing fields for optional columns.

Use a schema with type coercion turned off so you catch these at ingest instead of later.

Real-World Examples

Where validation pays off.

Common Mistakes

The habits that cost teams the most time.

• Only validating syntax and skipping schema.
• Writing schemas without required/enum/pattern.
• Ignoring additionalProperties and letting typos through.
• Turning off strict mode to make errors go away.
• Validating on the way out of your app instead of on the way in.

Best Practices

The playbook that scales.

• Validate at every trust boundary.
• Keep schemas in version control next to the code they protect.
• Return field-level errors, not "invalid input".
• Prefer Ajv (JS) or jsonschema (Python) over hand-rolled checks.
• Reject unknown fields unless you explicitly allow them.

Why Use Convert CSV Online?

Convert CSV Online is free, browser-based, and requires no account for everyday conversions. Turn CSVs into JSON and inspect them in the Online CSV Editor. Once the JSON parses cleanly, run schema validation in your app to catch shape errors. Client-side workflows work on Windows, macOS, and Linux browsers.

Conclusion

Validate JSON syntax with the built-in parser and validate shape with JSON Schema. The two checks together catch almost every real-world bug before it becomes a production incident.