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.
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.