Input
Waiting for input.
Output
YAML parsing uses js-yaml's safe schema — no arbitrary tag execution.
YAML parsing uses js-yaml's safe schema — no arbitrary tag execution.
Kubernetes manifests, CI pipelines, OpenAPI specs and application configs are YAML; APIs and tooling speak JSON. This converts either way as you type, detecting the direction from what you paste — JSON is valid YAML, so it tries JSON first. Multi-document YAML separated by --- round-trips to a JSON array.
Converts as you type, detecting which way round you pasted.
Kubernetes manifests separated by --- become a JSON array, and back again.
YAML parse failures point at the exact spot rather than failing silently.
js-yaml's safe schema only — no tag can construct arbitrary types or run code.
Yes, including multi-document files: each document separated by --- becomes an element of the resulting JSON array.
It uses js-yaml's safe schema, which does not construct arbitrary types from tags. Nothing in your document can execute code.
YAML forbids tab characters for indentation. The tab option applies to JSON output only; YAML output falls back to two spaces.