Useful formats
Convert between common table and structured-text formats without separate pages.
Input0 B
Output0 B
Add data or load the sample to begin.
0rows0columns0issues
Basics
Understanding the format
Structured-data conversion maps records and fields from one representation to another. CSV and TSV are flat tables; JSON, XML, and YAML can also contain nested structures.
When nested values are converted to a table, this tool flattens them into path-based column names so the mapping stays visible.
What it does
What this tool does
Choose source and target formats, paste or open data, inspect conversion diagnostics, and reuse the result for a round-trip check.
Preview first
Inspect the output and table dimensions before copying or downloading.
Visible flattening
Nested objects become path columns instead of silently disappearing.
Local processing
Conversion runs in this browser tab.
How to use
How to use it
Choose formats
Set the real source format and the target you need.
Add data
Paste content, open a local file, or load the sample.
Convert and inspect
Review diagnostics, row counts, escaping, and the generated output.
Reuse or export
Copy, download, or feed the result back into the input for a round-trip check.
Errors & limits
Common errors and limits
Nested source data
Nested JSON, XML, or YAML is flattened; inspect path-based headers before export.
Type loss
CSV and TSV store text and cannot reliably retain every number, date, boolean, or null distinction.
Encoding wrappers
Base64 and URL encoding operate on UTF-8 text; decode before selecting a structured source format.
Review
Not every format can round-trip perfectly. Comments, XML attributes, YAML anchors, types, field order, and nested structures may change when represented as a flat table.
FAQ
Frequently asked questions
Can I convert CSV to JSON?
Yes. The header row becomes object keys and each following row becomes an object.
Can I convert JSON back to CSV?
Yes. Arrays of objects are flattened into a union of path-based columns.
Does XML conversion preserve attributes?
Attributes are represented with @-prefixed path fields where practical, but complex mixed-content XML is not lossless.
Is there a file-size limit?
There is no server limit, but browser memory and rendering set practical limits.