Find and fix invalid JSON.

In the browser editor, open a .jsonc file or paste JSONC source, then choose Repair and JSONC to strict JSON. Safe JSON repairs remains the default task. Review the complete original and converted result before downloading a separate .json copy or explicitly applying one undoable edit. Only comments and trailing commas are removed; numeric and string tokens remain unchanged. Ordinary formatting still requires strict JSON. Duplicate keys and JSON5 syntax are refused. Conversion supports up to 2 Mi characters, 128 container levels and 100,000 tokens/values, with local cancellation and a five-second limit. Native file associations, installed versions and integration support can differ.

Choose Repair and JSON5 to strict JSON in the browser editor. Review the complete original and proposal, then download a separate .json copy or explicitly Apply; Undo restores the original. Supported JSON5 data includes comments, trailing commas, unquoted keys, single-quoted strings, signed decimals and hexadecimal integers. Strict decimal number spellings are retained, including values beyond JavaScript number range; hexadecimal integers convert exactly. Strings and keys are quoted or escaped when required. NaN, Infinity, decoded duplicate keys, JavaScript expressions and unsupported syntax are refused. Limits are 2 Mi source/output characters, 10,000 characters per numeric token, 100,000 tokens/values and 128 container levels, with local cancellation and a five-second deadline. Ordinary formatting and the separate JSONC task retain their strict policies. This does not provide comment-preserving JSON5 structured editing or certify installed/integration versions.

In the web editor or a desktop build that includes this feature, open Schema and use Exact schema validation. Import or paste raw schema text, explicitly load local references and choose Draft 2020-12 and a format policy. This separate whole-document check supports up to 1 MiB UTF8 per source and eight reference files. Unsupported inputs report unavailable. It does not change your document, existing continuous validation or precision guards for hints. Raw imports stay in this tool for the current page session. To validate AI proposals with them, explicitly enable Use these exact settings for JSON assistance. The whole proposed document is checked locally before review and again on Apply; invalid or unavailable checks cannot apply. This choice is off by default and schema or file changes turn it off.

Yes. In the editor, open Schema and load your schema and its local references explicitly. Syntax validity and schema validity are separate. Referenced schemas are not fetched automatically; schema completion and hover are withheld for precision-sensitive instance numbers. For precision-sensitive numbers, continuous diagnostics omit conditional, reference and numeric checks rather than showing errors from a rounded branch. Independent unconditional checks and proven exact enum/const checks remain available. Full validation stays unavailable in that continuous path, and schema-reviewed assistance cannot apply on an incomplete result. The web editor and desktop builds that include this feature separately offer an explicit exact raw-schema review policy for bounded AI proposals. Installed versions and platforms can differ. The separate bounded Exact schema validation action has its own explicit policies.

It checks whether the source parses as a complete JSON value. Review syntax feedback for malformed quotes, commas, brackets or trailing content, then edit and validate again.

No. Valid syntax does not establish that values are complete, accurate or suitable for your application. Review the parsed data before relying on it.

Local editing processes selected and pasted contents in your browser. Optional Assistance sends your goal and only the context you explicitly prepare and include, such as a selected subtree or observed query field metadata, to OpenRouter and the configured model provider. Its preview shows exactly what is included. Ordinary page and asset requests also reach the hosting provider.