Convert JSON into readable YAML

For making configuration easier to review, share or version, JSON to YAML produces a clear and readable result.

Produce readable YAML from JSON data so configuration files are easier to scan and maintain. You get the result directly in your browser.

How to use

  1. Drop a JSON object into the input area or import a .xml, .json, .yaml, .yml, .md, .markdown, .html, .htm or .txt file.
  2. Click Convert to turn the data into readable YAML.
  3. The result shows clear indentation and key: value pairs.
  4. Review the output to check that lists and nested objects are correct.
  5. Copy the generated YAML or clear everything with Erase.

Example

You want to make a JSON configuration more pleasant to read in a Git repository. The conversion to YAML produces a file with natural indentation. Your colleagues can browse and edit it more easily.

Limits and formats

Where processing happens

Processing happens in your browser: the JSON is converted locally without being sent out. Your configuration data therefore stays private during the operation.

Frequently asked questions

Is the generated YAML compatible with all parsers?

The YAML produced follows common syntax, but some parsers have preferences for quotes or indentation. It is wise to test the file with the tool that will consume it.

How are lists represented in YAML?

JSON arrays become YAML lists with dashes. Nested objects are indented. Check that the structure matches what you expect, especially for lists of objects.

Can I add comments to the generated YAML?

The tool does not generate comments. You can add them manually to the YAML file after conversion. Check that your parser accepts them.

Which file types can I import before converting to YAML?

The import area accepts .xml, .json, .yaml, .yml, .md, .markdown, .html, .htm or .txt files. You can also drop a JSON object into the input area. Click Convert to turn the data into readable YAML. The result shows clear indentation and key: value pairs. Processing happens in your browser and your configuration data stays private.

Will dates and large numbers stay exactly the same?

Not necessarily. Very large numbers or dates may be reinterpreted during conversion. Strings containing special characters may be quoted differently in YAML. Review the output and test the file with your usual YAML parser before using it in a critical system. Processing happens in your browser and your configuration data stays private.

Tools in the same category