A practical starting point

Make JSON readable and find syntax errors

Format a JSON sample, inspect parse errors, and preserve the values you started with before using the result in a configuration or API request.

3 steps to get startedSources reviewed
Use the JSON formatter to make valid JSON easier to inspect and surface syntax problems. This route helps with a pasted sample; it does not automatically infer the intended missing values.

Useful starting points

Tools and resources you can explore today. External services have their own terms and availability.

JSON formatterOn this site · Tool JSON formatting guideOn this site · Guide

A practical way forward

  1. Use a small representative sample

    Remove access tokens and personal records, then paste enough data to reproduce the error. Keep an untouched copy of the original.

  2. Fix syntax deliberately

    Inspect quotes, commas and matching brackets. JSON requires double-quoted strings and excludes trailing commas; change one issue at a time.

  3. Check the data after formatting

    Compare keys, array lengths and value types. Formatting success verifies syntax, not whether the data matches your application’s expected schema.

Worked examples & reusable files

Fix syntax without inventing data

This synthetic object has two independent syntax problems: single quotes and a trailing comma. Repair only those; preserve the identifier string.

Input or setup

{'id':'0012','active':true,}

Result or expected output

{
  "id": "0012",
  "active": true
}
  • A parser accepting this output confirms JSON syntax, not whether active should be true.
  • Do not change a quoted long identifier into a browser number just to make the file look cleaner.

Keep in mind

  • Large integer identifiers may lose precision if handled as ordinary browser numbers; preserve identifiers as strings.
  • A successful parse does not validate business rules or a schema.

Sources, not guesswork

Background for this guide. Discussion and documentation are useful signals, not proof of demand or an endorsement of every service.

Planned · Research

Explain and review JSON repairs

Research only — not available yet. Would suggested fixes with a visible before-and-after diff help you repair malformed JSON?

This feature is not available yet. We’re exploring whether it would be useful. Tell us about your task; leaving an email for follow-up is optional.

All solutions

Convert CSV to JSON without losing identifiers

Convert quoted CSV fields to JSON, preserve leading zeros and long identifiers as strings, and check multiline records with a downloadable example.

Read the guide

Turn flat JSON records into a spreadsheet table

Convert a flat JSON array into CSV, check the exported columns, and verify how your spreadsheet interprets identifiers and formula-like text.

Read the guide

Test a pattern against real examples

Check a regular expression against matching and non-matching examples, choose the right flags, and verify the pattern in its destination engine.

Read the guide
AN IDEA IN RESEARCH

What would make this useful?

This feature is not available yet. We’re exploring whether it would help. Sharing feedback is free and does not reserve a place or promise a launch date.

Please leave out passwords, private files, and other people’s personal information.

Feedback is kept privately for up to 90 days. Privacy & deletion