esc
21 free tools

JSON, CSV, XML & Excel converters
and YAML, Markdown, subtitles

Convert between JSON, CSV, XML, YAML, Markdown, HTML and Excel, plus subtitles (SRT, VTT), vCard contacts and GPX or KML map files. Your data never leaves your browser.

Violet file character juggling brackets
JSON JSON to CSVJSON → CSV CSV CSV to JSONCSV → JSON XML XML to JSONXML → JSON JSON JSON to XMLJSON → XML YAML YAML to JSONYAML → JSON JSON JSON to YAMLJSON → YAML HTML HTML to MarkdownHTML → Markdown MD Markdown to HTMLMarkdown → HTML JSON JSON to TOONJSON → TOON TOON TOON to JSONTOON → JSON MMD Mermaid to SVGMermaid → SVG MMD Mermaid to PNGMermaid → PNG CSV CSV to ExcelCSV → Excel XLSX Excel to CSVExcel → CSV SRT SRT to VTTSRT → VTT VTT VTT to SRTVTT → SRT VCF VCF (vCard) to CSVVCF → CSV CSV CSV to VCF (vCard)CSV → VCF GPX GPX to KMLGPX → KML KML KML to GPXKML → GPX OpenAI token counterPaste a prompt and see how many tokens it uses, as you type.

This JSON, CSV, XML and Excel converter moves data between the formats apps, spreadsheets and config files use, including YAML, plus Markdown and HTML for text and SRT and VTT for subtitles. Choose the format the receiving program expects; the notes below cover what changes on the way.

Which data format fits

  • CSV: flat rows and columns for spreadsheets, databases and bulk imports. Every value is plain text, with no nesting.
  • Excel (.xlsx): rows with real number cells and several sheets, for people who will sort, total or chart the data.
  • JSON: nested objects and lists, the format of web APIs and most apps.
  • XML: tagged data with attributes, still common in feeds, older APIs and exports.
  • YAML: the same kind of data as JSON written to be read by people, used in Docker, Kubernetes and CI config files.

What each conversion does

  • JSON to CSV: when the records sit inside an object, for example under a results key, that list becomes the rows.
  • CSV to JSON: the first row becomes the keys. Detect numbers & booleans turns 42 and true into real values instead of strings, while codes like 007 stay text.
  • XML to JSON: attributes become keys starting with @_, and the text of an element that also has attributes goes under #text.
  • Excel to CSV: each sheet that has data becomes its own CSV file.
  • CSV to Excel: numbers become numeric cells, and codes with leading zeros stay as text so the zeros survive.

No direct route? Chain two tools

There’s no single JSON to Excel or XML to CSV tool, but two steps get you there: JSON to CSV, then CSV to Excel; or XML to JSON, then JSON to CSV. YAML takes the same path through YAML to JSON.

Common problems

  • An error with a line and column number. The JSON, XML or YAML isn’t valid at that point, often because of a missing comma, quote or closing tag.
  • Excel puts everything in one column. In regions that write decimals with a comma, Excel often expects semicolons. Choose Semicolon under Separator in JSON to CSV or Excel to CSV.
  • Subtitles won’t load. Use SRT to VTT for HTML5 video on websites, and VTT to SRT for desktop players.

Questions

What happens to nested JSON in CSV?

Nested fields become dotted columns like address.city; arrays stay as JSON text in one cell.

How big a file can I convert?

Files of tens of megabytes work on most computers.

How do I convert JSON to Excel?

Run JSON to CSV, then put the CSV through CSV to Excel. Numbers become real numeric cells in the workbook.

Why do accented characters look wrong in my CSV?

CSV files made here are saved as UTF-8 with a marker that tells Excel the encoding, so they open correctly. If a UTF-8 CSV from elsewhere looks garbled in Excel, CSV to Excel builds a workbook that shows the characters properly.