Developer Tools

CSV to JSON & JSON to CSV.

Convert CSV to JSON or JSON to CSV in one box: pick the direction and the delimiter, or upload a .csv or .json file. Nested objects flatten to dot-notation columns and unflatten back on the way in. Everything runs in your browser — nothing is uploaded.

How to convert between JSON and CSV

  1. Pick the direction: JSON to CSV, or CSV to JSON. Swap direction flips it.
  2. Choose the CSV delimiter: comma, semicolon or tab.
  3. Paste your data into the box, or upload a .json or .csv file to load it.
  4. Press Convert, then copy or download the result.

How the conversion treats your data

Going from JSON to CSV, an array of objects becomes rows. Nested objects are flattened into columns named with dots, such as address.city. Nested arrays are kept as JSON text inside a single cell so no information is dropped. Going the other way, the first row is read as headers, dot-notation headers are rebuilt into nested objects, and numbers and booleans are detected automatically.

Spreadsheets in some regions expect a semicolon between values because the comma is the decimal mark, which is why the delimiter is selectable. Tab-separated output pastes cleanly into spreadsheet cells. If your JSON is not an array of objects, wrap the items in an array first.

Your data stays on your device

The converter runs in your browser, inside an isolated frame on this page that has no network access. Your file is read and written back by your own device, so it is not uploaded to TNAADO or anyone else, and nothing is stored. The advertising on this page sits outside the frame and cannot see what you choose. JSON and CSV files often hold customer records or exports, which is why nothing is parsed on a server.

How it works

Sources

RFC 4180, Common Format and MIME Type for CSV Files (October 2005), for quoting fields that contain delimiters, quotes or line breaks; RFC 8259, The JSON Data Interchange Format (December 2017), for the JSON side. Both retrieved 2026-10. CSV has no single binding standard, so files from some tools may differ from RFC 4180. To check or tidy the JSON you produce, use the JSON formatter or the JSON validator.

Worked example

Computed on 2026-10-26 with the same flatten, unflatten and Papa Parse 5.4.1 calls this page makes. JSON in:

[{"id":1,"name":"Ana","address":{"city":"Toronto","postal":"M5V 2T6"},"tags":["a","b"]},{"id":2,"name":"Lee, Jo","address":{"city":"Ottawa","postal":"K1A 0B1"},"tags":[]}]

CSV out. The nested address object became dot columns, the array stayed as JSON text in one quoted cell, and the name containing a comma was quoted:

id,name,address.city,address.postal,tags
1,Ana,Toronto,M5V 2T6,"[""a"",""b""]"
2,"Lee, Jo",Ottawa,K1A 0B1,[]

Converting that CSV back to JSON restores the nesting and turns id back into a number:

[
  {
    "id": 1,
    "name": "Ana",
    "address": {
      "city": "Toronto",
      "postal": "M5V 2T6"
    },
    "tags": "[\"a\",\"b\"]"
  },
  {
    "id": 2,
    "name": "Lee, Jo",
    "address": {
      "city": "Ottawa",
      "postal": "K1A 0B1"
    },
    "tags": "[]"
  }
]

Frequently asked questions

How do I convert CSV to JSON?

Set Direction to CSV to JSON, paste the CSV or choose a .csv file, pick the delimiter and press Convert. The first row is read as the column names and every later row becomes one JSON object in an array.

How are nested objects handled?

Going to CSV, a nested object becomes dot-notation columns such as address.city, and a nested array is stored as JSON text in one cell. Going to JSON, a header like address.city is turned back into a nested object.

Are numbers and true/false kept as numbers in the JSON?

Yes, CSV values that look like numbers or true and false are converted to JSON numbers and booleans. If a column holds IDs or codes that must stay text, check those values in the output.

Is my file uploaded to a server?

No. The conversion runs in your browser, and the file you choose is read locally and never sent anywhere.

Advertisement
Advertisement