Format Atlas

Guides

Choosing a Data Exchange Format

Start with the receiving system's specification. Use JSON for structured API data, XML where an integration requires its schema, and CSV for a single table.

Which format should you choose?

Choose by the role each file plays in your workflow.

  • Web APIs → JSON
  • Schema-based integration → XML
  • Values in one table → CSV

Check the recipient's contract first

JSON is not universally preferable. Existing integrations may require XML namespaces or schemas, while a flat table may only need CSV.

Formats to consider

JSON

Good for: Structured API and configuration data

Less suitable for: Keeping XML attributes and namespaces unchanged

XML

Good for: Existing schemas and integration requirements

Less suitable for: Only simple lightweight settings

CSV

Good for: Exchanging values in one table

Less suitable for: Preserving nested structure or formatting

Before you export

  • JSON–XML conversion may not preserve attributes, order, or namespaces uniquely.
  • For CSV, agree on columns, encoding, and delimiters.

Related comparisons

XML vs JSONXML and JSON are text formats for structured data, but use different structures and conventions.CSV vs XLSXCSV exchanges plain table values. XLSX is a spreadsheet file that can retain formulas, formatting, and multiple sheets.

Guides

Choosing a Spreadsheet Exchange FormatUse CSV to exchange values in a single table. Choose XLSX when the recipient needs formulas, formatting, or multiple worksheets.

File format basics

MIME types

References and specifications