Original text

0 characters (UTF-16)Line 1, column 1Red row: error; darker highlight: locationCtrl + Enter

Repair preview

Awaiting diagnosisGreen row: repaired; darker highlight: change
ReadyPaste YAML, then click Diagnose & repair
Click “Diagnose & repair” to see error locations, explanations and a repair preview.
Model capabilities and limitations

YAML formatting and minifying: Format for readability or minify optional layout whitespace. Choose one mode at a time. Strings, numeric spelling and comments are retained. XML/HTML mixed text and preformatted content, and YAML/TOML required line breaks and indentation, stay intact. Review the preview before applying it.

How to use: Paste your text and choose Diagnose & repair. Auto preview is off by default; enable it to update after editing. Choose formatting or minifying, review the changes, then copy the result or apply it to the original. Diagnosis runs in your browser; the site uses Google Analytics for traffic statistics.

How diagnosis works: This format uses a local, deterministic syntax checker and conservative repair rules. The trained 6,753-parameter model is used only for JSON. Diagnosis runs locally without third-party processing libraries or a model service. Google Analytics is used for site traffic statistics. A recovery scanner also continues after unresolved fields. It makes conservative local repairs and leaves unknown values visible for manual review.

Supported cases: Common YAML 1.2 block/flow mappings and sequences, quoted and plain scalars, block scalars and comments. Repairs include indentation tabs and certain missing brackets or invalid string escapes. Anchors, aliases, tags, directives and complex keys are outside scope. YAML 1.1-specific typing and full schema resolution are not provided.

What you should review: Review every change before applying it. A syntactically acceptable result may differ from the intended data. Closing tags, brackets and indentation repairs may be ambiguous. Missing values and duplicate fields require manual review. Formatting is optional and enabled by default. XML/HTML indent explicit element structure while preserving mixed text and raw-text blocks. YAML/TOML normalize separators while preserving indentation, comments and string contents. Unsupported layout structures stay unchanged.

Tests and limitations: This is a bounded basic checker, not a full specification validator. Passing these checks does not guarantee standards compliance or business correctness. Unsupported structures are reported for manual review. JavaScript, CSS, schemas and application rules are not validated.

Processing limits: Up to 131,072 UTF-16 code units and 128 nesting levels. Model search uses up to 24 steps; recovery allows up to 256 edits and 512 diagnostic items. If a limit is reached, the incomplete check is reported for manual review.