YAML and JSON Converter

Convert one YAML document to JSON, or turn JSON into YAML, in your browser.

Inputs stay on your device No sign-up Free to use
How this works

The tool runs in this browser. Your file or text is not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

Privacy details

Convert controls

Showing an example. Edit to see your own.

Paste one document. Custom YAML tags are not accepted.

Processed in your browser. Your inputs stay on this device.

How to use YAML and JSON Converter

  1. Paste one YAML or JSON document.
  2. Choose the conversion direction.
  3. The output or the parsing error updates as you change the input.
  4. Copy the result and check numbers and quoted values before using it.

Example: YAML and JSON Converter

Turn a two-item YAML list into JSON.

You add
name: Ada items: - one - two
You get
A JSON object with name set to Ada and items set to an array containing one and two.

Supported inputs and limits

Converts one document with ordinary JSON values only. Custom YAML tags, dates and binary values are not supported. YAML comments and anchors do not survive conversion; circular aliases are rejected. Numeric spelling and quoting may change, and JavaScript can round long numeric IDs; quote identifiers before converting. Input is capped at 500,000 characters and nesting at 100 levels.

Where your input is processed

This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

Questions about YAML and JSON Converter

Will YAML comments appear in JSON?

No. JSON has no comments, so YAML comments are lost when the document is parsed.

Can I convert several YAML documents at once?

No. Paste one document at a time; document separators for a stream are not supported.

Why did a long numeric ID change?

JavaScript numbers cannot exactly hold every long integer. Quote IDs as strings before conversion.

Can this run a custom YAML tag?

No. The converter uses JSON-compatible YAML values and rejects custom types.

Project manager: Tony Hines · Content updated 29 September 2026 · Report a problem