How to use Jsonwell, and when to ask for help.

No. Everything runs in your browser using the built-in JSON.parse function. Your JSON — partial or complete — is never transmitted, stored, or logged by any server. See the privacy policy for full details.

Some configurations that look like mistakes are technically valid JSON. The most common case is duplicate keys — {"a":1,"a":2} is legal JSON (the parser keeps the last value), and it is almost never what you meant. Jsonwell catches these in the shape report, labelled as duplicates.

Another case: trailing whitespace after the closing brace is valid. Jsonwell reports it, not as an error, but as a structural note.

Currently Jsonwell accepts paste-only input. There is no file-upload button or drag-and-drop zone. If your JSON is in a file, open it in a text editor, select all, copy, and paste into the tool.

The limit is whatever your browser can handle in a <textarea>. In practice this means documents up to a few megabytes are fine. Very large files (hundreds of megabytes) will cause the browser to slow or freeze, because everything is parsed synchronously in the main thread. There is no server-side parser that could handle larger payloads.

No. Jsonwell checks whether your input is valid JSON and reports structural properties of valid documents. It does not check whether the data conforms to a schema or a set of business rules. That is a different tool for a different job.

Not yet. Jsonwell is a browser-based tool only. There is no REST API, no command-line binary, and no editor plugin. If these are important to your workflow, let us know — contact details are below.