Single Quotes in JSON – Convert to Valid JSON

JSON strings and object keys must use double quotes. Single quotes are valid in JavaScript source but not standard JSON, so each conversion should be reviewed for apostrophes and escape behavior.

Runs locally
Ready to repair

Paste malformed JSON or AI-generated structured output.

30 chars

Run the repair to preview the corrected document.

0 chars

Try a focused case

Common invalid JSON examples

Load one broken syntax pattern at a time, run the repair, and compare the declared rule with the resulting repair log.

Trailing commas

Trailing comma

Remove commas that appear immediately before closing object or array delimiters without touching commas stored inside string values.

{"roles":["admin","editor",],"active":true,}

Review: Confirm that each removed comma was only formatting punctuation and did not represent an intentionally missing value.

JavaScript-style object

Trailing comma · Single-quoted string · Unquoted object key

Convert identifier-like keys and single-quoted strings from a JavaScript object literal into standard JSON syntax.

{
  name: 'VetaTool',
  features: ['repair', 'diff',],
}

Review: Review every inferred key and string boundary because apostrophes and JavaScript escaping can make the intended text ambiguous.

JavaScript comments

JavaScript comment

Remove line and block comments that are legal in some configuration formats but are not allowed by the JSON grammar.

{
  // feature flag
  "enabled": true /* temporary rollout */
}

Review: Check whether a removed comment contained operational context that should be preserved outside the repaired JSON document.

Markdown code fence

Markdown code fence

Strip one outer Markdown fence commonly added around JSON returned by chat assistants, documentation, or copied code blocks.

```json
{"name":"Ada","active":true}
```

Review: Verify that the fence wrapped the entire payload and that no explanatory prose outside the code block was discarded.

Unsupported JavaScript literals

Undefined value · Non-finite number

Replace undefined and non-finite numbers that JavaScript accepts but standard JSON cannot represent with reviewable null placeholders.

{"missing":undefined,"score":NaN,"limit":Infinity}

Review: Decide whether null is the correct business value, or whether the property should be removed or represented another way.

Missing and redundant commas

Missing comma · Redundant comma

Insert a separator between adjacent complete values and remove extra separators only where surrounding tokens identify the boundary.

{"first":1 "second":2,,"third":3}

Review: Confirm that inferred separators match the intended property boundaries and that no omitted value was represented by an empty slot.

Mismatched delimiters

Mismatched delimiter

Replace or add a closing brace or bracket when the nested token stack identifies one bounded structural mismatch.

{"items":[1,2,3}

Review: Inspect the surrounding nesting because heavily damaged objects can have more than one plausible brace or bracket completion.

Escaped JSON string

Escaped JSON string

Decode one outer JSON string layer when a field contains an escaped object or array instead of a directly nested JSON value.

{"payload":"{\"name\":\"Ada\",\"active\":true}"}

Review: Confirm that the field is intended to become a nested object rather than remain a string consumed by another downstream system.

Repair log

Run the repair to see each change and why it was made.

No repair run yet.

JSON quoting repair

Why JSON requires double quotes

JSON uses double-quoted strings and double-quoted object member names. The repair workspace above converts common JavaScript-style single-quoted strings while showing the change as review-required because apostrophes and escape sequences can make intent ambiguous. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Browser-local JSON processing
  • Route-specific malformed JSON example
  • Focused parser or repair guidance
  • Broken and corrected JSON example
  • Related JSON problem navigation
  • Single-quote conversion review

Steps

  1. Paste the single-quoted object or use the preloaded example.
  2. Run JSON Repair and inspect each quoting change marked for review.
  3. Verify apostrophes and backslashes in string values before copying the result.

JavaScript object literals are not the same as JSON

JavaScript accepts strings delimited with single or double quotes, while JSON only permits double quotes for strings and object names. Code that looks object-like can therefore still be invalid JSON.

Pay attention to apostrophes inside text

A value such as 'Ada's account' uses JavaScript-style escaping rules. Converting it safely requires preserving the intended text while changing the JSON string delimiter, which is why the repair remains reviewable.

Single-quoted JSON example

Both object keys and string values use JavaScript single quotes.

JavaScript-style input

{'name':'Ada','city':'London'}

Valid JSON

{"name":"Ada","city":"London"}

Common questions

Frequently asked questions

Can JSON use single quotes?

No. Standard JSON requires double quotes around string values and object member names.

Why does a JavaScript object with single quotes still work?

JavaScript object literal syntax is more flexible than JSON. A value can be valid JavaScript source while still being invalid JSON text.

Is converting single quotes always safe?

Not automatically. Apostrophes and escape sequences can change how string boundaries are interpreted, so the repair tool marks these conversions for review.

Debugging a specific JSON issue? Browse JSON troubleshooting.