toolready. JSON ↔ YAML ↔ TOML

JSON ↔ YAML ↔ TOML

Trilingual config converter: JSON, YAML, and TOML.

→

What's the point of having three config formats?

Each format trades off readability for different things. JSON is the lingua franca of APIs but is awkward to write by hand (quoting every key, trailing commas illegal). YAML is friendlier for humans (indentation, comments) but has surprising edge cases (the famous "Norway problem"). TOML splits the difference for config files — explicit, simple, and unambiguous. Tools like GitHub Actions, Kubernetes, Cargo, and pyproject use different ones; this converter is for when you need to cross between them.

How do I use it?

  1. Pick the source format (left) and target format (right).
  2. Paste the source. The output updates instantly.
  3. Click Copy to grab the result.

What about TOML's "must be an object" restriction?

TOML requires a top-level table — bare arrays or primitives aren't valid TOML documents. If you try to convert a JSON array [1, 2, 3] to TOML, you'll get an error. Wrap it: { items: [1, 2, 3] }.

Is anything uploaded?

No. Parsing and serialization happen entirely in your browser using js-yaml and @iarna/toml. Verify in DevTools.