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.