Missing Closing Bracket in JSON – Find and Fix ]

A JSON array opened with [ must close with ]. Missing or mismatched array delimiters often surface as unexpected-end errors or parser failures at a nearby closing brace.

Runs locally
Ready to repair

Paste malformed JSON or AI-generated structured output.

27 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 delimiter repair

How to close an unfinished JSON array

Arrays and objects can be nested together, so the correct closing token depends on the most recently opened structure. The repair workspace above identifies a bounded mismatch and proposes the missing ] as a review-required structural change. 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
  • Mismatched delimiter repair review

Steps

  1. Paste the broken array structure or start with the preloaded example.
  2. Run JSON Repair and review the proposed closing bracket.
  3. Confirm all expected array items are present before accepting the syntactic completion.

Use nesting order to choose ] instead of }

When an array is the most recent open structure, it must close before an outer object can close. A mismatched } at that point usually indicates that ] is missing first.

Check for lost array items in truncated responses

A repair can restore valid syntax but cannot know whether network truncation removed additional array items. Compare the response length or source producer when data completeness matters.

Missing closing bracket example

The roles array is still open when the outer object tries to close.

Invalid JSON

{"roles":["admin","editor"}

Repaired JSON

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

Common questions

Frequently asked questions

How do I find a missing ] in JSON?

Track arrays opened outside quoted strings and confirm each [ closes with ] before any surrounding object closes.

Can a missing bracket cause an end-of-input error?

Yes. If the source ends while an array is open, the parser is still waiting for a closing bracket.

Why can } be reported as unexpected?

If an inner array is still open, a closing object brace arrives too early. The missing ] must close the array before the outer object can end.

Recommended next steps

Unexpected End of JSON InputDiagnose JSON that stops before all strings, arrays, or objects are complete.Missing Closing Brace in JSONRepair an object that ends before its required closing brace.JSON Repair Online – Fix Invalid JSONApply conservative syntax repairs and review every reported change.

Debugging a specific JSON issue? Browse JSON troubleshooting.