Paste a comma-separated list and get back a clean, formatted JSON array. Trimmed values, no empty items, runs entirely in your browser.
Comma to JSON array
Drop in a comma-separated list, tags, categories, a row copied from a spreadsheet, and get back a formatted JSON array: each value trimmed, empty items dropped, indented and ready to paste into code, a config file or a test fixture.
It's a local tool. The split runs in your browser, not on a server, so nothing you paste is uploaded and there's no cap on how much you convert or how often.
Where the format comes from
The comma became the standard separator for tabular text because CSV, formalized in RFC 4180, made it the default, and every spreadsheet or export tool still reaches for it first. A tag list, an email list, a category set: whatever generated it probably joined the values with commas because that's the easy path.
The trouble is that some real values have a comma inside them: a name like 'Doe, John', an address, a number like '1,000'. A real CSV parser handles that with quoting rules. This app doesn't. It's a plain delimiter split, every comma is a boundary, quoted or not, which is exactly right for a simple list and exactly wrong for genuine quoted CSV.
Workflow
No settings to configure, nothing to install.
Why it matters
Run a plain comma split on real CSV pulled from accounting software or a contact list and a value like 'Smith, Jane' comes back as two array items instead of one. A price like '2,499.00' splits into '2' and '499.00'. An address with a city and state gets cut apart at a point you never intended.
None of that is the app misbehaving, it's a comma split doing exactly what a comma split does. The mismatch is between the tool and quoted data, not a bug in either.
The real distinction
This converter is built for the common case: a plain list where no value itself contains a comma, which covers most tag lists, category names and single-word spreadsheet columns. For that case a plain split is the right tool and faster than opening a script for a one-off job.
Genuine CSV with quoted, comma-containing fields needs a real CSV parser that understands quoting, not a single delimiter character. If your source data has quotes around fields, scan the result for split values before trusting it.
Straight answer
No. This is a delimiter splitter, not an RFC 4180 CSV parser, so it has no idea what a quoted field is. A comma inside quotes gets treated the same as a comma separating two fields.
For a plain list that distinction never matters. For a real CSV export with quoted fields, use a CSV-aware tool instead, or check every quoted value by hand afterward.
Who it's for
Developers use it to turn a comma-separated tag list or a set of IDs pasted from a bug report into a JSON array for a config file or fixture. No-code builders use it to push a spreadsheet column into the array shape a form step expects.
Content and SEO teams use it to turn a comma-separated keyword list into JSON for structured data. Anyone with a short, simple, unquoted list sitting in a chat message or an email uses it as the quickest way to valid JSON without opening a code editor.
Paste the list above and press Convert. Each value is trimmed and returned as a formatted JSON array ready to copy.
Yes, no signup, no paste limit, no run limit. It runs on your own device so there's nothing to meter.
No. The split runs entirely in your browser. Nothing is transmitted or stored.
No. It splits on every comma whether it's quoted or not, so 'Smith, Jane' inside quotes still becomes two items. Use a CSV-aware parser for quoted data.
They're trimmed automatically. 'red, blue , green' comes back as three clean items.
The empty item between them is dropped, and a trailing comma at the end doesn't produce a blank final item either.
Not with this tool, a comma inside a number looks the same as a comma between values, so it splits there too. Strip thousands separators first.
Yes, no length cap and no run limit. Very large pastes depend on your device's memory, not on any limit here.
Yes, the layout stacks on narrow screens and works the same in a mobile browser.
This one always splits on a comma. The custom delimiter tool lets you type any separator, useful when your data uses something else, or when commas appear inside the values.
Yes, it's built with JSON.stringify rather than assembled as text. What it can't guarantee is that the split happened at the right places for your particular data.
If it was copied and joined with commas, yes. If copied directly from a spreadsheet it more likely arrived tab-separated, in which case use the tab to JSON array converter.
No. Every comma-separated value becomes its own array item, repeats included.
Not yet. Paste, convert, copy is the fastest route for one list at a time.
Yes, no address contains a comma, which makes it exactly the kind of simple list this app is built for.
No, this converter only splits on commas. Semicolon-separated data, common in European exports, has its own tool.
Empty items get dropped automatically rather than shown blank, so if a value's missing it was likely two commas with nothing meaningful between them.
If your values were quoted for CSV purposes, remove those quote characters yourself, since this tool doesn't interpret quotes, only commas.
Yes, the output is plain JSON text, so you can run it through the JSON prettifier or minifier if you want to reformat further.
No fixed limit. Thousands of items convert the same way as five, capped only by your browser's memory.