Line Break Remover – Unwrap Hard-Wrapped Text in Your Browser
Text copied out of a PDF, an e-book, a plain-text email, a terminal window, or a chat log almost never arrives clean. It arrives with hard wraps baked in at roughly 72 to 80 columns, because whatever produced it was formatting for a fixed-width page rather than for your screen. Paste that into a CMS, a form field, a spreadsheet cell, or an AI prompt and you get ragged, broken paragraphs. A line break remover repairs exactly that, and this one runs entirely in your browser — nothing is uploaded.
Why a plain find-and-replace is not enough
The obvious fix is to replace every newline with a space. It works for a single paragraph and destroys everything else. Blank lines between paragraphs vanish, so a three-page document becomes one enormous run-on block. Bullet lists collapse into a sentence. Words that a justified PDF split across lines stay split, leaving exam- ple stranded mid-sentence.
The real distinction is between a soft wrap — a break inserted purely because the line ran out of room — and a break that carries meaning. Soft wraps should become a space. A blank line, a bullet marker, and a numbered list item are structure and should survive. Smart mode makes that distinction automatically and is the correct default for prose.
Choosing a mode
Remove all line breaks flattens everything into one continuous line, which is what you want for minifying a multi-line JSON, SQL, or log payload. Join with separator turns a vertical list into a delimited string — a column of names becomes apple, banana, cherry for pasting into a query or a tag field. Remove blank lines only keeps every real break and just compacts double-spaced text. De-hyphenate repairs words broken across lines before joining, which is the mode built for two-column academic PDFs. Flatten for one cell removes breaks and collapses whitespace so a multi-line address fits a single spreadsheet cell or form input.
Line endings: CRLF, LF, and CR
Three conventions are still in circulation. Windows terminates lines with \r\n, Unix, Linux, macOS and Git use a bare \n, and classic Mac OS used a bare \r. A file with the wrong one opens as a single unreadable line in some editors, and a file with a mixture produces Git diffs where every line appears to have changed. The tool detects the mix in your input, shows the breakdown as a composition bar, and Normalize line endings mode converts them all to one convention without touching your line structure.
Whitespace hygiene and re-wrapping
Joining lines exposes whitespace problems that were previously hidden at the end of each line. Trim each line strips leading and trailing whitespace before joining, so indented PDF text does not leave a double space at every seam. Collapse multiple spaces squashes any remaining runs into one. If your destination still needs a fixed width, set Max output line length and the joined text is greedily re-wrapped at that column — useful for producing a clean 80-column plain-text email from messy source material.
Advanced control
Power users get two extra levers. The custom separator field understands the escape sequences \n, \t, \r and \s, so you can join with a tab for spreadsheet paste or with a literal trailing space that would otherwise be invisible in an input box. The regex line filter restricts joining to lines matching a pattern — ^\s*\w joins only lines starting with a word character, leaving anything else on its own line.
Reading the statistics
Every pass reports lines, characters, words, and bytes before and after, plus breaks removed, blank lines removed, paragraphs preserved, and the longest resulting line. The byte figure is true UTF-8 size, so it shows the real saving from stripping carriage returns out of a large file. Characters are reported both as code units and as Unicode code points, which differ whenever emoji or CJK surrogate pairs are present. Results can be copied, downloaded as a .txt, exported as a CSV pairing each source line with its resulting block, or fed straight back into the input with the swap button.