A useful bug report needs the failing shape, not your real customer data. Do not start by pasting a production payload into a public issue and masking a few obvious names afterward. Nested fields, IDs, URLs and free-text values may still identify someone.
Write a fresh, invented example that reproduces the syntax issue. For a trailing-comma case, {"demo":[1,2,]} is enough. It contains a property, an array and the offending comma without exposing the original record. If your real problem is different, keep the smallest relevant nesting or escaping structure and invent every value. This is manual example preparation; neither tool is an automatic anonymizer.
The final report can be short:
- Tool URL and mode.
- Synthetic input that fails.
- Observed error, copied accurately.
- Proposed synthetic output and the small difference.
- Whether the proposed output parses in the formatter.
- What remains untested, such as the consuming application's schema.
If a problem cannot be reproduced without real data, stop before publishing it. Ask for an approved private reporting route rather than assuming local processing makes later screenshots or issue posts private. Clear the sample after the check and review any screenshot for unrelated tabs or account details.
Compare the example at a glance
| Stage | What you enter or see |
|---|---|
| Input that fails | {"demo":[1,2,]}The final comma before ] is invalid. |
| Run result | Choose Mode: Format → Run. The tested version shows “Check the input and selected format.” Output stays empty; Copy result is unavailable. Error wording can vary. |
| Corrected input | {"demo":[1,2]}Run again. Output contains demo with the array [1, 2]; indentation may change, values must not. |
Reproduce the example in the actual formatter
- Open JSON Formatter & Validator. In Input, paste
{"demo":[1,2,]}. Choose Format in Mode, then Run. - Expect an error rather than a successful formatted output. Error wording may differ by browser/version; copy what your session actually reports. The comma immediately before
]is invalid JSON. - Replace Input with
{"demo":[1,2]}and choose Run again. The output should contain the propertydemoand the two numbers1and2in an array. Whitespace and indentation are formatting, not additional data. - Reparse the result or compare the values before reporting success. In Text Compare, compare the two invented strings if you need to show the removed comma. The comparison alone does not validate JSON.
- Include both strings, the selected mode, observed error and corrected result in the bug report. State that schema rules and the consuming application have not been tested. Choose Reset to clear the tool when finished.
If your result differs
- Still invalid: check double quotes, closing brackets and accidental copied text. Fix one synthetic error at a time; do not delete production fields at random.
- Valid JSON but rejected by your app: syntax success does not prove required fields, types or business rules. Use that application's documented schema in an approved private environment.
- Duplicate-key warning: avoid hiding it by reformatting. Different consumers can interpret duplicate properties differently; make the intended structure explicit.
FAQ
Does this anonymize production records?
No. Invent the sample from scratch. Neither formatting nor replacing a visible name guarantees removal of identifiers.
Why does a valid result not fix my application?
The formatter checks and formats supported JSON syntax. It does not run your application's schema or execute the values as code.