CSV to JSON Converter
CSV rows become a JSON array, keyed by the header row.
Convert JSON into clean, indented YAML in your browser. YAML 1.2 is a superset of JSON, so the result is valid. Watch for unquoted values.
Your browser is preparing the tool. It runs 100% locally.
Paste JSON and get YAML. The tool reformats your data into YAML's indented style: objects become key: value lines, arrays become dash-prefixed items, two spaces per level. Since YAML 1.2 is a superset of JSON the output is valid YAML. One caution: values are written unquoted, so a string like no or 1.0 can be read back as a boolean or number. All of it happens in your browser.
This rewrites JSON as YAML. Each object key becomes a key: value line, each array item becomes a line starting with a dash, and nesting is shown with two-space indentation. The data is unchanged; only the notation differs.
Because YAML 1.2 is a superset of JSON, valid JSON always converts to valid YAML. The catch is type safety: values come out without quotes, so anything that looks like a boolean, number or null can be re-interpreted by a YAML reader.
Paste or type JSON. It is parsed first, so invalid JSON is reported rather than mis-converted.
The tool walks the structure: objects become key-value lines, arrays become dash items, and each level of nesting adds two spaces.
Values are written as-is, without quotes. Copy the YAML or download it as a .yaml file. All of this happens in your browser.
Object key = key: value (one line per key)
Array item = a line starting with a dash and a space
Nesting = two spaces deeper per level
Values = written unquotedThe JSON {"name": "Smart Free Tools", "tools": ["pdf", "image"], "meta": {"free": true}} becomes (line by line): name: Smart Free Tools / tools: / then two dash items, pdf and image / meta: / then free: true.YAML 1.2 is a superset of JSON, so the result is valid YAML. Because values are unquoted, though, a string like no, yes or 1.0 can be read back as a boolean or number.
Your browser parses and converts the JSON without a server, and the tool uploads nothing.
The data never leaves your device, so even sensitive records stay private.
You don't need an account and the site keeps no copy, so the conversion is gone once you close the tab.
| Input | JSON |
|---|---|
| Output | YAML (.yaml) |
| Indent | Two spaces per level |
| Arrays | Dash-prefixed items |
| Quoting | Values unquoted |
| Validity | Valid YAML 1.2 |
| Processing | 100% in-browser |
Values are written unquoted. A JSON string such as no, yes, on, off, null or 1.0 comes out bare, and a YAML reader may interpret it as a boolean, null or number. This is the well-known Norway problem. Quote such values yourself if a clean round-trip matters.
YAML 1.2 is a superset of JSON, so the output is valid YAML. Most JSON converts predictably; the risk is about how a value is later read, not whether the YAML parses.
This is a basic serializer. It does not add quotes, fold long strings into literal blocks, or specially handle a value that contains a colon-and-space or starts with a dash or a brace. Any of these could confuse a YAML reader.
Indentation is two spaces per level. Numbers and booleans are emitted as-is, matching their JSON form.
Invalid JSON is reported as an error, so you will not get half-formed YAML from a typo.
Turn a JSON config into the YAML that many tools, such as CI systems, Kubernetes and Docker Compose, prefer.
Convert dense JSON into YAML that is easier to scan and edit by hand.
Show the same data in YAML for documentation or a tutorial.
Generate a starter YAML file from a JSON source.
If exact type round-trips matter, quote ambiguous values or use a full YAML library. To convert YAML back, use the YAML to JSON converter.
Reformats your parsed JSON into YAML's indented style: objects become key-value lines, arrays become dash-prefixed items, two spaces per level. Because YAML 1.2 is a superset of JSON the result is valid YAML, but values are written unquoted, so a string that looks like a boolean or number can change type when re-read. All of it happens in your browser.
CSV rows become a JSON array, keyed by the header row.
Flatten a JSON array of objects into CSV columns.
Turn everyday Markdown into clean HTML in your browser.
Pasted CSV becomes a real .xlsx, with leading zeros kept.
Pull the first sheet of a workbook out as plain CSV.
Each spreadsheet row becomes a JSON object keyed by the header.
The file never leaves your computer, and you don't need an account.