Data Converter

Convert JSON, YAML and CSV locally, preserving numeric tokens and CSV cell text within explicit supported formats.

Conversion format

JSON ↔ YAML 1.2: strings, booleans, null, arrays and unique string-key objects. JSON numeric tokens stay exact, including big integers and decimals. Comments/layout are not retained. Tags, anchors/aliases and non-JSON numeric spellings are rejected.

Input: 1 MiB UTF-8; output: 4 MiB. Up to 100 nesting levels, 100,000 values/cells, 10,000 CSV data rows and 1,000 columns. Conversion has a 2-second time limit. Changing input or direction clears the previous output.

Report a problem

Conversion runs locally in a worker. The source and results are not uploaded or included in automatic reports.

Convert the current input to create an output.

About Data Converter

Convert JSON/YAML data and flat string-valued JSON/CSV records.

Select one of four directions and run conversion. JSON/YAML preserves exact numeric spelling; CSV keeps fields as strings.

Download .json, .yaml or .csv, or copy the current successful result.

The calculation or rendering runs in this browser tab. Copy, download and share actions make the chosen output available outside this tab.

Worked example

Input / settings
[{"id":"00123","name":"Kim"}]
Action
JSON → CSV
Result
id,name 00123,Kim

Scope and limits

  • Input: 1MiB UTF-8; output: 4MiB; depth: 100; CSV: 10,000 data rows and 1,000 columns; worker: 2,000ms. YAML aliases, explicit tags, multiple documents and non-JSON numbers are rejected. CSV requires matching nonblank unique headers and string cells.

Frequently asked questions

Will YAML comments or CSV cell types survive?
Comments and layout are not retained. CSV carries text only; numbers, booleans, null and nested JSON cells are rejected instead of silently losing type or structure.

For account, sync, advertising and analytics data flows, see the Privacy Policy.

Related tools