Decide whether a value is text
Quote values such as "001", "true" and long account IDs if they are text. An unquoted YAML number becomes a JSON number; a quoted one stays a string. YAML 1.2 core rules apply, not YAML 1.1 guessing. Unquoted dates remain strings under this schema. YAML output deliberately quotes strings and keys.
Use one JSON-compatible document
Supply string-keyed objects, arrays, finite numbers, booleans, strings and null. Multiple documents, duplicate keys, explicit tags, anchors, aliases and complex keys stop conversion. The converter never fetches a referenced URL or applies a configuration to a service. Resolve application-specific syntax separately.
Handle exact values deliberately
Unsafe integers, negative zero, non-finite numbers and numeric tokens that would round are rejected. Quote high-precision amounts and large identifiers before converting. If all you need is readable JSON indentation, use the JSON formatter to keep number tokens exactly as supplied.
Keep the original commented file
JSON has no comments. YAML comments, source quoting and layout disappear during data conversion. Download the generated file under a new name and compare representative values before replacing anything in your own project. Use at most 400 KB / 100,000 characters; the tool also bounds nesting and output.