How to use the Data Converter
- 1
Select the input format (JSON, YAML, XML, CSV or TOML) and the output format you need.
- 2
Paste your data into the input panel. The conversion runs as you type, so syntax errors show up immediately.
- 3
Check the output. Nested objects are kept when converting between JSON, YAML, TOML and XML; for CSV the data should be an array of flat objects, one per row.
- 4
Copy the result, or use Swap Formats to convert it back and confirm nothing was lost.
Practical examples
Kubernetes and Docker Compose
Convert a JSON object from an API or a script into YAML to paste into a deployment manifest or docker-compose.yml, without fighting indentation by hand.
Spreadsheet data to JSON
Export a sheet as CSV, paste it here and get an array of JSON objects ready for a seed script, a mock API or a front-end prototype.
Legacy XML APIs
SOAP services and older feeds return XML. Converting it to JSON makes the structure easier to read and to map to TypeScript types.
Config file migration
Moving a project from config.json to pyproject.toml, Cargo.toml or a YAML file? Convert the existing settings instead of retyping them.
Frequently asked questions
Which conversions lose information?+
JSON, YAML and TOML map almost one to one. XML attributes and repeated elements need a convention to become JSON, and CSV can only hold flat rows, so deeply nested data is flattened or rejected.
Why does CSV conversion fail?+
CSV needs a consistent table: the same columns in every row and quotes around values that contain commas or line breaks. For JSON to CSV, the input must be an array of objects.
Is YAML just JSON without brackets?+
YAML is a superset of JSON with indentation-based structure, comments and extra types. Watch out for values like no, yes or 0123, which some YAML parsers interpret as booleans or numbers.
Is my data uploaded?+
No. Parsing and conversion run in your browser, so configuration files with credentials or customer exports stay on your device.