Work through the task
Translate the supported YAML subset into JSON values.
- Enter one supported YAML document and convert it.
- Review the decoded types; aliases and custom tags are rejected rather than resolved.
- Review the result before copying or downloading. Editing an input invalidates the previous result; keep an original if the transformation matters.
Example to check
v: "007" becomes {"v":"007"}; a quoted text value stays text.Limits and output behavior
Source is limited to 100,000 characters. JSON/YAML/TOML have 10,000 values and 40 data levels; XML has separate node/attribute and element-depth guards. Comments, numeric spelling and other lexical formatting may normalize. YAML aliases/custom tags and TOML null values are unsupported.
Troubleshooting
Remove unsupported aliases/custom tags and fix duplicate keys or unsupported values. The converter does not fetch or resolve external definitions.
Questions
Are YAML comments retained in JSON?
No. Conversion writes the supported decoded data values. Comments and original source layout are not JSON values.
Input and privacy
Processing runs in this browser. Inputs are not saved automatically. An explicitly chosen local draft, where offered, is plaintext storage on this device. Downloaded files, clipboard contents and browser extensions have separate retention behavior.