What Is JSON? Values, Syntax, And Interoperability

Understand JSON values, object members, arrays, number grammar, duplicate-name risks, Unicode strings, and the difference between syntax and application validity.

Need To Check A Conversion?

Use the JSON Formatter tool for the direct action. This guide stays focused on the explanation, tradeoffs, mistakes, and reference context behind that task.

JSON Text Contains One Serialized Value

RFC 8259 defines JSON text as a serialized value. An object or array is common, but a string, number, true, false, or null is also a complete JSON text.

JSON syntax uses double-quoted strings, a fixed number grammar, arrays, objects, and three literal names. Comments, trailing commas, NaN, Infinity, and single-quoted strings are outside the grammar.

Syntax Versus Meaning

Question JSON syntax can answer A schema/application must answer
Does it parse? Yes Not needed
Is a field required? No Yes
Is a duplicate name acceptable? Syntax permits it Consumer policy decides
Is a number exact in the destination? Grammar only Numeric model decides
May this user submit it? No Authentication and authorization decide

Interoperability Is Narrower Than Syntax

Object member names should be unique for interoperable exchange even though the grammar does not reject repetitions. Consumers may keep the first value, keep the last, expose every pair, or fail.

JSON numbers can contain more digits or a larger exponent than a receiving numeric type can represent. Keep identifiers as strings when numeric arithmetic is not intended, and test the destination before relying on very large values.

Practical Review Checklist

  • Validate one complete value before formatting or converting it.
  • Preserve source text when number spelling, duplicate members, escaping, signatures, or hashes matter.
  • Use a schema or application validator for fields and business rules.
  • Treat parsed data as untrusted until the consuming context validates it.

Related Tools

Developer

JSON Validator

Check complete JSON syntax and surface interoperability warnings without claiming schema validation.

 Developer

JSON Minify

Remove only insignificant JSON whitespace without materializing large numeric values.

 Developer

JSON to CSV

Map an array of flat JSON objects into a declared CSV table profile.

References

Related Guides In This Category

CSV vs Excel vs JSON: Choosing the Right Data Format

Choose a tabular or structured format with formula-cache and numeric-fidelity limits visible.

JSON Formatter vs Validator vs Minifier

A task-selection guide for three operations that share a parser but answer different questions.

Browse More Developer Guides

Need the broader support library for this topic? Visit Developer Guides for related references, comparisons, and practical background before returning to the exact tool.

Explore The Full Category

Need another related task? Open Developer Tools for the full tool set, quick-reference examples, and related category paths.