How do I convert JSON to YAML?
Paste the JSON into the input with JSON selected above it and YAML selected above the output; the YAML appears as you type. Objects become indented key: value blocks, arrays become lists of "- " items, and every key keeps the order it had in the JSON. Strings are left unquoted wherever YAML would read them back as the same text, and quoted wherever it would not — "yes", "1.0", "2026-10-17" and "null" all stay strings rather than turning into a boolean, a float, a date and nothing. Text with line breaks is written as a | block, the way a person would write it by hand.
How do I convert YAML to JSON?
Select YAML for the input and JSON for the output, or simply paste: a pasted document is recognised and the input format switches to match. Comments are dropped, since JSON has none; anchors and aliases (&name and *name) are expanded into copies, and << merge keys are applied. A file holding several documents separated by --- becomes one JSON array with a document per item. The output can be indented by two or four spaces, or minified onto a single line for a request body.
Can it convert JSON or YAML to TOML?
Yes, with three rules that come from TOML itself. The document has to be a table at the top level, so a bare array must be put under a key first. TOML has no null, so a null value stops the conversion and names where it is, unless you tick "Leave out null values". And a table lists its plain keys before its sub-tables, because a key written after a [header] belongs to that header — so some keys can move up, which the tool tells you about. Nested objects become [table] sections, and arrays of objects become [[array of tables]] sections, as Cargo.toml and pyproject.toml are written.
Are data types preserved between JSON, YAML and TOML?
Yes, as far as the target format can hold them. Integers and floats are kept apart, so a version: 2.0 stays 2.0 rather than becoming the integer 2, and integers are carried exactly, including 64-bit IDs above 2^53 that most JavaScript tools round. TOML dates and times arrive in YAML as unquoted timestamps and come back as dates, while JSON, which has no date type, gets them as strings. Booleans stay booleans, and a quoted "02134" stays a string with its leading zero. The one loss is NaN and infinity, which JSON cannot express, so the tool says which value is the problem instead of writing something else.
Why does my YAML or TOML fail to parse?
The error names the line and column where the parser stopped and shows that line with a marker under it; "Show line" selects it in the input. In YAML the usual causes are a tab used for indentation, a child indented by a different amount than its siblings, a value containing ": " that needs quotes, or the same key twice in one mapping. In TOML they are a string without quotes, a table defined twice, or a key set again after its table was closed. In JSON they are a trailing comma, single quotes, a comment or a missing comma between two lines — each of which the message names.
Which YAML and TOML versions does it support?
YAML 1.2 with the core schema, which is what modern parsers and the YAML specification use, and TOML 1.0. When writing YAML the output also stays safe for older YAML 1.1 readers such as PyYAML and go-yaml v2: words like yes, no, on, off, y and n are quoted, so they are not read as booleans, and a time like 07:32:00 is quoted so it is not read as a base-60 number. That keeps Kubernetes manifests, Docker Compose files and GitHub Actions workflows meaning what you wrote.
Is my configuration uploaded anywhere?
No. The whole conversion is JavaScript running in your own browser, so the configuration files you paste or open — with whatever hostnames, keys and passwords are in them — are never sent over the network, written to a log or attached to an analytics event. You can confirm it by opening the network tab and watching it stay empty while you work.