Converters
23 free tools · 100% client-side
Convert between JSON, XML, YAML, CSV, TSV, and other data formats instantly. Free, accurate converters with a premium editor experience.
Start here
Most-used Converters
CSV to JSON
Header-aware CSV parsing into clean JSON — pick the delimiter, keep IDs as strings or type them, and choose objects, arrays or JSON Lines.
JSON to CSV
Flatten JSON arrays into spreadsheet-ready CSV — nested keys become dot-path columns, quoting handled for you.
XML to JSON
Parse any XML document into clean JSON — repeated elements become arrays, attributes preserved, text nodes kept.
All 23 Converters
JSON to XML
Turn any JSON document into well-formed XML — element per key, repeated tags for arrays, declaration included.
JSON to CSV
Flatten JSON arrays into spreadsheet-ready CSV — nested keys become dot-path columns, quoting handled for you.
JSON to YAML
Re-express JSON as clean, human-friendly YAML — smart quoting, two-space indentation, list dashes done right.
JSON to TSV
Tab-separated output that pastes perfectly into Excel and survives data full of commas.
JSON to String
Turn a JSON document into a complete, ready-to-paste string literal for the language you're actually writing — quotes and delimiters included, not just an escaped body.
XML to JSON
Parse any XML document into clean JSON — repeated elements become arrays, attributes preserved, text nodes kept.
XML to CSV
Turn record-style XML into spreadsheet-ready rows — wrapper elements unwrapped, nested fields flattened to columns.
XML to String
Validate your XML, then escape it into a single string literal — ready to embed in JSON fields or source code.
XML to YAML
From angle brackets to clean indentation — XML parsed and re-expressed as readable YAML.
RSS to JSON
Turn any RSS feed into clean JSON — channel metadata and an items array, ready for your app or script.
YAML to JSON
Full YAML 1.2 parsing — anchors resolved, types preserved, errors pinpointed — straight into clean JSON.
YAML to XML
From indentation to angle brackets — YAML parsed with full 1.2 semantics and rendered as well-formed XML.
YAML to CSV
YAML record lists in, spreadsheet-ready CSV out — flattened columns, RFC 4180 quoting, no manual reshaping.
CSV to JSON
Header-aware CSV parsing into clean JSON — pick the delimiter, keep IDs as strings or type them, and choose objects, arrays or JSON Lines.
CSV to XML
Rows to records: every CSV line becomes a <row> element with header-named children, in one well-formed document.
CSV to YAML
Spreadsheet rows re-expressed as a clean YAML list — typed values, dash items, human-readable in any editor.
CSV to HTML
A semantic, fully-escaped HTML table from any CSV — thead, tbody, and a styling hook, ready to paste.
String to JSON
Paste an escaped JSON string — with all its backslashes — and get the real, formatted JSON back.
YAML to Properties
Flatten application.yml into application.properties — dotted paths, Spring's key[0] list convention, and the ISO-8859-1 \uXXXX escaping Java's Properties loader expects.
Properties to YAML
Rebuild application.properties into application.yml — dotted keys unflattened into real nesting, key[0] lists reassembled, and your # comments kept.
vCard to JSON Converter
Turn a .vcf export into a predictable JSON array — structured names and addresses, typed phones and emails, every card in the file.
TOML to JSON
Parse any TOML document — pyproject.toml, Cargo.toml, wrangler.toml — into clean JSON, with dates kept as ISO strings and 64-bit integers kept exact.
JSON to TOML
Turn a JSON object into well-formed TOML — tables from nested objects, [[tables]] from arrays of objects, and an honest report of what a null cost you.
Learn more
Move data between formats without losing structure
Every integration eventually hits a format mismatch: the API speaks JSON, the legacy system exports XML, the spreadsheet wants CSV, and the deployment pipeline reads YAML. These converters translate between all of them with structure preserved — XML attributes become @-prefixed keys, YAML anchors are resolved, CSV headers become object fields with types inferred — so what comes out is usable data, not a lossy approximation.
Each direction is a dedicated page with its own sample, options, and documentation, which keeps conversions one-click simple: JSON to XML, XML to JSON, YAML to JSON, CSV to JSON, JSON to CSV, TOML to JSON, JSON to TOML, YAML to Properties, Properties to YAML, and a dozen more, including RSS feeds to JSON and Excel-pasted tables to HTML. Not sure which of TOML, YAML or JSON actually fits a new config file? The TOML vs YAML vs JSON guide walks through the trade-offs. Like everything on NV Toolkit, the parsing happens in your browser — converting a confidential export never sends it anywhere.
Conversion gotchas these tools handle for you
Format conversions have sharp edges: JSON arrays have no natural XML representation (the converters use repeated elements), CSV has no nesting (single-key wrappers are unwrapped to reach the tabular rows), YAML's anchors and merge keys need resolving before JSON can represent them, and type inference — is "007" a string or a number? — changes meaning. TOML has no null at all (a null object value is omitted, with a count, rather than silently vanishing), and Java's flat .properties format has no real nesting either — just a dotted-key convention the YAML to Properties / Properties to YAML pair unflattens and reflattens on purpose. The converters apply sensible, documented defaults for each edge, and the per-tool FAQ explains the exact mapping so you can verify the behavior matches your schema before relying on it.
Help
Frequently asked questions
Everything you need to know about the Converters.
01Do these converters preserve all my data?
Structure-preserving mappings are used wherever the target format can express the source: keys, nesting, arrays, and values all survive JSON ⇄ YAML and JSON ⇄ XML round-trips. Where a target genuinely can't represent something (CSV has no nesting; XML attributes have no JSON equivalent), the documented convention on each tool page explains exactly what happens.
02Which converter do I use for spreadsheet data?
CSV to JSON turns exported spreadsheets into objects keyed by the header row, with numbers and booleans typed automatically. Going the other way, JSON to CSV flattens an array of objects into rows. For data pasted straight from Excel (tab-separated), Excel to HTML produces a clean table you can embed.
03Can I convert files, or only pasted text?
Both — every converter accepts pasted text, a loaded file, drag-and-drop, or a fetched URL, and the result can be copied or downloaded with the right extension. Processing is local either way; the file never uploads.
Learn the format
Guides for converters
TOML vs YAML vs JSON: Choosing a Configuration Format
TOML, YAML and JSON compared for configuration files: comments, types, nesting, dates, tooling and the ecosystems that chose each — with a decision guide and conversions.
6 min readGuide · Data FormatsYAML Multi-line Strings: | vs > vs Quoted (Indentation Rules)
How YAML literal | and folded > block scalars differ, what -, + and a digit change, when to quote instead, and why a run: block loses its line breaks.
9 min readTutorial · Data FormatsHow to Convert CSV to JSON in JavaScript, Python and the Browser
Tested CSV to JSON code for Node (papaparse) and Python (csv.DictReader), plus type inference, nested output, streaming, and the trip back to CSV.
7 min readGuide · Data FormatsXML Namespaces Explained: Prefixes, Default Namespaces and Common Errors
What xmlns and xmlns:prefix do, how default namespaces scope and inherit, why attributes are excluded, and why XPath returns nothing on namespaced XML.
7 min readGuide · Data FormatsYAML Anchors, Aliases and Merge Keys Explained (With Real Config Examples)
How &anchor, *alias and the <<: merge key work in YAML, where docker-compose, GitLab CI and Helm use them, the override order, and the errors they cause.
7 min readGuide · Data FormatsJSON vs XML: An Honest Comparison
JSON vs XML compared without tribalism: syntax, size, attributes, namespaces, schemas, tooling — and the cases where each format genuinely wins.
2 min read