BRev YAML to JSON
Paste YAML, get JSON — with a difference: JSON has no comment syntax, so every # comment in your file is about to disappear. Most converters drop them silently; this one counts them and tells you, along with every anchor and alias it had to expand into duplicated data.
It also checks your file for the Norway problem: under YAML 1.1 the bare scalars no, yes, on and off are booleans, so a country list quietly turns Norway into false. Every ambiguous scalar is shown with both its 1.1 and 1.2 readings so you can pick the version your consumers actually parse.
Multi-document files (--- separators) are handled explicitly rather than truncated to the first document, and conversion runs entirely 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 file leave the browser?
No — parsing and conversion are client-side. Config files with embedded secrets never leave the page.
What happens to my comments?
They cannot survive: JSON’s data model has no comments at all. Instead of losing them silently, the loss report counts every dropped comment so you know what to carry over by hand.
Why did "no" become false?
YAML 1.1 defines no/yes/on/off as booleans; YAML 1.2 reads them as strings. This tool flags every scalar that reads differently between the two versions and lets you switch the reading.
What about multiple documents in one file?
A file with --- separators contains several documents. The converter reports this and represents them explicitly instead of silently keeping only the first.