Format family
Data format family — JSON, CSV, XML & more
Data formats carry tables and objects between apps and APIs. Prefer CSV/TSV for grids, JSON/YAML/TOML for configs and APIs, XML when a schema ecosystem requires it.
Tabular
Rows and columns for spreadsheets and ETL.
CSV is the lingua franca for moving tabular data between spreadsheets, databases, and scripts. It carries values—not formatting or formulas—so pair it with XLSX when people need filters, charts, and styled sheets.
Format hub →
TSV avoids comma collisions inside fields and is common in spreadsheet paste workflows and some bioinformatics/data tools. Convert to CSV when a destination insists on commas.
Format hub →
Structured / config
Nested objects and documents.
JSON is the default payload for web APIs and many app configs. It maps cleanly to programming types. Convert JSON to CSV when analysts need a flat table, or to YAML when humans must edit the same data as config.
Format hub →
XML powers feeds, office document internals, SVG, and enterprise integrations that need namespaces and schemas. Newer public APIs often prefer JSON, but XML remains essential where standards and documents demand it.
Format hub →
YAML makes Kubernetes manifests, CI pipelines, and Compose files readable with indentation instead of braces. Convert to JSON when an API rejects YAML, and quote tricky scalars so booleans and versions do not get mistyped.
Format hub →
TOML aims for obvious semantics: tables, typed values, and fewer surprises than YAML edge cases. Convert to JSON when an API or web tool only accepts JSON.
Format hub →
Best for…
Decision guides for this family — not generic productivity tips.
JSON is the default API payload. XML when standards require it. YAML/TOML for human-edited config — convert to JSON for strict APIs.
CSV for values and pipelines. XLSX when humans need sheets, formulas, and formatting. TSV when commas fight your data.