A precise comma to JSON array converter: trims values, drops empty items and returns formatted JSON, computed locally with no quoting logic implied.
Free · no account · nothing leaves your browser
The tool
This tool takes a comma-separated list and returns a formatted JSON array: each value trimmed, empty items dropped, output indented at two spaces so it reads cleanly in a diff or a code review.
The conversion runs entirely in JavaScript in your browser. There is no request to a server to queue or log, which is also why there is no run limit, nothing here costs us anything to serve you.
Where the format comes from
The comma is the default field separator for tabular text because CSV, standardised as RFC 4180, made it so, and most export tools still default to it. A tag list, a category set, an ID list pulled from a database: the path of least resistance for whatever generated it is a comma-joined string.
RFC 4180 also defines quoting: a field that itself contains a comma is wrapped in double quotes, and a parser that respects that rule treats a quoted comma as content, not a boundary. This tool does not implement that rule. It is a single-character delimiter split, every comma is a boundary, quoted or not.
How it works
No configuration, no network round trip to account for.
Why it matters
Feed this converter, or any plain comma split, a real CSV export from accounting software or a CRM and a quoted value like 'Smith, Jane' returns as two separate array entries instead of one. A price formatted '2,499.00' splits at the thousands comma. An address field with a city and state name splits somewhere you did not intend.
None of that is a defect in the tool. A single-character split does precisely what its name says: split at every occurrence of that character. The failure sits in the mismatch between an unquoted split and quoted source data, not in either one alone.
Scope, stated precisely
This converter is scoped to the common case: a plain list where no individual value contains a comma, which covers the large majority of tag lists, category names and single-word spreadsheet columns pasted into a text field. For that case a single-character split is correct, fast, and considerably less overhead than a full CSV parser for a one-off conversion.
Genuine RFC 4180 CSV with quoted, comma-containing fields is a different problem and needs a parser that understands quoting. If your source has quoted fields, treat this tool's output as a draft and check every quoted value before you rely on it.
Straight answer
No. This is a delimiter splitter, not a CSV parser, and it has no concept of a quoted field. A comma sitting inside quotes is indistinguishable, to this tool, from a comma separating two fields.
For a plain, unquoted list, that limitation never surfaces and the result is exactly correct. For a genuine CSV export with quoted fields, use a CSV-aware parser instead, or verify every quoted value in the output by hand.
Who it's for
Developers use it to turn a comma-separated tag list, an enum of allowed values, or an ID list pasted from a ticket into a JSON array for a config file or a test fixture. Teams building internal tools use it to move a spreadsheet column into the array shape a form or an automation step expects.
Content and SEO teams use it to turn a comma-separated keyword list into JSON for a structured data field. Anyone with a short, unquoted list sitting in a message or a spreadsheet cell reaches for it as the fastest route to valid JSON without opening an editor.
All answered in full, nothing to click open.
Paste the list into the input field and press Convert. Each value is trimmed and returned as a formatted JSON array.
Yes. No signup, no length cap, no run limit, because the conversion runs on your own device rather than a server we're metering.
No. The split runs entirely client side. Nothing is transmitted, stored or logged.
No. It splits on every comma regardless of quotes, so a value like 'Smith, Jane' inside quotes still becomes two items. Use a CSV-aware parser for quoted data.
It's trimmed automatically. 'red, blue , green' returns as three clean items with no leading or trailing spaces.
The empty item between them is dropped, and a trailing comma at the end of the list doesn't produce a blank final entry.
Not with this tool. A comma inside a number is identical, to a plain split, to a comma between values. Remove thousands separators first.
No. There's no cap and no run limit, the practical ceiling is your device's own memory.
Yes. The layout adapts to narrow screens and behaves the same on mobile.
This tool is fixed to a comma. The custom delimiter tool accepts any separator you type, which matters when your data uses something else or when commas appear inside the values themselves.
Yes, it's constructed with JSON.stringify rather than assembled as text. What isn't guaranteed is that the split points match your intent for quoted or comma-containing data.
If it was copied and joined with commas, yes. A direct spreadsheet copy more often arrives tab-separated, which has its own converter.
No. Every comma-separated value becomes its own array entry, duplicates included.
Not currently. This is a single-paste, browser-based converter.
Yes. No valid address contains a comma, which puts it squarely in the case this converter is scoped for.
No, this tool is fixed to commas only. Semicolon-delimited exports, common outside the US, have a dedicated converter.
Empty items are dropped rather than returned blank, so a missing value usually means two commas in a row with nothing meaningful between them.
If your source values were quoted for CSV purposes, remove those quote marks yourself, this tool doesn't interpret quotes, only commas.
Yes, it's plain JSON text, so it can be passed through the JSON prettifier or minifier for further formatting.
No fixed maximum. A list of a few thousand items converts the same way as one of five, bounded only by browser memory.
Trimmed values, dropped empty items, computed locally with no run limit.
Open the converter