Import CSV text
Read CSV from spreadsheets, databases, or text exports; choose the separator and encoding; rename or exclude columns; and create JSON, XML, or HTML.
Convert JSON, CSV, and XML
Convert JSON to CSV, XML or HTML, import CSV as structured JSON or XML, and verify mapping and output choices before using the result.
Core conversion workflows
JSONBuddy keeps the source, mapping choices, preview, and generated result close enough to inspect before the transformed data enters another application or automated process.
Read CSV from spreadsheets, databases, or text exports; choose the separator and encoding; rename or exclude columns; and create JSON, XML, or HTML.
Transform documents in either direction, configure the conversion in a dedicated dialog, and preserve XML attribute or namespace information when the target needs it.
Select child objects and values with JSON Pointer paths, preview the tabular rows, and generate CSV for Excel or another CSV-aware application.
A concrete JSON-to-CSV workflow
Check the mapping before export
Keep the unchanged source available until the converted output has passed its downstream checks. A successful conversion is only the first check. JSON objects and arrays, XML elements and attributes, and CSV rows and columns do not express every structure in the same way. Review a representative result before converting the complete data set.
Confirm that the selected array represents the intended rows, nested values map to useful columns, headers are stable, and separators or encodings open correctly in the target spreadsheet or database tool.
Check column names, excluded fields, empty cells, numeric-looking identifiers, dates, delimiters, quoted text, and character encoding. Keep identifiers as strings when leading zeroes or exact text must survive.
Inspect attributes, namespaces, repeated elements, mixed content, arrays, and scalar types. Use a small round-trip sample when downstream software depends on a particular mapping, then validate the converted result against its intended contract.
Beyond one interactive conversion
Conversion can remain an editor task, move to a command-line workflow for repeatable processing, or feed an HTML result through an XSLT stylesheet when the output needs a human-readable presentation.