YAML ↔ JSON ↔ TOML Converter (Mutual Conversion, In-Browser)

Q: "Can YAML anchors and aliases be converted?"

"Yes, but anchors and aliases may be expanded or lost because JSON and TOML do not support an equivalent reference model."

Q: "Can value types (number/string) change during conversion?"

"Yes. YAML implicit typing can reinterpret values like \"01\" or yes/no/on/off. Quote values explicitly when needed."

Q: "Which character encoding is used?"

"UTF-8 is assumed. Japanese and other multibyte text are handled as-is."

Q: "Are comments preserved?"

"No. Comments are not preserved in round-trip conversion, especially because JSON does not support comments."

Q: "Is my input sent to a server?"

"No. Conversion is performed entirely in your browser."

Convert YAML, JSON, and TOML both ways. Paste text and get formatted output instantly.

YAML JSON TOML conversion runs entirely in your browser, and your input is never sent to a server.

No server upload (browser-only processing)

Auto convert (switch to manual mode anytime)

Copy and download ready

How to convert YAML JSON TOML

Paste the text you want to convert.
Choose an input format (or use auto detect) and an output format.
Copy or download the result.

Conversion patterns

yaml to json (YAML -> JSON)

Convert YAML configuration into JSON for APIs and tooling.

json to yaml (JSON -> YAML)

Convert JSON into YAML for easier-to-read config files.

json to toml (JSON -> TOML)

Convert JSON into TOML for application settings.

Sample

YAML -> JSON

Input

app:
  name: demo
  enabled: true
  retries: 3

Output

{
  "app": {
    "name": "demo",
    "enabled": true,
    "retries": 3
  }
}

JSON -> TOML

Input

{"title":"demo","timeout":30}

Output

title = "demo"
timeout = 30

FAQ

Can YAML anchors and aliases be converted?

Yes, but anchors and aliases may be expanded or lost because JSON and TOML do not support an equivalent reference model.

Can value types (number/string) change during conversion?

Yes. YAML implicit typing can reinterpret values like "01" or yes/no/on/off. Quote values explicitly when needed.

Which character encoding is used?

UTF-8 is assumed. Japanese and other multibyte text are handled as-is.

Are comments preserved?

No. Comments are not preserved in round-trip conversion, especially because JSON does not support comments.

Is my input sent to a server?

No. Conversion is performed entirely in your browser.