Open Cron Expression Explainer
Reads the schedule back to you, and when it next fires.
JSON Repair
Paste JSON that will not parse and get valid, formatted JSON back. Mechanical faults are repaired here on the spot; a model is only involved when the damage needs judgement, and whatever it returns is parsed again before you see it.
- Not stored by NexKit
- 20,000 characters
- No sign-up
Broken JSON
or paste your own — anything goes
Settings
Formatting
Applied to the parsed document, not guessed at by a model.
⌘↵ to run
Valid JSON
STANDING BY
This panel has nothing to do yet.
Put some text into 01 and it lands here. The sample works too, if you would rather not think of anything.
How your text is processed. Pressing Repair JSON sends your text to NexKit's servers, which answer it directly where they can. Only when that is not possible is it passed on to a third-party AI provider — the result says which of the two happened. NexKit does not store prompts or output after the request, and never links them to an account, because there are no accounts — that is not a guarantee about what happens on the provider's side, so avoid pasting confidential, sensitive or personal information. AI-generated output can be wrong; check anything that matters before you rely on it.
01Using JSON Repair
- 01
Paste the JSON
Trailing commas, single quotes, comments, unquoted keys, smart quotes, True/False/None — all of it.
- 02
Choose the formatting
Two spaces, four, tabs or minified. Sorting keys is available and off by default, because it changes the document.
- 03
Repair
You get valid JSON and a list of exactly what was changed. Anything fixed mechanically is marked as having needed no model at all.
What people use it for
- Parse the config someone hand-edited at 2am
- Clean up JSON copied out of a log line or a chat message
- Turn a Python dict literal back into JSON
- Find out what is actually wrong with a payload an API rejected
Questions
Does this always call an AI model?
No, and that is deliberate. The input is parsed first; if it is already valid it is only reformatted. Failing that, a deterministic repair pass runs here on the server — quoting, commas, brackets, comments, literals — and most broken JSON is fixed at that step, with no model called and nothing sent to any provider. The model is the fallback for damage that needs judgement, such as a truncated document.
Can it give me back invalid JSON?
It should not. Whatever the model returns is parsed here before it reaches you, and put through the same mechanical repair pass if it does not parse first time. If it still will not parse, you get an error rather than a document that only looks fixed.
Will it change my data?
It is built not to. The repair fixes syntax, never values, and every change is listed. Two things do alter the document and both are reported: sorting keys, if you switch it on, and integers beyond about sixteen digits, which JSON numbers cannot hold exactly — those are flagged with a warning, and the fix is to store them as strings.