CSV To JSON Converter, And Back Again

Most CSV to JSON converters split each line on a comma. That works until a customer is called “Alvarez, Maria”, an address contains a line break, or Excel writes semicolons because the machine is set to a European locale. This one uses a proper parser: a quoted field may hold the delimiter, a newline and doubled quotes, records may end with Windows, Unix or classic Mac line endings, and the invisible byte order mark Excel puts at the start of a UTF-8 export is stripped before it can turn id into a column name nothing matches.

Who It Is For

Anyone holding an export they did not create. A shop owner with an orders CSV who needs JSON for a form or an app. Someone whose spreadsheet came out of a course, a scanner or a chat with an assistant and now has to go into a website. A developer who wants to eyeball a file before writing an import script. You do not need to know what RFC 4180 is; you need to know that row 47 came through intact, which is what the table preview is for.

How It Works

Everything runs in your browser. The file is never uploaded, and nothing is sent anywhere unless you press Publish. The tool reads your data into a table, then writes it out as JSON — an array of objects keyed by the header row, or an array of arrays if you prefer positions to names. The delimiter menu covers comma, semicolon, tab and pipe, and Auto tries all four and keeps whichever reads as a consistent table, so a semicolon-separated file from Excel and a TSV to JSON conversion both work with no settings at all.

Ragged rows are reported, never silently fixed. If a row has fewer cells than the header the missing fields come through empty; if it has more, the extra values get their own column. Either way the line number is listed underneath the panel so you can find it in the original file. Convert numbers and booleans is deliberately off by default, because turning 0042 into 42 or a phone number into a float is how a converter quietly ruins a file. Even with it on, values with a leading zero, a leading plus or more than fifteen digits stay as text.

Going Back: JSON To CSV

The other tab converts JSON to CSV. Keys are unioned across every record, so a field that appears on only one object still gets a column instead of vanishing. Objects nested one level deep are flattened into dotted columns, so customer.name and customer.city become two ordinary columns. Anything deeper than that, and any array, is written into the cell as compact JSON text: it stays in the file, and it does not explode into hundreds of columns. If you want that data as markup instead, the HTML Table Generator takes the same CSV and gives you a<table>, and the JSON Formatter will indent and validate the JSON before you convert it.

Limits

A dropped file is capped at 5 MB, since the whole conversion happens in one browser tab. The table preview shows the first 200 rows; the output and the download always hold every row. There is no schema inference, no nested output structure built from dotted headers, and no date parsing — dates stay exactly as they were written, which is almost always what you want.

Then Put It Online

Data is usually going somewhere: a price list, a fixture list, a stock count someone needs to see today. Publish A Share Page wraps your table in a small complete page and puts it on a free OxyPages link with HTTPS in seconds, with no account. The link lasts 30 minutes unless you claim it, claiming is free, and from there you can choose your own address and connect a custom domain on a paid plan. See how it works for the whole picture.