Convert data between JSON, XML, YAML, TOML, CSV, TSV and INI in one place. Pick the source and target formats, paste your data, and get a clean conversion instantly — in your browser, no uploads.
YAML conversion needs the js-yaml library from CDN (network required). JSON, XML, CSV, TSV, INI and TOML work fully offline.
Related tools
This page replaces the individual converters below, which remain available as standalone pages.
Your input is parsed into a neutral in-memory structure, then serialized to the target format. JSON, XML, CSV, TSV, INI and TOML are handled by built-in parsers that work fully offline; YAML uses the js-yaml library loaded from a CDN. XML attributes map to @-prefixed keys, CSV and TSV become arrays of row objects, and INI sections become nested objects.
Limits to know
Conversions are structural, not magic: deeply nested data flattens awkwardly into CSV rows, and INI only supports one level of sections. TOML support covers the common subset (key/value pairs, sections, arrays, basic types). For YAML you need a network connection the first time the library loads.
No. Parsing and serialization run entirely in your browser. Only the optional YAML library is fetched from a CDN; your data never leaves the page.
Why does my CSV conversion look flat?
CSV is a tabular format, so nested objects are represented as row objects with one column per key. Deeply nested structures convert best to JSON, XML, YAML or TOML instead.
How are XML attributes handled?
Attributes become keys prefixed with @ (for example @id), and mixed text content lands in a #text key, so a round-trip back to XML preserves them.
Does it validate my input?
Yes. Malformed JSON or XML produces a clear error message instead of a partial result, so you know exactly what to fix.
Can I convert without a network connection?
For JSON, XML, CSV, TSV, INI and TOML, yes — everything is built in. YAML is the only format that needs the CDN library.