The error message that tells you nothing
An "unexpected token" complaint with no location is one of the least helpful sentences in debugging. When a config file refuses to load or an API rejects your request body, the actual mistake is usually a single character — but finding it by eye in a wall of brackets is slow and demoralizing. A validator that reports exactly where the parser stopped changes the job from proofreading a document to jumping to a position. SafeFileConvert’s JSON formatter does precisely that, and works the same whether the JSON came from a colleague, a webhook, or a production log.
Step by step
- Open the JSON formatter at safefileconvert.com/data/json-formatter/. You can paste JSON directly into the page or open a .json file from disk.
- Read the error, if there is one. Malformed input produces a message that names the problem and points at the position where parsing failed, so you can go straight to the offending character instead of scanning the whole document.
- Fix the input at that spot and run it through again, repeating until it parses. The tool deliberately does not auto-repair: automatic fixes can silently change meaning, so it shows you the problem and leaves the decision to you.
- Choose your output. Pretty-print with two spaces, four spaces, or tabs for reading and code review, or minify to a single line for embedding in configs and shrinking payloads.
- Copy the result to your clipboard or download it as a file.
The usual suspects
Most invalid JSON fails for one of a handful of reasons: a trailing comma after the last item in an array or object, single quotes where the format requires double quotes, an unquoted key, or a stray character dragged in from a log line. When the validator points at a position, check for those four first — the odds are good the fix is deleting or requoting a single token.
Safe for payloads with secrets in them
The JSON people paste into formatters is rarely dummy data. It is API responses carrying bearer tokens and session IDs, webhook payloads with customer emails, database exports. A formatter that posts input to a backend quietly hands all of that to a third party. Here, parsing happens with JavaScript in your own tab — no request carrying your JSON is ever made, nothing is logged, and there is no account, usage cap, or paywall around any option. You can validate the most sensitive payload of your week with the same confidence as a hello-world sample.