Comma to JSON Array

The goal of this page is simple: turn a messy, human-written comma list into a clean, machine-friendly JSON array. People tend to write lists with extra spaces, trailing commas, mixed separators, and accidental blanks. JSON does not allow any of that. It has to be a well-formed array with quotes around each string and proper escaping for characters like quotation marks and backslashes.

This tool uses deterministic rules so you always know what you will get. It splits your input on commas and line breaks. Each token is trimmed. Empty tokens are removed. This means an input like a, b, , c, becomes ["a","b","c"]. The editor stays editable so you can paste, convert, then quickly adjust any edge case.

• Trim whitespace

  Leading and trailing spaces are removed from each value so copy-paste artifacts do not leak into JSON.
• Ignore empty values

  Blank entries created by consecutive commas or a trailing comma are dropped, and the tool reports how many were ignored.
• Preserve characters

  Characters inside a value are kept as-is. JSON escaping is handled by the encoder so quotes and backslashes remain valid.
• No CSV quoting rules

  If your list contains commas inside quotes, this tool will still split on commas. For true CSV parsing, use a CSV-specific converter.

Many tools and APIs accept a JSON array but not a plain comma-separated list. A classic example is passing a list of tags, IDs, or allowed values into an API request body, a configuration file, or a deployment template. If the destination expects JSON and you paste raw text, it either fails validation or silently interprets your string as one value.

Converting a list to

A good mental model is that you are preparing data for code, not for people. In JavaScript, you can paste the output directly into a constant, pass it as part of a request payload, or store it in local configuration. In many no-code tools, a field that says “array” still expects JSON syntax. A valid JSON array keeps you out of the gray area where a platform tries to guess what you meant.

This page intentionally avoids hidden heuristics. That keeps results predictable, but it also means certain inputs need a quick manual check. The most common edge case is a value that itself contains a comma, like a city name formatted as Toronto, ON. In CSV, that would be quoted. Here, it will be split into two values. If you have comma-containing data, you should use a proper CSV tool or replace those commas before conversion.

Another edge case is mixed separators. People paste lists separated by newlines, then add commas on some lines. This tool accepts both because it splits on commas and line breaks. The tradeoff is that it does not understand more complex formats like semicolon-delimited records or nested data. If you can normalize your list first, you will get cleaner output.

One more practical edge case is hidden whitespace. Values copied from spreadsheets or PDFs can contain non-breaking spaces or invisible separators. Trimming removes the obvious padding, but it cannot reveal every hidden character by sight. If your destination rejects the array even though it looks fine, paste the original list into a whitespace-cleaning tool first, then convert again.

The output is generated using the browser's JSON serializer, which safely escapes quotes, backslashes, and control characters. That is the main reason to use a converter instead of manual quoting. Even if your list includes characters like " or newline sequences, the resulting JSON stays valid.