Sort and clean lines

Decide whether order is part of the data

Use A–Z or Z–A when the list should be arranged for reading or review. Use Keep original order if the input is already ranked, chronological or deliberately grouped and you only need to remove blank or repeated rows. Order can be information in its own right. A list of meeting tasks may be sequenced by dependency; sorting it alphabetically could make the next step less clear even though every item remains present.

Keep a copy before sorting. Identify whether the first line is a header or an actual item and separate the header if it should stay at the top. This tool sorts all retained lines as values. It does not know that one line describes the list instead of belonging to it. A title can move into the middle after sorting if you leave it in the input.

For a list assembled from several sources, decide whether those sources should stay grouped. If the groups carry labels or different meanings, sort each list separately. A blank line between them does not tell the sorter to treat them as independent groups. If the task is simply to compare membership, use Compare two lists without sorting first.

Test digit sequences alongside ordinary labels

Paste the following sample with A–Z selected. Turn on the two cleanup options if you want a single copy of each nonblank line.

Item 10
    Item 2
    
Item 1
    Item 2

The result should place Item 1 before Item 2 and Item 10 after both. This is a natural comparison of digit sequences within a line, not a numerical calculation on every value. It helps when labels contain suffixes, such as page numbers or numbered files. If you need to order decimal values, negative values or dates as a specific data type, use a spreadsheet or a typed data tool that understands those values.

Try Z–A to confirm which end of the list you want to read first. Then choose Keep original order to check which entries would be removed without any reordering. This separates the two decisions. For example, removing exact repeated filenames while keeping a manually ranked list does not require alphabetical sorting at all.

Do not assume that sorting also normalizes or deduplicates

A line remains as written when the sorter moves it. The comparison can group related spellings for display, but it does not replace accents, correct capitalization or rewrite punctuation. A different locale or a spreadsheet's own sorting rules may produce a different order for accented names or mixed-case labels. Check a representative sample if you need the output to match a specific convention used elsewhere.

Duplicate removal uses exact line equality. Two values can appear next to each other in the sorted list and still count as distinct because one contains a trailing space, a case difference or an invisible character. Decide whether that distinction matters. Use the invisible character inspector on a small pair if the difference is unclear, or use Clean whitespace on a separate copy when the extra whitespace is accidental.

Do not change exact IDs or file paths to make them look alike. If a list is case-sensitive, preserve both variants. If you intentionally create a comparison copy with consistent case or Unicode form, keep the raw source as the authoritative version. The sorter can arrange the values, but it cannot define what a duplicate means in another system.

Choose whether blanks and repeated rows should remain

Removing blank lines is useful for a flat list of individual items. It is not appropriate when a blank row marks a paragraph or separates categories that should not be combined. Try one whitespace-only line as well as a truly empty row. If you need to preserve group structure, clean each group separately and restore the separator between them.

A duplicate may represent an accidental repeated name or a legitimate repeated event. The same timestamp or label can occur in multiple events. Do not drop an entry just because two lines look alike unless the receiving workflow needs one value per distinct item. The duplicate line remover is an alternative for a narrow job where the original sequence must remain intact.

When you enable both cleanup options, review the difference before and after. A report that the list became shorter does not establish why each row disappeared. If a repeated record is important, keep it or count occurrences separately. A unique list is useful for navigation or selecting values; it is not a complete history of what appeared in the source.

Use a table-aware workflow for sorting by a column

This sorter compares the entire line. A CSV row beginning with an order number will usually be ordered by that visible prefix before later fields. If you need to sort a table by delivery date or a particular city, open it in a spreadsheet or another tool that understands columns and value types. Sorting individual cells separately can break the relationship between a row's fields.

A quoted CSV cell can include an internal newline. Sorting the physical lines of that file can move part of a cell away from its record and corrupt the result. Use the CSV and TSV converter to examine a sample or extract one deliberate column first. Verify that the extracted result is a true one-item-per-line list before sorting it here. Check the importer with a row containing a separator inside a quoted value.

For a single-column worksheet, copy only the intended values and leave its header out of the sort. If the source uses a typed date or amount, check whether the copied value preserves its sort meaning as text. A visually formatted date may not sort chronologically when treated as a string. Work in the table application when that distinction matters.

Verify the list before adding labels or sharing it

Inspect the first and last item, a pair that differs by a number and a row whose spelling matters. Check the number of retained lines if you used cleanup. If the output order is surprising, test the smallest pair that demonstrates it and decide whether a natural text sort is appropriate. Do not rewrite the source names merely to obtain the expected ordering.

If the next step is numbering, do it after sorting with Split, join and number lists. Adding sequence numbers first makes those numbers part of each compared string and can preserve an old ordering rather than the new one you intended. For a change report, keep the sorted copy and the original list separately. A line diff will report moves as changes, so use a list comparison if you only need to show that membership stayed the same.

The guide to preparing lists and tables covers when to keep a simple list and when to handle structured records instead. In your own notes, state the sort direction and any cleanup settings. This lets another person reproduce the list without assuming that order or repeated rows were meaningless.

Check prefixes that would dominate the sort

If every line starts with a date, category or bullet label, that prefix is part of the text being compared. If the intended sort key is the name after the prefix, extract the name in a separate working copy or use a table with separate fields. Do not manually shuffle the lines after conversion while claiming the output follows a single reproducible rule.

Inspect near-ties before relying on a specific order

Two names can appear next to each other because the comparison treats them as similar while still preserving their literal spelling. Test a case variant, an accented name and a value with a numeric suffix if the output must match another application's order. A useful rule is to document the ordering you actually need: natural text sort, chronological order or typed numeric order. These are not interchangeable.

If the input contains a category prefix, sorting on the whole line may group that prefix first. Keep the category and value in separate fields if you need to sort by one and then by the other. Use a table-aware editor for the final sorted records.