03
STRINGS
Multi-line preserved
Block scalars (| literal, > folded) preserved correctly. Newlines kept where YAML kept them.
What it actually does
02
RESOLVE
Anchors and refs
&anchor / *reference patterns inlined into the JSON. Merge keys (<<:) handled correctly.
04
EMIT
Pretty or compact
Indented JSON for readability. Minified for the API call. Both valid.
How it works
- Open morph.cool — browser only.
- Drop the .yaml or .yml file. Or paste the content.
- Pick JSON as the output. The parser runs locally.
- The JSON downloads. Anchors resolved, references inlined.
- The YAML stays untouched.
0Upload
∞Batch limit
1-clickExport
Why people leave the upload-and-queue tools
YAML is what humans write config in. JSON is what machines read it as. Most tools accept both — but most CI pipelines, most APIs, most validation tools want JSON specifically. Morph runs js-yaml in your tab — anchors and references resolved, multi-line block scalars preserved, output spec-compliant.
Frequently asked
How is this different from yq, js-yaml CLI, or online tools?
yq and js-yaml CLI require install and a learning curve. Online tools queue and watermark. Morph runs in your browser — drag, drop, download.
Does it handle anchors and references?
Yes. &anchor / *ref patterns inlined into the JSON. Merge keys (<<:) handled correctly.
Multi-line strings (| and >)?
Both block scalar styles preserved correctly — literal and folded.
YAML 1.1 vs 1.2?
Parser defaults to YAML 1.2 (the modern spec). 1.1 quirks (yes/no as bool, octal numbers) configurable.
Can I batch?
Yes. Drop a folder of YAMLs, get JSONs. Free tier has no batch limit.
Is there a free tier?
Yes. Everything that runs on your device is free with no cap. AI and server work is paid in credits, about a cent each.
Nothing leaves your device · Free for what you make, credits for what we run