data
JSON to YAML and CSV
Turn JSON into YAML or CSV without a backend.
Runs 100% in your browser. Nothing you paste is uploaded, stored, or sent to a server.
How to use
- Paste valid JSON. Objects, arrays, and primitives are all accepted.
- Open the YAML tab for a readable mapping, or the CSV tab for a spreadsheet-shaped export.
- CSV works best with an array of objects. Nested values are stringified. Keys become the header row.
- Copy the result into a runbook, a GitHub issue, or a spreadsheet.
JSON is easy for programs and noisy for humans. YAML is the format most Kubernetes manifests and Ansible inventories already speak. CSV is what spreadsheets and data teams ask for. This converter does both transformations on the device so you can reshape a payload you would rather not park in a third-party “JSON to CSV” form.
The YAML emitter is intentionally small: mappings, lists, scalars, and literal block strings. It is not a YAML 1.1 compatibility suite. The CSV path is similarly pragmatic — a table from homogeneous objects, or a key/value dump from a single object.
Examples
Object to YAML
{"name":"DeskKit","ok":true} becomes a two-line mapping. Booleans and nulls stay unquoted; strings that look like numbers or booleans are quoted.
Array to CSV
[{"id":1,"name":"Ada"},{"id":2,"name":"Grace"}] becomes a header row plus two data rows. A comma inside a field is quoted.
Single object to CSV
A lone object exports as key,value rows so you can still open it in a spreadsheet.
Limits on purpose
This is a one-way converter for the cases developers hit daily: tidy a JSON fixture, drop it into a YAML doc, or hand a PM a CSV. It will not emit YAML anchors, merge keys, or custom tags. It will not invent columns from deeply nested trees — those cells become JSON strings so nothing is silently dropped.
If the input is not JSON, you get the parser error and no output. That is nicer than producing half a CSV from a truncated paste.
For pretty-printing JSON itself, use the JSON formatter. For encoding the result into a URL or Base64, chain the other tools on this site.
FAQ
Can I convert YAML back to JSON?
Not on this page. YAML-in is a larger parse problem (tags, duplicate keys, Norway problem). The MVP ships JSON as the source of truth.
How are nested objects represented in CSV?
They are JSON-stringified into a single cell. Flattening arbitrary trees without a schema invents column names you would not want.
Does YAML output round-trip?
Simple documents should. The emitter quotes strings that would otherwise be parsed as booleans or numbers, which avoids the classic “yes/no/on/off” trap.
Is the JSON uploaded?
No. Conversion is local.