ToolSphere

CSV to JSON Converter

More tools

Convert CSV to JSON and JSON to CSV in your browser with comma, tab, or pipe delimiters. Toggle numeric type conversion and export files securely.

CSV input
JSON output · 2 rows

Parsing runs in your browser, so spreadsheets of customer or payroll data never leave the device. Nested JSON objects are flattened into their string form when converting to CSV — CSV has no way to express nesting, so reshape the data first if the nested fields matter.

On this browser only

Give feedback

Did this tool help?

Tell us what worked, what didn’t, or what you’d like next.

Opens Google Forms in a new tab with this tool’s name filled in. No sign-in or email required. Feedback is optional.

How to use CSV to JSON Converter

  1. 1Paste CSV (or JSON) into the left pane, or start from the sample.
  2. 2Choose the delimiter that matches your file — comma, semicolon, tab or pipe.
  3. 3Turn off type conversion if your data has identifiers with leading zeros.
  4. 4Copy or download the converted output, or press the direction button to reverse.

About CSV to JSON Converter

Converting between the two formats people actually exchange data in

CSV is what spreadsheets export and what finance teams send. JSON is what APIs speak. Moving between them is one of the most common small tasks in a developer's week, and it is routinely done by pasting a spreadsheet of customer names, salaries or order histories into someone else's server. This converter runs the parse in your browser, so the data never leaves your machine.

Getting the delimiter right

Comma-separated values are only comma-separated in some parts of the world. In locales where the comma is the decimal separator, Excel exports semicolons instead — which is why a European CSV opened with a comma parser collapses into one column. Tab-separated files come out of databases and analytics exports, and pipe-separated files out of older enterprise systems. Pick the delimiter that matches your file, and the preview tells you immediately whether you chose right.

Type conversion is a choice, not a default

With type conversion on, 42 becomes the number 42 and true becomes a boolean, which is usually what you want for an API payload. Turn it off when your identifiers are numeric strings: an order reference like 0012345 becomes 12345 under type conversion, and a leading zero lost in a customer ID is a bug that surfaces much later. Phone numbers, postal codes and account numbers all belong in this category.

The limits of CSV as a target

CSV is a flat grid. It has no way to express a nested object or an array inside a field, so converting nested JSON flattens those values into their string form. If the nested fields carry meaning, reshape the JSON into flat rows before converting rather than accepting a column full of stringified objects.

Row-by-row error reporting tells you which line failed rather than just refusing the file, which matters when the problem is a single unescaped quote three thousand rows in.

Frequently asked questions

Is my spreadsheet uploaded?

No. Parsing runs in your browser, so payroll, customer and order data never leaves your device.

Why did my CSV parse into a single column?

Almost always the delimiter. Excel in comma-decimal locales exports semicolons, and database dumps often use tabs. Switch the delimiter and the preview corrects immediately.

Why did my IDs lose their leading zeros?

Type conversion turned the text 0012345 into the number 12345. Turn it off for identifiers, phone numbers, postal codes and account numbers.

How is nested JSON handled when converting to CSV?

CSV is a flat grid with no way to express nesting, so nested values are flattened to their string form. Reshape the JSON into flat rows first if those fields matter.

What happens if one row is malformed?

The error names the row number and the problem rather than rejecting the whole file, which matters when a single unescaped quote sits thousands of rows in.

Have a suggestion for CSV to JSON Converter?Share your feedback ↗