Converter tools
Translate between CSV, JSON, Markdown, HTML and Word formats when one system exports what another refuses to read.
11 toolsAll run in your browser
- Image ConverterRe-encode between PNG, JPEG and WebPIn your browser
- CSV to JSONTurn delimited text into structured JSONIn your browser
- JSON to CSVFlatten a JSON array into a tableIn your browser
- JSON Formatter and ValidatorValidate, indent and minify JSONIn your browser
- Excel to JSONRead a workbook into structured JSONIn your browser
- JSON to ExcelWrite a JSON array out as a workbookIn your browser
- Markdown to HTMLRender Markdown into sanitised HTMLIn your browser
- HTML to DOCXConvert HTML into a real Word documentIn your browser
- LaTeX to WordExport equations as DOCX or MathMLIn your browser
- Bank Statement ConverterPDF statements to Excel, CSV, QBO, OFX, QIF or Tally, checked against the balanceIn your browser
- PDF in E-Rechnung umwandelnRechnungs-PDF auslesen, Felder prüfen, XRechnung oder ZUGFeRD erzeugenIn your browser
Move data and documents between the formats systems insist on
Conversion work is rarely interesting and always necessary: one system exports CSV, the next only accepts JSON; a colleague needs a Word file and you have HTML. These tools handle the common crossings between spreadsheet, structured data and document formats.
The data converters run entirely in your browser, so commercial figures and customer records are not transmitted to be reshaped. Real quoting rules are respected, so a value containing a comma or a line break survives the trip.
Which Converter tool do you need?
A spreadsheet export an API will not take
CSV to JSON parses quoted fields correctly and keeps leading zeros intact by default, which matters for IDs and postcodes.
An API response a colleague cannot read
JSON to CSV flattens nested objects into dotted columns and takes the union of every key, so no field is dropped.
A real Excel file, not a CSV
JSON to Excel writes a genuine .xlsx workbook, and Excel to JSON reads .xlsx, .xls, .ods and CSV back out.
JSON that will not parse
JSON Formatter pretty-prints, minifies, sorts keys and reports the structure, so a syntax error is located rather than guessed at.
Markdown or HTML that must become a document
Markdown to HTML renders sanitised GitHub-flavoured Markdown; HTML to DOCX builds a genuine Word document.
A bank statement that only comes as a PDF
The Bank Statement Converter checks each row against the running balance, then writes Excel, CSV, QuickBooks, OFX, QIF or Tally files.
Questions about Converter tools
Is my data uploaded during conversion?
No. The CSV, JSON, spreadsheet, Markdown, HTML and bank statement converters all run in your browser, so commercial data and customer records are never transmitted to be reshaped.
Is the Word file a real .docx?
Yes. HTML to DOCX builds genuine Office Open XML by assembling real Word structures, so the result opens, edits and repaginates like any other Word document rather than being a renamed HTML file.
What happens to nested JSON in a spreadsheet?
Nested objects are flattened into dotted column names such as user.id, and arrays are written as JSON text in the cell. A grid cannot hold a tree, so the structure has to be flattened somewhere.
Are Excel formulas calculated?
No. Excel to JSON reads the value cached when the file was last saved, not the formula behind it. Re-save the workbook in Excel if a cached result looks stale.
Is the output safe to open in a spreadsheet?
Review untrusted data first. The JSON and spreadsheet converters do not escape values beginning with =, + or @, so a spreadsheet may interpret those cells as formulas when it opens the file. The bank statement converter escapes them in its CSV files.