Data Format Converters
Move data between formats without losing control of how it maps. Attribute handling, array notation, delimiters and flattening are all options rather than hidden assumptions.
Move data between JSON, XML, YAML, CSV, TSV, HTML tables and query strings with the options each format actually needs.
25 tools
25 tools
- JSON to Base64Encode a JSON document as Base64 for transport in tokens, URLs or headers.JSONBase64
- Base64 to JSONDecode a Base64 string and format the JSON it contains.Base64JSON
- JSON to SQLGenerate INSERT statements from a JSON array of objects.JSONSQL
- SQL to JSONParse INSERT statements into a JSON array of row objects.SQLJSON
- JSON to XMLTurn JSON objects and arrays into well-formed XML with a configurable root element.JSONXML
- XML to JSONParse XML into JSON with configurable attribute, text-node and array handling.XMLJSON
- JSON to YAMLConvert JSON into readable YAML for Kubernetes, CI pipelines and app configuration.JSONYAML
- YAML to JSONParse YAML configuration into JSON, with clear errors for indentation mistakes.YAMLJSON
- JSON to CSVFlatten an array of JSON objects into a spreadsheet-ready CSV file.JSONCSV
- CSV to JSONParse CSV into a JSON array with delimiter detection and optional type inference.CSVJSON
- XML to CSVExtract repeating XML records into flat CSV rows for analysis.XMLCSV
- CSV to XMLTurn CSV rows into XML records with configurable root and row element names.CSVXML
- YAML to XMLConvert YAML configuration directly into well-formed XML.YAMLXML
- XML to YAMLRead XML documents as YAML, with attributes and text nodes mapped explicitly.XMLYAML
- CSV to HTML TableGenerate a clean, accessible HTML table from CSV data.CSVHTML
- JSON to HTML TableRender an array of JSON objects as an HTML table with automatic columns.JSONHTML
- JSON to TSVExport JSON records as tab-separated values for pasting into spreadsheets.JSONTSV
- TSV to JSONParse tab-separated data — including clipboard pastes from spreadsheets — into JSON.TSVJSON
- JSON to Query StringBuild a URL-encoded query string from a JSON object, including nested values.JSONQuery string
- Query String to JSONParse a URL or query string into structured JSON, expanding arrays and nested keys.Query stringJSON
- HTML Table to JSONTurn an HTML table into an array of objects, honouring colspan and rowspan.HTMLJSON
- CSV to YAMLConvert spreadsheet rows into a YAML sequence, with delimiter detection.CSVYAML
- YAML to CSVFlatten a YAML sequence into spreadsheet columns, with nested keys as paths.YAMLCSV
- JSON to NDJSONSplit a JSON array into one record per line for streaming and bulk loads.JSONNDJSON
- NDJSON to JSONCombine newline-delimited records into one JSON array, reporting the bad line.NDJSONJSON
Why format conversion needs options
No two data formats model the world identically, so every conversion involves a decision that a naive tool makes silently. XML has attributes and JSON does not. CSV is flat while JSON nests. YAML reinterprets bare words like yes and no as booleans. SQL has types that JSON cannot express. When a converter hides those decisions, you only discover them later, in production, as a subtly wrong value.
Each converter here surfaces the relevant choice instead. XML to JSON lets you set the attribute prefix and force repeated elements into arrays so a single item and a list share one shape. JSON to CSV asks how to flatten nested objects and what to do with arrays. CSV to JSON lets you pick the delimiter and decide whether numeric-looking strings become numbers.
Round-tripping and what it costs
Converting A to B and back rarely returns exactly what you started with, and it is worth knowing where the losses are. XML attributes do not survive a trip through JSON, because JSON has nowhere to put them. Empty arrays vanish in XML, since there is no element to repeat. CSV has only strings, so type information is reconstructed by inference rather than recovered.
Where a lossless round trip matters, keep the original as the source of truth and treat the converted form as a derived artefact. Where it does not, the options panel lets you choose the mapping that loses the least of what you actually care about.
Nothing is uploaded
Every converter on this page runs as a pure function in your browser. Parsing, mapping and serialising happen locally, and large documents are moved to a Web Worker so the page stays responsive rather than freezing. No request carries your data anywhere.