JsonForge · JSON · zero upload
JSON that points at its own error.
Line, column, character.
Parsed in this tab.
Unexpected token tells you nothing at 3 a.m. Paste the document and JsonForge marks the
line, column and the character that broke the parse, then formats it, opens a
tree that copies any node's JSONPath, writes the TypeScript interface or
Zod schema the sample implies, and flattens it to CSV.
Format, minify, validate
the error is the feature—
Walk the document
click any node · copies its pathKeys that are not plain identifiers are copied in bracket form, $["a-b"].items[0], so the path pastes straight into a JSONPath query. Very large arrays are listed 300 at a time instead of all at once.
Types from a sample
inference, not a contract—
—
An object that appears as {...} inside an array is merged across every element: a field missing from some elements becomes ? / .optional(), and a field that is a string in one and a number in another becomes a union. Empty arrays cannot say what they hold, so they come out as unknown — type them by hand.
Flatten to rows
dotted columns · round tripNested objects become dotted columns; an array stays in one cell as compact JSON, because it has no fixed number of columns. Empty cells are null and missing fields. CSV downloads carry a UTF-8 BOM so Excel opens Korean without mojibake.
—
What the parse actually does
three things people conflate01One error at a time
JSON.parse stops at the first token it cannot accept, so fixing the reported character often reveals the next one. That is not the tool being lazy — the grammar has no way to continue past an invalid token, so every parser works this way. Fix, re-paste, repeat.
02Duplicate keys are legal
RFC 8259 says names should be unique but does not forbid repeats, and every engine keeps the last one silently. A config with two "port" keys will parse, and you will spend an hour on a value that was overwritten before you read it.
03Numbers lose precision
JSON numbers become IEEE-754 doubles, so an id like 9007199254740993 comes back changed and a 19-digit bank reference is quietly wrong. Keep long identifiers as strings on both sides of the wire.
Questions
errors · privacy · typesThe JSON is valid but the app still rejects it — why?
null where a string was expected, a date in the wrong format, or a number sent as a string. Run the TypeScript · Zod tab on the response you actually received and compare it with what the code expects — the difference is usually one optional field or one type.