Delimiter.live
Data Conversion Tools Runs in your browser Free · no account

YAML to JSON Converter

The YAML to JSON converter parses common YAML — nested mappings, sequences, quoted and plain scalars, block scalars, comments and multiple documents — and emits the equivalent JSON. It covers the subset that configuration files actually use.

Options
YAML 0 characters
JSON to YAML
JSON

Your result will appear here.

Not sure where to start? Use Load example.

Results update automatically and are calculated on your device. Nothing you type is sent to a server.

Runs in your browser. Processing happens entirely in your browser. Nothing you enter is sent to Delimiter.live.

How to use the YAML to JSON Converter

  1. Paste your YAML file, or load a .yml file from your device.
  2. Read the JSON result; any parse error names the line that caused it.
  3. Copy or download the JSON.

Example

Input
name: Ada
tags:
  - a
  - b
Output
{
  "name": "Ada",
  "tags": ["a", "b"]
}

Common use cases

  • Inspecting a CI, Kubernetes or Docker Compose file as JSON.
  • Feeding a YAML configuration into a tool that only reads JSON.
  • Checking that hand-edited YAML actually parses to the structure you intended.

Limitations and things to watch for

  • The parser covers the YAML subset used by real configuration files: nested mappings and sequences, inline flow collections, single- and double-quoted scalars, literal and folded block scalars, comments, document separators and the usual scalar types. It deliberately does not implement anchors and aliases, custom tags, complex keys or merge keys — if your file uses those, the parser reports an error rather than guessing.
  • Duplicate keys in the same mapping keep the last value, matching how most YAML loaders behave.
  • Tabs are not valid for indentation in YAML and are reported as an error, which is usually the real bug in a file that will not parse.

Frequently asked questions

Which YAML features are supported?
Nested mappings and sequences, flow style ({} and []), quoted and plain scalars, literal (|) and folded (>) block scalars, comments, multiple documents and the standard scalar types. Anchors, aliases, custom tags and merge keys are not supported and produce a clear error.
Why does my file fail with an indentation error?
YAML forbids tab characters for indentation. Replace tabs with spaces — the whitespace remover can do it in one pass — and the file will parse.
Is my configuration file uploaded?
No. Parsing runs entirely in your browser, which matters because configuration files often contain internal hostnames and settings.

Share this tool