CSV to JSON Converter

CSV (Comma-Separated Values) is a plain-text table. Each line is a row, values inside a row are separated by commas, and the first line usually holds the column headers. Because it is just text, nearly every spreadsheet, database and analytics tool can read and write it.

Yes. Drag a .csv, .tsv, .txt or .json file anywhere onto the input box, or click Browse to pick one. The converter reads it with the browser's own file reader, works out whether it is CSV or JSON, and converts it immediately. The file is never sent anywhere.

Yes. The Download button saves the output as a .json or .csv file, named after the file you dropped in. There is also a Copy button if you would rather paste the result straight into your editor.

Yes. Delimiter detection is automatic — the tool inspects the first row and picks whichever of comma, semicolon, tab or pipe is being used, which covers European exports and TSV files. You can also override it manually if the guess is wrong.

Because converting 03001234567 to a number would silently drop the leading zero and corrupt the data. Values with a leading zero, and numbers too long to represent exactly, are deliberately kept as strings. Everything else converts normally, and you can switch number conversion off entirely if you want every value as text.

Nested objects are flattened into dot-notation columns, so { "address": { "city": "Karachi" } } becomes a column called address.city. Arrays are flattened by index. If you would rather keep the raw structure, turn flattening off and nested values are written as JSON inside a single cell.

Every key found anywhere in the data becomes a column, in the order it first appears, and rows that do not have that field get an empty cell. Going the other way, short CSV rows are padded so each record has the full set of keys.

It comfortably handles files with thousands of rows, since the conversion is native JavaScript running on your own machine with no network round trip. Files up to 15 MB can be dropped in; beyond that a streaming or command-line tool is a better fit.

Yes. All parsing and conversion happens locally in your browser. Nothing is uploaded, logged or stored, so it is safe to use with customer exports and internal reports.