Clean a pasted list without silently changing its meaning

Keep the original and identify the record boundary

Save an unchanged copy of the source and decide what one line represents. These tools operate on whole lines. They do not identify a matching column in a CSV, preserve a spreadsheet schema, or recognize a quoted CSV field that contains an embedded newline.

Use the six-line sample below. The fourth line has one space before beta and one after it; the fifth line is blank. Decide that, for these display labels, letter case and spaces at the edges are insignificant. That is an explicit choice for this example, not a safe assumption for every list.

Alpha
beta
ALPHA
 beta 

Gamma

Remove blank records without erasing useful indentation

In Remove Empty Lines, choose Remove whitespace-only lines and leave Trim each line unchecked. The blank fifth line disappears, and the spaces surrounding the fourth line remain. The result has five records. This keeps blank-record removal separate from the decision to alter each record’s text.

Remove empty lines handles lines with no characters. Remove whitespace-only lines also handles lines containing only spaces or tabs. If you enable Trim each line first, those whitespace-only lines become empty before the selected operation runs.

For prose, Collapse multiple empty lines can retain one paragraph separator. For source code, edge whitespace may be indentation with real meaning. Choose the operation according to the destination rather than assuming all visible blank space is disposable.

Make the duplicate rule explicit

Paste the original sample into Remove Duplicate Lines. Enable Trim whitespace, Ignore case, and Ignore empty lines, then choose First occurrence under Keep. The expected output is Alpha, beta, and Gamma on separate lines. Trimming makes the two beta records equal, and ignoring case makes Alpha and ALPHA equal.

Change Keep to Last occurrence and run the same original input again. The result starts with ALPHA, followed by beta and Gamma. The surviving lines keep their relative order from the original; the tool does not sort them automatically.

If the list holds case-sensitive identifiers or URLs with case-sensitive paths, leave Ignore case off. If spaces are part of a record, leave trimming off. Deduplication compares text after your selected transformations; it cannot determine whether two labels refer to the same person, product, or database record.

First occurrence:
Alpha
beta
Gamma

Last occurrence:
ALPHA
beta
Gamma

Use numeric sorting only for numeric records

For a separate test, paste 2, 10, and 1 on separate lines into Sort Lines. Choose Numeric ascending to get 1, 2, 10. A → Z compares text, so this simple digit-only sample instead gives 1, 10, 2. Neither result is inherently wrong; they represent different sorting rules.

Remove blank records and labels before numeric sorting. This implementation removes commas before converting each record to a number. A grouped value such as 1,000 is read as one thousand, but a decimal-comma value such as 1,5 is read as fifteen. Do not use that mode on a decimal-comma list without first converting the format deliberately.

Keep identifiers such as 001 and 1 distinct when their spelling matters. Numeric sorting can give them equal numeric values while preserving the displayed strings, and it uses JavaScript number precision. Sorting whole CSV rows numerically does not select a numeric column; use a column-aware tool for that task.

Input:
2
10
1

Numeric ascending:
1
2
10

A → Z:
1
10
2

Inspect changes and investigate look-alike text

Compare the original and cleaned versions in Text Difference using Line difference. Leave Ignore case and Ignore whitespace unchecked when auditing what changed. A moved line can appear as a removal and an addition, so review both the removed records and the surviving values instead of judging the cleanup only by the final line count.

Two strings can look identical while containing different Unicode code points. For example, an accented letter can be stored as one precomposed character or as a base letter followed by a combining mark. These cleanup tools do not automatically apply Unicode normalization, so visually identical records can survive exact deduplication. Character Counter can help reveal different code-point and UTF-8 byte counts, although it does not identify every invisible character for you.

Normalize text only when that transformation is appropriate for the receiving system, and keep the original for comparison. Alphabetic sorting uses the browser’s locale comparison, so accented-letter ordering can also vary with locale. Check the final output in the application that will consume the list.

Record the cleanup choices so the result is repeatable

When sharing a cleaned list, state the blank-line mode, trimming choice, case rule, first-or-last occurrence choice, and sort order. For this sample, six original lines become three retained labels with trimming, case-insensitive deduplication, empty-line removal, and first-occurrence preservation.

UtilBrix performs these text operations in your browser. The transformation tools accept up to 500,000 JavaScript string units per input; complex text comparisons can still hit a processing timeout. For a large export, work on a representative sample first and check that the same record assumptions hold throughout the source.

Try the tools in this guide

• Character Counter — Keep track of characters, bytes, and text limits.
• Remove Duplicate Lines — Keep your list tidy by removing repeated lines.
• Sort Lines — Put your lines in alphabetical or numerical order.
• Remove Empty Lines — Clean up blank lines and extra whitespace.
• Text Difference — Compare two texts and see exactly what changed.

References

• MDN: Unicode normalization and equivalent strings
• MDN: Locale-aware string comparison