PasteCleanly / Text workshop

Split, join and number lists

Change how a list is laid out while keeping the contents of each item.

Text and opened files stay in this tab. How privacy works

Try a sample

Original
Paris,"New York, NY",Berlin
Result
Paris
New York, NY
Berlin

Choose Split into lines and select Comma. Quotes keep New York, NY together as one entry. Join lines quotes fields containing the selected separator or quotation marks and doubles quotes inside a field.

Number or label each entry

Use Number lines to add 1., 2. and so on. Choose Prefix lines to add a custom label or a bullet such as - . Turn on Skip empty entries if blank rows should not be included.

One row or one list at a time

Splitting is for a single record, not a complete CSV table with multiple rows. Values with internal newlines are outside the scope of this tool. To prepare a list first, try Sort and clean lines.

Split, join and label a single list without damaging its values

Choose one operation for one list

Split into lines is for a single row of separated values. Join lines takes one item per line and makes one delimited row. Number lines and Prefix lines keep one item per line but add visible labels. Think about what the result needs to be before choosing: a list for reviewing, a row for importing, or a sequence ready to paste into a document. Do not use the same setting simply because all three jobs start with some copied text.

A list has one kind of item repeated, such as cities, labels or identifiers. A table has several related fields per record. If your source has multiple records and each has multiple columns, the separator is only one part of the structure. Use the CSV and TSV converter for a table instead. A list joiner cannot infer how to reconstruct headers or the relationship between several columns.

Start with a copy of the original and test a sample containing a value with punctuation. A join or split can appear correct on three simple names but fail the real intent when a city contains a comma. Pick a sample that tests your actual constraints, not just the shortest possible case.

Split a quoted value without breaking it into pieces

Paste the following as a single row and select Comma under the separator. Split into lines should produce Paris, New York, NY and Berlin as three items, with New York, NY on its own line.

Paris,"New York, NY",Berlin

The quotation marks delimit the second field. They are not part of the city name. To represent a literal quote inside a quoted value, double it in the source. Review the original if the parser reports malformed quotes. Removing all quotation marks to silence a warning can turn one field into several and change the list you are trying to recover.

If the comma is not the separator in your export, choose the actual delimiter before trying to split. Tabs can look like a group of spaces, and a vertical pipe can be part of the value in a different format. Look at the source application's export settings or use the invisible character inspector on a small sample. If every item is returned as one line, first check whether you selected the wrong separator rather than assuming the converter did not run.

Paste this row into the list formatter

Join lines and inspect the quoting in the result

Join lines is useful when the destination expects one record with several values. Choose the delimiter it expects rather than choosing the one that makes the output look most familiar. The converter quotes fields that contain the delimiter or a quotation mark. It doubles an internal quotation mark where needed so the receiving parser can recover the original value. A quoted value in the result is not necessarily a change to the item itself.

Take the three city lines from the previous example and join them with Comma. The city containing a comma needs protective quotes. Join the same lines with Pipe and the comma is no longer the selected separator. The result can look different while carrying the same three items. Test the actual recipient rather than replacing every quote or delimiter by hand.

An empty line needs a decision. In a list of optional values, a blank field can mark a position that matters. In a casual list assembled from notes, it may simply be a spacer. Use Skip empty entries only when dropping those positions is appropriate. Compare the original item count with the split result after a small round trip, and inspect any values at the beginning or end of the list.

Add numbering or a label only after cleaning the list

Number lines is useful for a checklist or a sequence you want a reviewer to refer to. Prefix lines can add a bullet, a project label or another fixed string to every item. Keep the source separately if the result will later be consumed by a system that expects raw values. A line beginning with 1. contains that text; it is not a formatted list object or a property the destination can always remove automatically.

Apply numbering after sorting, filtering or removing repeats. If you add a different number to every line first, two otherwise identical items will no longer be exact duplicates. Sorting numbered strings can also preserve the previous numbering instead of sorting the intended values. Use Sort and clean lines or Remove duplicate lines on the underlying list first.

Check any lines that already have a prefix. Adding a bullet to an existing bullet list can produce two markers per item, and another paste may render them in an unexpected way. If you need to replace a known literal marker, use Find and replace on a small sample, then apply a new prefix to the clean list. Review both the first and last entry in the destination.

Separate one delimited row from a multi-record table

The split action is deliberately for one row. An entire CSV table may contain multiple records and quoted values with embedded line breaks. Those breaks cannot safely be treated as separators between independent list items. If the input came from a table, identify the column that contains the items, extract that column with a table-aware tool and verify its output before trying to label or join the values.

Conversely, a pasted list may contain no record structure beyond one item per line. It does not need a header or a conversion to JSON just to be readable. If you need a machine-readable array, agree on the destination format rather than assuming a joined line is a valid substitute for it. Use the CSV and JSON converter only when the source or target fits that tool's flat table model.

If you are copying values from a spreadsheet selection, paste a small example first. A single column usually produces newlines between cells. A multi-column selection can produce tabs as well. Those are distinct structures. Separate the needed values in the source instead of mixing both dimensions into one string and expecting a delimiter choice to recover the missing relationships.

Verify the result where it will be pasted

For a report, paste into the destination and inspect how numbering or bullets render. For an import, reparse the output with the intended delimiter and verify a value with punctuation, an empty value and the last item. A successful preview in one editor does not guarantee that another application uses the same quote rules. Keep the original as a reference if you need to repeat the operation.

If you are comparing lists, check membership before adding presentation labels. The list comparison tool expects exact lines, so extra prefixes or numbering can make shared values look different. Compare clean values first, then add labels to a separate report for a human reader. The guide to preparing lists and tables covers when to use each of these representations.

For an ongoing workflow, note the separator and whether empty entries were preserved. Include a small before-and-after example containing a delimiter inside a value. This is more useful than a vague instruction to “make it comma separated.” Someone using the workflow later can verify not just that the result has commas, but that it still has the intended items in the intended order.

Check the first and last values for accidental separators

A trailing delimiter in a delimited row can represent an empty final field. An extra pasted blank line can also look like a missing item once you switch between representations. Inspect both ends of the sample before running a full conversion. If the receiving process uses field position, keep intentionally empty positions and document what they mean. If the task is a readable checklist, remove only blanks that are not carrying structure. These are two legitimate choices with different results, and the list formatter cannot decide between them from the text alone.

Use literal list labels only where the destination needs them

A written number or bullet is useful in plain-text notes. A rich document editor may already number its list items automatically. In that case, paste the unnumbered values and use the destination's list control instead. Otherwise you can end up with two numbers or with labels that do not update when a new item is inserted. Keep an unnumbered source when the list will be edited again.