What can be lost when YAML becomes JSON?
Comments, anchors, tags, and scalar styles have no direct JSON equivalent.
Different expressive models
YAML supports comments, anchors, aliases, and several scalar styles. JSON is stricter and is commonly used for machine exchange, so YAML to JSON is usually normalization rather than a lossless copy.
Record the loss
Comments, layout, anchors, custom tags, and some date or number semantics do not survive. Snapshot important fields and run the target application's configuration tests after migration.
Safe parsing
Untrusted YAML should not be loaded with arbitrary constructors. JSONLane follows a constrained YAML 1.2 core model and rejects custom tags, duplicate keys, unsafe integers, and excessive alias expansion.
Related tools
Sources
Last updated: 2026-08-23