Kim Yihyung
← All tools

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.

0 bytes uploaded 0 external requests native JSON.parse works offline

Format, minify, validate

the error is the feature
Indent
JSON input Waiting for JSON
Result —
—

What the parse actually does

three things people conflate

01One 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 · types
The JSON is valid but the app still rejects it — why?
Syntax is the cheapest check. The next failures are all semantic: a field the schema requires is missing, 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.
Can I keep working on a huge file?
Paste up to a few megabytes comfortably; formatting and statistics are linear and happen once per edit. The tree renders lazily, 300 children at a time, so a 20,000-row array does not lock the tab. Above roughly 10 MB the textarea itself becomes the slow part, which is a browser limit rather than a page limit.
Does sorting keys change the meaning?
No, and that is a property of JSON worth knowing: an object is an unordered set of name/value pairs, so a consumer that depends on key order is depending on something the spec never promised. Two arrays, on the other hand, are ordered, and this page never reorders them.
Is any of this sent anywhere?
No. The page loads no font, no script and no stylesheet from another host, and makes no request after the first paint. The footer counts cross-origin requests with a PerformanceObserver and it stays at 0 — the honest version of the claim, rather than a promise in a marketing line.