Why are all my numbers quoted as strings?

That is the default on purpose. '007' as a number becomes 7 and a 13-digit id loses exactness, so values stay strings until you turn on type inference deliberately.

Can it handle commas inside a field?

Yes — quoted fields are parsed as one value, including embedded commas and newlines, which is what RFC 4180 CSV requires and what spreadsheet exports produce.

My file is semicolon-separated. Will it work?

Set the delimiter to ';' and it converts unchanged. The same field accepts a tab for TSV.

Is it safe to paste sensitive rows here?

For anything you would not email, yes: the conversion runs in your browser and the data is never sent to a server.

Text & Data Ready to use

CSV to JSON Converter

Paste CSV and get JSON objects, with header detection, custom delimiters, quoted fields, whitespace trimming and optional number and boolean inference.

CSV input

Output

First row is header

Delimiter

Trim whitespace

Value types

Type inference only applies to JSON output.

This tool runs entirely in your browser. Your input never leaves your device.

About CSV to JSON Converter

Converting CSV to JSON is five lines of code and yet everyone rewrites it, because the awkward cases are not the happy path: a header row that is really data, a name containing a comma inside quotes, a file saved as tab-separated with a .csv extension, a '1234567890123' phone number that JSON infers as a number and silently loses precision on. This converter exposes those decisions as switches instead of making them for you.

With the header switch on, the first row becomes the keys of every object; with it off you get arrays of values and positional keys. The delimiter field accepts a tab or any character, so TSV and semicolon-separated European exports work without a detour through a spreadsheet. Type inference is off by default — everything arrives as a string, which is the safe answer for postcodes, ids and phone numbers — and switching it on parses numbers, booleans and null where they are unambiguous.

Conversion happens in the page, so the file never leaves your machine: no upload, no retention, no third party reading a customer export.