How does it know which breaks to remove?

A blank line is treated as a real paragraph boundary and kept; every other break is treated as wrapping and removed. That matches how hard-wrapped text is produced, which is why it works on most sources.

My paragraphs all ran together.

The source had no blank lines between them, which is common in text extracted from a PDF. There is no signal to work from in that case, so the paragraph breaks have to go back in by hand.

What happens to hyphenated words split across lines?

The hyphen is removed and the two halves are rejoined, which is what you want from PDF text. A genuinely hyphenated word at the end of a line is the rare case where that guesses wrong.

What is the difference between CRLF and LF?

Windows ends a line with a carriage return and a line feed; Unix and macOS use the line feed alone. Mixing them makes diffs show every line as changed, and is why Git offers to normalise them on checkout.

Remove Line Breaks

Unwrap hard-wrapped text without losing paragraphs.

Everything runs inside your browser. Your files never leave your device.

Input

Result

The result appears here as you type.

Ask about Remove Line Breaks

Questions about what this tool does, which option to pick, or what it can and cannot handle.

The question you type here is sent to an AI provider to be answered — your files and whatever you put in the tool above are not, and the assistant cannot see them. Answers are generated and can be wrong. The tool itself is not guessing: it runs deterministic code on your device.

About the Remove Line Breaks

Text copied out of a PDF, an email client or a terminal often arrives with a line break every seventy or eighty characters — wrapped for a column that no longer exists. Pasting it anywhere else produces a ragged block that reflows badly and reads worse.

This joins those lines back into continuous paragraphs. The difficulty is knowing which breaks were the original formatting and which were meant, and the tool handles that by treating a blank line as a genuine paragraph boundary and everything else as a wrap to be removed.

That rule is right most of the time because it matches how the text was produced. A hard-wrapped document separates paragraphs with an empty line and wraps within them, so keeping the empty lines and joining the rest reconstructs the original. Text extracted from a PDF is the main exception, since PDFs frequently have no blank lines at all, and there the result needs a read.

Joining is done with a space rather than nothing, because two lines pushed together without one produce merged words. Where a word was hyphenated across a break the hyphen is removed and the halves rejoined, which is the behaviour you want from PDF text and the thing that makes the difference between readable output and a page full of "some- thing".

The other direction is available too: converting Windows line endings to Unix ones and back. That matters when a file crosses between systems, and it is the invisible cause of a great many diffs that show every line as changed when nothing in them actually was.

How to use it

1Paste the text with unwanted breaks in it.
2Choose whether blank lines should be kept as paragraph boundaries — usually yes.
3Read the result. Text from a PDF may need a check, since PDFs often lack the blank lines that mark paragraphs.
4Use the line-ending conversion instead when a file is moving between Windows and Unix systems.

Questions

How does it know which breaks to remove?: A blank line is treated as a real paragraph boundary and kept; every other break is treated as wrapping and removed. That matches how hard-wrapped text is produced, which is why it works on most sources.
My paragraphs all ran together.: The source had no blank lines between them, which is common in text extracted from a PDF. There is no signal to work from in that case, so the paragraph breaks have to go back in by hand.
What happens to hyphenated words split across lines?: The hyphen is removed and the two halves are rejoined, which is what you want from PDF text. A genuinely hyphenated word at the end of a line is the rare case where that guesses wrong.
What is the difference between CRLF and LF?: Windows ends a line with a carriage return and a line feed; Unix and macOS use the line feed alone. Mixing them makes diffs show every line as changed, and is why Git offers to normalise them on checkout.