Config format translation · Real‑time syntax validation · 6 production examples · Supports up to 10MB
All conversions happen in your browser – your config files never leave your device.
YAML, JSON, and TOML are the three most popular configuration formats in modern software development. ng.cc's online converter enables bidirectional conversion, real‑time syntax validation, precise error location, and includes 6 production‑ready examples such as Docker Compose, package.json, Cargo.toml, Kubernetes. All conversions are performed locally in your browser – zero data upload, max privacy.
YAML ↔ JSON ↔ TOML, six conversion directions with one click. Handles arrays, nested objects, booleans, nulls.
Detects errors as you type, with highlighted lines and precise messages. Supports YAML indentation, JSON brackets, TOML table syntax.
Docker Compose, package.json, Cargo.toml, Kubernetes Deployment, app config, complex data structures.
Pure JavaScript implementation – your API keys, database passwords, cloud credentials stay in your browser.
Pros: Most readable, supports comments, ideal for human‑edited configs (Docker, K8s, Ansible).
Cons: Indentation‑sensitive, slower for large files.
Common uses: docker-compose.yml, kubernetes/deployment.yaml, .gitlab-ci.yml
Pros: Universal, supported by every language, fast parsing.
Cons: No comments, strict syntax (no trailing commas).
Common uses: package.json, manifest.json, API responses
Pros: Unambiguous, supports multi‑level tables, no indentation tricks.
Cons: Smaller ecosystem, less widespread than YAML/JSON.
Common uses: Cargo.toml (Rust), pyproject.toml (Python), Wren.toml
#) are discarded during conversion. TOML supports comments, but they are also lost when converting to JSON. To keep comments, stick with YAML or TOML.
2026-02-12 become JSON strings; TOML dates like 1979-05-27 also become strings. None of these formats have a native date type, so all dates are handled as strings.
yq or jq.
This converter is part of the ng.cc config‑tool collection. You might also like:
⚡ All conversions happen locally – your config files never leave your browser.