Comma to JSON array
What the comma to JSON array converter does
Paste a comma-separated list, such as a row of tags or a column of values copied out of a spreadsheet, and this tool returns a properly formatted JSON array. Each item is trimmed of stray spaces, empty items between repeated commas are dropped, and the result is pretty-printed with two-space indentation so it is ready to paste straight into a config file, a test fixture or an API payload.
It runs in your browser. Nothing you paste is sent anywhere, there is no signup, and there is no limit on how much text you convert or how often you come back to do it.
Where the format comes from
Comma-separated values, in plain terms
The comma became the default field separator for tabular data because it is what CSV, defined in RFC 4180, standardised on decades ago, and it is what every spreadsheet, database export and API still defaults to when you ask for plain text output. A row of tags, a list of email addresses, a set of category names: all of it tends to arrive comma-separated because that is the path of least resistance for whatever exported it.
The catch is that plenty of real values contain a comma of their own. A name written 'Doe, John', an address with a city and state, a number written '1,000': all of these have a comma sitting inside the value, not between values. A proper CSV parser handles that by quoting the field and treating a quoted comma as content rather than a boundary. This tool does not do that. It is a plain delimiter split: it treats every comma as a boundary, quoted or not.
How it works
How to convert comma-separated text to a JSON array in three steps
There is nothing to install and no format to learn first.
- Step 1
- Paste your comma-separated list into the input box.
- Step 2
- Press Convert. The split, trim and formatting happen instantly on your own device.
- Step 3
- Copy the JSON array from the output box, ready to paste wherever it needs to go.
Why it matters
What a naive comma split actually breaks
Run this tool, or any plain comma split, on real CSV exported from accounting software or a contact list, and a value written 'Smith, Jane' comes back as two separate array items instead of one. A price formatted '2,499.00' splits into '2' and '499.00'. An address field with a city and a state name splits somewhere you did not intend.
None of that is a bug in the tool. It is exactly what a comma split is supposed to do: split on every comma. The failure is a mismatch between the tool and the data, not the tool doing the wrong thing with the data it was given.
The real distinction
Why simple lists work here and quoted CSV does not
This converter is built for the common case: a plain list where no individual value contains a comma, which describes most tag lists, category names, short keyword lists and single-word columns copied out of a spreadsheet. For that case, a plain split is exactly right, and it is faster than opening a spreadsheet tool or writing a script for a one-off conversion.
Genuine CSV with quoted fields, embedded commas and possibly embedded line breaks inside a cell is a different problem that needs a real CSV parser, one that understands quoting rules rather than a single delimiter character. If your source data has quotes around any field, check for embedded commas in the result before you trust it.
Straight answer
Does this parse full CSV files?
No, and it is worth saying plainly rather than letting you find out the hard way. This tool is a delimiter splitter, not an RFC 4180 CSV parser. It has no concept of a quoted field, so a comma inside quotes is treated exactly the same as a comma between fields.
For a simple list, that distinction never comes up and the result is exactly right. For a genuine CSV export with quoted, comma-containing fields, run it through a CSV-aware tool instead, or check every quoted value in the result by hand before you use it.
Who uses it
Who uses a comma to JSON array converter, and when
Developers use it to turn a comma-separated tag list, an enum of allowed values, or a list of IDs pasted from a bug report into a JSON array for a config file or a test fixture. No-code and low-code builders use it to get a spreadsheet column into the array shape a form field or an automation step expects.
Content and SEO teams use it to convert a comma-separated keyword list into JSON for a structured data field. Anyone who has a short, simple, unquoted list sitting in an email, a spreadsheet cell or a chat message uses it as the fastest way to get that list into valid JSON without opening a code editor.