Remove Line Breaks
Strip line breaks or clean up extra blank lines.
Your cleaned text will appear here.
This strips line breaks from text or collapses only the extra blank lines, with a live preview, entirely in your browser. It exists because copying text out of a PDF, an email or a terminal frequently brings hard line breaks with it — breaks that were part of how the text was displayed rather than part of the text itself — and those breaks make the content unusable when pasted anywhere that reflows. Two modes cover the real cases. Remove-all joins everything into one continuous block, which is what you want after un-wrapping a PDF column. Extra-only keeps single breaks and collapses runs of blank lines, preserving paragraph structure. Windows CRLF and Unix LF endings are normalised identically, so text pasted from any platform behaves the same. The optional trim strips stray leading and trailing spaces per line, which matters because quoted email text often carries invisible indentation that survives the break removal.
About the Remove Line Breaks
Clean up text that's been broken into awkward lines by emails, PDFs, or copy-paste. Strip every line break, or just collapse extra blank lines while keeping paragraphs intact — all in your browser, with a live preview.
How to use the Remove Line Breaks
- 01Paste your text into the input box.
- 02Pick a mode: remove all line breaks, or only extra/empty lines.
- 03Optionally turn on "Trim each line" to strip stray whitespace.
- 04Click "Copy" to send the cleaned text to your clipboard.
Why use our Remove Line Breaks
- 01
Two cleanup modes
Remove every line break, or only collapse repeated blank lines into single breaks.
- 02
Live preview
See the cleaned text update instantly as you toggle options.
- 03
Trim whitespace
Optionally strip leading and trailing spaces on each line for tidy output.
- 04
Private & free
All processing happens in your browser — your text is never uploaded.
Why pasted text arrives broken
The problem originates in the difference between a line break that means something and one that is an artefact of layout. In a PDF, text is positioned glyph by glyph and there is no concept of a flowing paragraph, so when you select and copy, the extractor inserts a break at the end of every visual line. Plain-text emails have historically been hard-wrapped at 72 or 78 characters, a convention dating to terminal widths, so every line ends with a real newline character. Terminal output, code comments and text pasted between systems with different conventions all produce the same result: text that looked like paragraphs on screen arrives as dozens of short lines. Pasting that into a word processor or a web form produces a ragged column that will not reflow, because the breaks are now genuinely in the content. Removing them restores the text to a flowing paragraph that wraps naturally to whatever width it is placed in.
Remove all versus collapse extra
The two modes solve opposite halves of the problem and choosing wrongly destroys structure. Remove all joins everything into a single continuous block, which is correct when the text is one paragraph that was hard-wrapped — a quotation pulled from a PDF, an abstract copied from a paper, a paragraph of an email. It is wrong when the text contains multiple paragraphs, because it will run them together with no separation. Collapse extra keeps single line breaks and reduces runs of blank lines to one, which is correct when the structure is right but the spacing is excessive — text that arrived double-spaced, or a list where every item is separated by two empty lines. The reliable approach when you are unsure is to try collapse extra first, look at the preview, and escalate to remove all only if the result is still wrong. The live preview exists precisely so this is a two-second decision rather than a guess.
Line endings, whitespace and the invisible differences
There are three conventions for marking the end of a line and they are not interchangeable. Windows uses a carriage return followed by a line feed, written CRLF or \r\n. Unix, Linux and modern macOS use a bare line feed, LF or \n. Classic Mac OS before version 10 used a bare carriage return. Text moved between systems can end up with a mixture, which is what causes the familiar symptoms of a file displaying as one long line in one editor and correctly in another, or showing stray ^M characters. This tool normalises all three before processing, so mixed line endings are handled without you needing to know which you have. The related nuisance is trailing whitespace: PDF extraction in particular tends to leave spaces at the end of each line, which survive the join and produce doubled spaces mid-sentence. Turning on the trim option removes leading and trailing whitespace per line before joining, which is almost always what you want when cleaning pasted text.
Which mode to use
| Your text | Mode | Result |
|---|---|---|
| One paragraph, hard-wrapped from a PDF | Remove all | A single flowing paragraph |
| Several paragraphs, double-spaced | Extra only | Paragraphs kept, spacing normalised |
| A list with blank lines between items | Extra only | List structure preserved |
| An email quote broken at 72 characters | Remove all | Continuous text that reflows |
| Unsure | Extra only first | Check the preview, escalate if needed |
Trailing spaces from PDF extraction cause doubled spaces after joining — enable trim to remove them.
Frequently asked questions
What is the difference between remove all and extra only?
Remove all joins everything into one continuous block. Extra only keeps single line breaks and collapses runs of blank lines, which preserves paragraph structure.
Will this break my paragraphs?
In extra only mode, no — paragraphs are preserved. In remove all mode every break goes, which is what you want for a single hard-wrapped paragraph and wrong for multi-paragraph text.
Why does text copied from a PDF break like this?
PDFs position text visually rather than as flowing paragraphs, so extraction inserts a break at the end of every displayed line. Those breaks were never part of the content.
Does it handle Windows and Mac line endings?
Yes. Windows CRLF, Unix LF and classic Mac CR are all normalised before processing, so mixed line endings are handled without you needing to identify them.
Why do I get double spaces after joining?
PDF extraction often leaves a trailing space on each line, which survives the join. Enable the trim option to strip leading and trailing whitespace per line first.
Can I undo it if I pick the wrong mode?
The original text stays in the input box and the preview updates live, so switching modes shows the alternative immediately without losing anything.
Why are emails wrapped at 72 characters?
A convention inherited from terminal widths and codified in early email standards. The breaks are real newline characters in the message body, not display wrapping.
Is there a length limit?
No. Processing happens locally, so the practical limit is your device's memory and long documents handle fine.
Is my text uploaded?
No. Everything runs in your browser and nothing is sent to a server or stored.
Last updated
Line-ending conventions per the Unicode Standard Annex 14 and historical platform practice. Email line-length convention follows RFC 5322.