Notepad++ handles line-break cleanup through its Find and Replace dialog with the Regular expression option enabled, where you can match \r\n, \n, and \r characters and replace them with a single space, an empty string, or a paragraph break. The approach is fast and lives inside the editor you already have open, but the regex flags are easy to get wrong, and a slip like enabling the wrong Search Mode, picking the wrong escape, or leaving the Replace with field empty can collapse spaces, join words, or strip punctuation you meant to keep. A more focused alternative is to copy the text out of Notepad++, paste it into the Line Break Remover, choose one of three explicit modes, review the detected and removed token counts, then copy the result back into your document. All processing happens locally in your browser, no upload is required, and the five recognized line-break tokens (CRLF, standalone CR, standalone LF, U+2028 LINE SEPARATOR, and U+2029 PARAGRAPH SEPARATOR) are counted and transformed according to the mode you selected rather than guessed at from the editor's render.
Why Notepad++ regex is fast and where it can bite
Notepad++ opens Find and Replace with Ctrl+H and exposes a Search Mode panel at the bottom of the dialog. Switch the panel to Extended and you can type \r\n, \n, or \r directly into the Find what field; switch to Regular expression and the same patterns work with the same escape style. Replace them with a single space, leave the field empty to delete them, or insert two \r\n tokens to keep a paragraph break.
The editor handles the actual file on disk, so nothing leaves your machine, and a multi-megabyte log file processes as quickly as Notepad++ can stream it. The catch is that regex flags and dialog settings are unforgiving. A stray checkbox, a miscounted token, or an empty Replace with field collapses punctuation, joins words the source never meant to join, or — when Extended mode meets a Windows file — doubles up the carriage returns because the editor writes back the unchanged pair. None of this is hidden; it is the documented behavior of the dialog, but it is easy to miss when you are in a hurry.
Five line-break tokens worth recognizing
The line-break character you need to remove depends on where the text came from, and a faithful remover should treat all of them explicitly rather than pattern-matching only what the editor renders as a newline.
- CRLF (U+000D U+000A) — the Windows pair. The remover treats it as one combined token so statistics stay honest about what was actually present in the source.
- Standalone LF (U+000A) — the Unix, Linux, and modern macOS break. Almost every modern export uses this on its own.
- Standalone CR (U+000D) — older Classic Mac files, some generated data, and a handful of imported records still carry CR alone, and they survive copies unchanged.
- U+2028 LINE SEPARATOR — a Unicode break that document systems and certain exporters insert invisibly, often without any visible change in the editor.
- U+2029 PARAGRAPH SEPARATOR — a stronger Unicode break that signals paragraph intent rather than a soft wrap, and that some word processors write in place of plain CR or LF.
The ECMAScript specification lists line terminators as a defined set, and MDN's lexical grammar reference restates the same tokens for JavaScript. A browser-based remover that walks the string can therefore catch every member of that set in a single pass without having to know which operating system produced the file or how the editor is rendering it.
How to clean Notepad++ text with the Line Break Remover
- Open the file in Notepad++ and select the lines you want to clean, or press Ctrl+A to grab the whole document. Press Ctrl+C to copy.
- Open the Line Break Remover in a new browser tab and paste the copied text into the input area.
- Pick one of the three explicit modes — replace every line-break token with a single space, replace every token with an empty string, or preserve paragraph boundaries while joining single wrapped lines.
- Click the process button and read the three counters: detected tokens, removed tokens, and remaining tokens. A mismatch between detected and the sum of removed plus remaining tells you a paragraph was retained on purpose.
- Click the copy button to send the transformed text to your clipboard. If the browser blocks clipboard access, the result stays on screen so you can select it manually with Ctrl+A and Ctrl+C.
- Switch back to Notepad++, place the cursor where the cleaned text should land, and paste with Ctrl+V. Save the file once the result looks right.
Editing the input or switching the mode clears the previous result, the validation message, and the clipboard status. That guard is intentional: it stops a stale asynchronous clipboard completion from overwriting a newer copy you started, and it keeps the on-screen output honest about which generation of input produced it. The input budget is 1,000,000 UTF-16 code units, and an over-sized paste is rejected with an explicit message before any transformation runs, so text is never sliced, sampled, or silently capped.
Three modes compared
The three modes share the same recognized-token set and the same statistics, but they map tokens to output characters differently.
| Mode | One token becomes | Two consecutive tokens become | Three consecutive tokens become |
|---|---|---|---|
| Replace with one space | one ordinary space | two ordinary spaces | three ordinary spaces |
| Remove completely | empty (adjacent text joined) | empty (adjacent text joined) | empty (adjacent text joined) |
| Preserve paragraphs | one ordinary space | two LF characters (one blank line) | two LF characters, with one token counted as removed |
Replace with one space applies one space per recognized token, so two consecutive LF tokens become two spaces rather than one — the tool deliberately does not collapse the result. Remove completely inserts no replacement at all, so words separated only by a line break end up joined. Preserve paragraphs treats any uninterrupted run of two or more tokens as a single paragraph boundary and rewrites that run to exactly two LF characters; a run of exactly one becomes one space. Any non-newline character sitting between two breaks — a space, a tab, or a non-breaking space — splits them into separate runs, and each side is transformed on its own.
What the remover deliberately leaves alone
The contract is narrower than a generic whitespace cleaner. Spaces, repeated spaces, tabs, non-breaking spaces, and any leading or trailing non-newline whitespace pass through untouched. The tool never trims the start or end of your input, collapses repeated spaces, expands tabs, swaps non-breaking spaces for ordinary spaces, normalizes Unicode text, or changes punctuation and letters. Leading and trailing line breaks are still transformed according to the mode you picked — they are not protected just because they sit at the edge of the input.
The remover also does not parse Markdown, HTML, CSV quoting, source-code syntax, postal addresses, or any semantic document structure. A line break inside a Markdown paragraph and a line break between two Markdown paragraphs look identical in raw text, so the tool cannot know which one carries meaning for you. Use paragraph mode only when blank-line runs in your source genuinely represent paragraphs, and review the output before committing to remove mode on natural language, because deleting breaks without spaces will intentionally join words that were never meant to meet.
Common Notepad++ tasks that fit this workflow
Hard-wrapped prose copied out of a PDF or a chat transcript arrives as one sentence per line in Notepad++, which is awkward to reformat. Pasting the block into the remover with Replace with one space rejoins the sentence without losing the spaces between the original lines. Spreadsheet exports and CSV dumps from older tools sometimes keep CR-only line endings; the remover catches those alongside the LF endings that a typical editor would render the same way.
Prompt text being prepared for an API call benefits from remove mode when the prompt should be a single line, and from preserve-paragraph mode when the prompt carries structured sections separated by blank lines. Cleaning copied PDF text, stripping record separators before another controlled transformation, and tidying OCR output are all cases where a focused, browser-local pass is faster than yet another regex tweak in the editor.
Notepad++ remains the right place to do structural edits, regex-driven refactors, and multi-gigabyte file processing. For the narrow job of transforming recognized line-break tokens with predictable, reviewable counts, the Line Break Remover is a faster path that stays inside your browser, refuses to touch anything you did not ask it to change, and caps input at one million UTF-16 code units so an over-sized paste is rejected up front instead of silently truncated.
If you're weighing options, Does Remove Text Formatting Parse HTML and Strip Tags? covers this in detail.
If you're weighing options, Remove Accents from Text Online Without Losing Letters covers this in detail.