json:yaml

Disclaimer

This disclaimer covers what the site does not guarantee. Conversion between formats is not always lossless, and nothing here is professional advice.

Effective 1 August 2026. Last updated .

General information only

Everything on json-yaml.com — the converters and the written reference material alike — is provided for general information. It is offered in good faith and written carefully, but we make no representation or warranty of any kind, express or implied, about its completeness, accuracy, reliability, or suitability for your purpose.

Any reliance you place on this site is strictly at your own risk.

Conversion accuracy

Format conversion is not always lossless, and this matters more than people expect. Some of what gets lost or changed:

  • YAML to JSON discards comments permanently and expands anchors, so the relationship they expressed is gone.
  • Anything to CSV flattens structure; nested values are serialised into a cell rather than becoming columns.
  • XML to JSON cannot tell a one-element list from a single value, and loses mixed content entirely.
  • TOML has no null, and no agreed convention for representing one.
  • Type inference can change meaning. An unquoted 1.10 becomes 1.1; an unquoted NO can become false.

Each tool page documents the specific limits of that conversion. Please read them, and check the output before you use it for anything that matters. Verifying a converted file against the tool that will consume it — kubectl apply --dry-run, a schema validator, your own test suite — takes moments and is always worth doing.

We are not liable for any loss or damage arising from output that was inaccurate, incomplete, or unsuitable for your purpose.

Documentation accuracy

The reference material describes how parsers generally behave. Behaviour varies between libraries, between versions of the same library, and between YAML 1.1 and 1.2 — which is itself the source of several of the pitfalls we describe. Where correctness matters, verify against the specific parser you will be using rather than against our description of it.

Command-line examples are written for common versions of the tools named. Flags and behaviour change over time. Check the tool's own documentation before running anything against data you care about.

If you find something wrong here, please tell us at contact@json-yaml.com. Corrections are the most useful mail this site gets.

Not professional advice

Nothing on this site is professional advice. In particular, none of it is legal, financial, security, or compliance advice, and none of it is a substitute for the judgement of a qualified professional or for your own testing.

The privacy statements on this site describe how this site behaves. They do not tell you whether your own handling of a particular document meets your obligations under data protection law, your employer's policies, or a contract you are bound by. If you are unsure whether you may process a document, ask someone qualified to answer that.

Your data and your device

Because conversion runs in your browser, your documents stay on your machine — but that also means we cannot recover anything for you. There is no server-side copy, no history, and no undo. Closing or reloading the tab discards your work. Keep your own copy of anything you cannot afford to lose.

Very large documents can exhaust the memory available to a browser tab. If a file is big enough to make the page unresponsive, convert it locally with a command-line tool instead; every tool page shows how.

You are responsible for the security of your own device, browser, and browser extensions. An extension with permission to read page content can read anything you paste into any website, including this one. That is outside our control.

External links

This site links to external documentation, repositories, and reference material. We do not control those sites, do not monitor them, and are not responsible for their content, accuracy, availability, or privacy practices. Following an external link is at your own risk, and a link is not an endorsement of everything on the destination.

Availability

We do not guarantee that the site will be available, uninterrupted, or free of errors, and we accept no liability for it being unavailable when you need it. If your work depends on a conversion happening reliably, put it in your build pipeline rather than depending on a website.

How this fits with our other terms

This disclaimer sits alongside the terms of use, which contains the full limitation of liability, and the privacy policy, which explains what data is and is not collected. Where this page and the terms of use address the same subject, the terms of use govern.