What is a JSON parser?

A JSON parser reads JSON text and identifies its objects, arrays, property values, and primitive data types. This parser presents those values as a document-order table, making it easier to inspect nested API responses, configuration files, logs, and exported data without manually tracing braces.

Each row shows where a value appears in the document, what type it is, and how to address it with a JSON Pointer. The source text stays unchanged.

How to parse JSON online

Paste or type strict JSON in the input editor, or select Example.
Select Parse JSON.
Review the root type and summary, then inspect each node’s JSON Pointer, type, preview, depth, and source position.
Use the copy action beside a row when you need its JSON Pointer.

If the input is invalid, select a diagnostic to move the editor to the reported line and column. Editing the source clears the previous table so the results never describe an older version of the document.

JSON parsing example

The built-in example includes every JSON data type:

{
  "project": "Bitty Coder",
  "release": 1,
  "active": true,
  "tags": ["json", "parser"],
  "settings": {
    "theme": "system",
    "note": null
  }
}

After parsing, the first row represents the root object. /tags identifies the array, /tags/0 identifies its first string, and /settings/note identifies the null value. The table follows the same order as the original document.

What does the parser table show?

Column	Meaning
JSON Pointer	A standard path that identifies the node. The root Pointer is an empty string and is displayed as `(root)`.
Type	One of `object`, `array`, `string`, `number`, `boolean`, or `null`.
Value summary	A property or item count for containers, or a compact source preview for primitive values.
Depth	How many object properties or array indexes lead from the root to the node.
Position	The one-based line and column where the value starts in the original input.

JSON Pointer escapes ~ as ~0 and / as ~1 inside property names. For example, a property named a/b appears as /a~1b.

JSON parser vs viewer, formatter, and validator

Tool	Primary purpose
JSON Parser	Inspect every parsed node with its Pointer, type, depth, preview, and source position.
JSON Viewer	Browse valid JSON as a collapsible tree.
JSON Formatter	Add readable indentation and line breaks to JSON text.
JSON Validator	Check strict JSON syntax and review diagnostics without creating a node table.
JSON Repair	Correct common non-standard or damaged JSON, then review the result.

Parsing and viewing both reveal structure, but they serve different tasks. Use the Parser when exact paths and source positions matter; use the Viewer when you want to open and close branches visually.

JSON data types and root values

JSON supports objects, arrays, strings, numbers, booleans, and null. Any of these can be the complete root value, so this parser also accepts documents such as:

"hello"

true

The parser reads the original JSON tokens instead of converting the document with JSON.parse() and JSON.stringify(). This keeps large integer spelling, decimal and exponent notation, property order, array order, and duplicate property tokens visible. Duplicate keys produce compatibility warnings because other software may keep only one value.

Common JSON parsing errors

Strict JSON requires double-quoted property names and strings. Common errors include trailing commas, single quotes, unquoted keys, missing commas, unclosed objects or arrays, invalid escape sequences, comments, malformed numbers, and extra content after the root value.

The parser reports errors instead of guessing how to change the input. Use JSON Repair only when you intentionally want common problems corrected.

JSON parser FAQ

Can the parser read a top-level array or primitive?

Yes. Objects, arrays, strings, numbers, booleans, and null are all valid root values.

What is the JSON Pointer for the root value?

The standard JSON Pointer for the whole document is an empty string. The table displays it as (root) so the row remains easy to identify, while the copy action copies the correct empty Pointer.

Does parsing change large numbers or duplicate keys?

No. The table is built from the original JSON tokens, so number spelling and duplicate property tokens remain visible. Duplicate keys are reported as compatibility warnings.

Can this parser fix invalid JSON?

No. It locates syntax problems but does not modify the source. Use JSON Repair when you want common issues corrected.

JSON Parser

JSON input