Rebuild a tagged JSON Pointer document
Paste a version 1 tagged document produced by JSON Flattener, then choose Rebuild document. This page does not accept arbitrary dotted-key maps. Explicit object and array tags tell the tool how to reconstruct empty containers and numeric-looking property names.
Example: restore the nested structure
The example contains five nodes. The root is an object; /items is an array; /items/0 holds number 1; /items/1 is an empty object; and /a~1b holds null. Reconstruction returns {"items":[1,{}],"a/b":null} with readable indentation. Loading the example replaces the current input and old output.
Required node ordering and validation
The first node must have an empty pointer and define the root. Every parent container must precede its children. Array children must appear in consecutive index order from zero; sparse arrays and indices with leading zeros are rejected. Duplicate paths, missing parents, a child under a scalar, unknown fields and mismatched type/value fields produce errors.
Only scalar nodes contain a value field. Empty objects and arrays need their own nodes. Pointers use ~1 for slash and ~0 for tilde. Names such as __proto__ are ordinary own properties in a null-prototype object rather than prototype mutations. The result is JSON text, not executable code.
Format and reconstruction bounds
At most 2,500 tagged nodes and 64 reconstructed nesting levels are supported. The input envelope also follows the JSON reader's total input/value limits. This restores parsed value structure, not original whitespace or numeric spelling. Preserve original files if byte identity or signatures matter. Use JSON Pointer Resolver to inspect a rebuilt branch.
Reader limits and output
Input supports 200,000 characters, 20,000 values and 64 nesting levels. Duplicate keys, unsafe integers, nonfinite numbers and nonzero values that underflow to zero are rejected. Other decimals use JavaScript floating-point precision. Formatting, escape spelling and negative zero may normalize; quote precision-sensitive data as strings. General output is capped at two million characters, with tighter tagged-format limits described above where applicable. Processing stays in the browser, and editing inputs or options clears stale results.





