YAML·JSON conversion
Convert YAML to JSON bidirectionally. Preserve large numbers and check types, aliases, and annotations that cannot be converted to JSON.
Input is processed in this tab and is not saved or sent. Sharing includes only a summary.
Result
Execute after input.
Conversion result · Direct copy
Processing criteria and changes during conversion
Share result
Share the tool link and result text together. No URL is included in the result. Check the below content and then share it.
How to use and processing criteria
A tool that checks document types and converts YAML 1.2 settings and JSON documents in both directions.
Actual example
YAML name: When converted to tool, active: true, id: 9007199254740993, name becomes a string, active becomes a boolean, and id becomes a non-rounded number in JSON. yes becomes a string in YAML 1.2. When converting from JSON to YAML, double quotes are added to keys and strings to prevent type changes for characters like yes and null.
Frequently Asked Questions
Which YAML types are supported?
YAML 1.2 core supports string, numbers, booleans, null, arrays, and string key objects. It supports numeric and complex object keys, .inf, .nan, custom tags, object creation tags, and merge keys <<. YAML 1.1 and multiple document streams are reported as errors. Duplicate keys are silently overwritten.
Are notes and anchors retained?
JSON is non-significant; remove or expand as a standalone value with processing instructions. Cyclic aliases are rejected; expansion is limited to 50 items or 10,000 values. Large integers and decimals maintain original precision but may change formatting such as indentation, quotes, or hex notation.
What are the document size limits and storage methods?
The input is 100,000 characters or less, the conversion depth is 80 or less, and the output is 1,000,000 characters or less. The execution of a separate Worker takes up to 3 seconds, and the module preparation takes up to 10 seconds. If there is an error or cancellation, the previous normal result is retained. After reviewing the result, save it to a JSON or YAML file, but do not store the input in a browser storage.
Calculation criteria and reference materials
- yaml — YAML 1.2 parsing and document type
YAML core schema, aliases, and source node processing
- RFC 8259 — JSON
JSON syntax and interoperability considerations for number precision
Verification of calculation criteria: · Calculation·verification principles · Report errors