Tidy notes without removing paragraph breaks
With the defaults, three consecutive blank lines become one blank line, and multiple ordinary spaces become a single space. A paragraph separator remains visible.
No changes.
Operations run in a fixed order: Unicode, special spaces and quotes, zero-width spaces, line endings, line trimming and spacing, blank lines, duplicate lines, then text edges. All processing stays in your browser. Maximum input: 250,000 UTF-16 code units.
Text processing is local to this browser. The original input is kept separately from the generated preview until you reset or leave the page.
How to use the Text Cleaner
- 01
Paste your source text or load the example.
- 02
Choose cleanup operations. The defaults trim ordinary whitespace, normalize line endings, and keep at most one consecutive blank line.
- 03
Enable more specific operations only when you need them, such as replacing nonbreaking spaces or removing duplicate lines.
- 04
Review the cleaned text, then copy it or download a UTF-8 .txt file. Reset clears the text and restores the defaults.
Examples
Remove repeated list entries
Enable duplicate-line removal to keep the first copy of each nonblank line after trimming and spacing. “Apple” and “apple” remain separate because comparisons are case-sensitive.
Preserve emoji when removing zero-width spaces
The optional zero-width operation removes only U+200B and U+FEFF. It preserves U+200D joiners, U+200C non-joiners, variation selectors, and Unicode tags used by scripts or emoji.
A predictable order of operations
Cleanup first applies optional NFC normalization, special-space replacement, quote replacement, and zero-width-space removal. It then processes line endings, trims and collapses spaces within each line, handles blank lines and duplicates, and finally trims text edges. Duplicate comparisons therefore use the already-cleaned line. Removing all blank lines takes precedence over keeping one blank line.
Ordinary whitespace and meaningful formatting
Line trimming and space collapsing target ASCII spaces and tabs. Nonbreaking spaces are changed only when selected. Normalizing line endings converts CRLF, CR, and Unicode line separators to LF. These operations can change indentation, deliberate spacing, or document layout; use Deselect all and enable a narrower set when formatting matters.
What to know
- The cleaner operates on plain text; it does not parse HTML, Markdown, CSV, source code, or rich-text formatting.
- Input is limited to 250,000 UTF-16 code units. Trimming and spacing operations can change meaningful indentation.
Common questions
Does cleanup remove every invisible Unicode character?
No. The optional zero-width operation removes only U+200B and U+FEFF. Use the invisible character detector to inspect direction marks, joiners, unusual whitespace, and other hidden code points separately.
Does NFC normalization remove accents?
No. NFC composes canonically equivalent sequences where possible, such as e plus a combining acute accent into é. It does not strip accents, translate text, or apply compatibility normalization.
Are duplicate lines compared before or after trimming?
After the selected Unicode, special-character, trimming, and spacing operations. Comparisons are exact and case-sensitive, and the first nonblank occurrence is kept.
Can I preserve the original line endings?
Yes. Turn off Normalize line endings. The remaining original line terminators stay intact unless the corresponding lines are removed. Browsers may already normalize line endings when text is entered into a textarea.