Split a CSV row into lines

This parser understands standard quoted fields, doubled quote escapes, empty columns, and an optional final line ending. It is useful when a row copied from a spreadsheet, export, log, or command output needs to become a list for a document, form, script, or comparison. The same deterministic conversion runs in the browser and through the API, with no network lookup or format guessing.

Paste one complete CSV record

Provide exactly one comma-separated record in the text field. A simple input such as <code>red,green,blue</code> becomes three lines in the same order. Empty columns are not discarded: <code>red,,blue,</code> produces four values, including the empty second and final fields. That behavior matters when column positions carry meaning, because silently dropping blanks would shift every later value. You may include one final LF, CRLF, or CR record terminator, which is convenient when the row was copied from a file or terminal. Any additional record separator outside a quoted field is rejected because this capability is intentionally for one row, not an entire CSV document. It does not trim spaces or reinterpret numbers, dates, booleans, or null-like words. The characters in each field remain the characters supplied by the user after CSV quote syntax is decoded. This makes the conversion predictable for identifiers, labels, addresses, spreadsheet cells, and machine-generated values where automatic cleanup could corrupt meaningful content.

Quoted fields are parsed as CSV, not split blindly

A plain string split at every comma fails as soon as a field contains an address, product description, or sentence with punctuation. This capability uses a stateful CSV parser instead. When a field begins with a double quote, commas remain part of that value until the matching closing quote. Two consecutive double quotes inside a quoted field decode to one literal double quote, following common CSV escaping rules. Line breaks may also occur inside a quoted field and remain part of that value. After a closing quote, only a comma or the end of the record is valid; unexpected characters trigger a clear input error rather than producing a plausible but incorrect list. A quote encountered midway through an unquoted field is rejected for the same reason. These strict checks expose malformed exports early and avoid quietly changing their meaning. The parser makes one bounded pass through the input, uses no external service, and always produces the same result for the same text.

Use the vertical result wherever lines are easier

The response provides a newline-joined result for immediate copying, a lines array for structured use, and a field count for quick verification. The joined result is convenient for pasting values into a multiline form, text editor, allowlist, configuration file, issue description, or one-column spreadsheet range. The array is safer for application code because it preserves the boundary of every parsed CSV field, including empty fields and values that themselves contain a line break. Before automating a conversion, compare field_count with the number of columns expected by the receiving system; a mismatch often reveals a missing comma, an extra trailing column, or malformed quoting upstream. Use a full CSV parser when the input contains headers and multiple records, needs delimiter detection, or requires schema validation. This focused capability is best when the source is already known to be a single comma-separated record and the desired transformation is simply from horizontal fields to vertical values. API requests cost $0.002; the browser version performs the same deterministic parsing locally.