BRev JSON to YAML
Turn JSON into readable YAML for configs, CI pipelines and Kubernetes manifests — with the output details under your control: 2- or 4-space indentation, automatic or forced string quoting, and a top-level array written either as a sequence or as separate --- documents.
The dangerous direction of this conversion is invisible: a JSON string like "no", "on" or "1.0" written as a bare YAML scalar will be read back as a boolean or number by any YAML 1.1 parser. This converter checks every emitted scalar against both YAML versions and quotes the ambiguous ones, so your strings stay strings.
Nothing is dropped silently in either direction — anything the target cannot represent faithfully is reported. Conversion runs on your device.
The Norway problem: in YAML 1.1 the bare word no is the boolean false — so a list of country codes quietly turns Norway into false. YAML 1.2 reads no, yes, on and off as plain strings, but plenty of parsers still speak 1.1, which is why this tool checks every plain scalar against both readings and shows you the difference before it bites.
Why comments can't survive JSON: converters exchange data, and JSON's data model has no comment syntax at all — a comment in YAML or TOML simply has nowhere to go. Instead of dropping them silently, this tool counts every dropped comment and reports it, along with expanded YAML anchors, TOML dates turned into strings, null values TOML can't hold, and integers too big for JavaScript.
FAQ
Does my data leave the browser?
No — the conversion is fully client-side. Nothing is uploaded.
When should I output --- documents instead of a sequence?
When the consumer expects a stream of documents — kubectl apply and many CI tools read multi-document YAML. For a plain data list, a sequence (the default) is what you want.
Why are some of my strings quoted in the output?
Because unquoted they would change type on the way back: no becomes false, 1.0 becomes a number, 095 can be read as octal by older parsers. Quoting is applied exactly where ambiguity exists.
Which YAML version does the output target?
You can pick 1.2 (modern) or 1.1 (still spoken by many parsers, including several in the Kubernetes ecosystem) — the quoting decisions adapt to the version you choose.