Does Google Docs Find and Replace support \n for line breaks?

Yes. Open Edit, Find and Replace, click the three-dot menu, and enable Match using regular expressions. The pattern \n in the Find field matches line breaks, and the Replace field can be left empty or set to a single space.

Will the tool change any spaces in my document?

No. Spaces, repeated spaces, tabs, non-breaking spaces, and leading or trailing non-newline whitespace are preserved exactly. Only the five recognized line-break tokens are transformed.

How does Preserve paragraphs work?

One line-break token becomes one space. An uninterrupted run of two or more tokens becomes exactly two LF characters. Any non-newline character between breaks keeps them in separate single-token runs.

Does CRLF count as one or two line breaks?

It counts as one combined token. Standalone CR, LF, U+2028, and U+2029 each also count as one token, so the detected and removed counters always use the same unit.

Is my document uploaded or stored?

No. Transformation, statistics, and clipboard preparation happen locally in the current browser tab. Nothing is sent to a server.

How to Remove Line Breaks in Google Docs

Line breaks in Google Docs can be removed in three reliable ways: enable regular expressions in Find and Replace and search for \n to delete or replace every break at once, paste the text unformatted into a clean document and fix it by hand, or copy the text into Line Break Remover, process it with one of three explicit modes, and paste the result back. The native Find and Replace path is the fastest option when the document is already open, while an external browser tool gives you finer control over how paragraph boundaries are handled and surfaces an exact count of removed versus retained tokens. Whichever path you take, the actual characters you are working with are CR, LF, CRLF, U+2028, and U+2029 — the same five line-break tokens that the JavaScript specification and the Unicode Line Breaking Algorithm recognize. Google Docs does not visibly distinguish between them in the editor, which is why a counted, mode-driven transformation is usually more reliable than scrolling and pressing Backspace.

The Line Break Tokens Hidden in Google Docs Text

Most pasted prose carries line breaks from a previous home. A PDF export hard-wraps every seventy columns, a spreadsheet export slaps CRLF after every record, an older Mac file still uses standalone CR, and document systems occasionally emit U+2028 LINE SEPARATOR or U+2029 PARAGRAPH SEPARATOR because Unicode counts them as breaks too. Google Docs will render any of them as a new line in the body, so visually they look identical. That visual sameness is exactly why a manual cleanup often misses the unusual ones.

The five recognized tokens in Line Break Remover map to the official specifications. According to the MDN JavaScript lexical grammar and the ECMAScript Language Specification, JavaScript line terminators are exactly LF, CR, LS (U+2028), and PS (U+2029), while CRLF is treated as a single combined token. Handling all five avoids leaving hidden separators behind simply because a text area displays them in the same way.

Three Google Docs Methods Worth Knowing

Before reaching for an external tool, try the built-ins. They cover most everyday cases without leaving the document.

Find and Replace with regular expressions. Open Edit, choose Find and Replace, click the three-dot menu inside the dialog, and enable Match using regular expressions. In the Find field type \n. Leave the Replace field empty to delete every break, or type a single space to reflow wrapped lines into continuous prose. Click Replace all. CRLF and standalone CR are also matched because the regex engine normalizes them, so the count is reliable.
Paste unformatted text. Copy the source text from its origin, click into the Google Docs document, and press Ctrl+Shift+V on Windows or Chrome OS, or Command+Shift+V on macOS. Choose Paste unformatted text. The pasted block carries ordinary paragraph breaks only, which you can then join with Find and Replace as above.
Manual backspace with formatting marks visible. Open View and enable Show non-printing characters so paragraph marks (¶) and section breaks become visible as light glyphs. Place the cursor at the start of the unwanted break and press Backspace, or at the end and press Delete. This is fine for a handful of breaks but error-prone across hundreds of paragraphs.

When the document is large, the source already mixes several break types, or the result has to be reviewed paragraph by paragraph, the manual path becomes impractical. That is the case where a counted, mode-driven transformation pays off.

Clean the Text with Line Break Remover

The fastest way to clean a large block is to copy the text out of Docs, run it through Line Break Remover, and paste the result back. Every step happens inside the current browser tab, so nothing is uploaded.

Paste text and choose one-space replacement, complete removal, or paragraph preservation. Select the text in Google Docs, copy it, and paste it into the input area on the Line Break Remover page. Then pick the mode that matches the result you want. Replace with one space turns every break into a single ordinary space. Remove completely erases every break with no replacement. Preserve paragraphs keeps paragraph boundaries while joining single wrapped lines.
Process the text and review the removed, detected, and remaining line-break token counts. Run the tool and inspect the three counters. Detected is the total number of recognized line-break tokens in the input. Removed is how many were replaced. Remaining is how many line-break tokens still appear in the output. The relationship detected = removed + remaining is always enforced, and CRLF contributes one token rather than two.
Copy the output, or select it manually if browser clipboard permission is unavailable. Use the copy button for a one-click transfer, or highlight the output with the mouse and copy it with the platform shortcut if the browser blocks programmatic clipboard access. Paste the cleaned text back into Google Docs with Ctrl+Shift+V to keep it unformatted.

The input budget is 1,000,000 UTF-16 code units, so inputs up to that size are processed in one shot. Text at the exact boundary is accepted; one code unit beyond it is rejected before any transformation runs. Editing the input or switching mode clears the previous result immediately, so stale statistics never leak into a new decision.

Choosing Between the Three Output Modes

Each mode maps the same five tokens through a different rule, so the right pick depends on what the breaks mean in the source.

Mode	Rule per recognized token	Best used when	Risk to watch
Replace with one space	Every CRLF, CR, LF, U+2028, or U+2029 becomes one U+0020.	The breaks are visual line wraps in continuous prose, the most common case.	Two consecutive breaks produce two spaces, not one, because the tool does not collapse the result.
Remove completely	Every recognized token is replaced with an empty string.	You are cleaning record separators, CSV exports, or other structured text where words are already space-separated.	Words split across a hard wrap will be joined directly, which corrupts natural prose.
Preserve paragraphs	A one-token run becomes one space. Any uninterrupted run of two or more tokens becomes exactly two LF characters.	The source uses blank lines to separate paragraphs and the wrapped lines inside each paragraph should be joined.	A single U+2029 alone is treated as one break, not as a paragraph, so place two breaks where a paragraph must remain.

Only actual line-break tokens participate in a run. If a space, tab, or non-breaking space sits between two breaks, those breaks belong to separate single-token runs and each becomes one space. Spaces, tabs, and non-breaking spaces are never collapsed or trimmed, so the output carries the exact horizontal whitespace the input had.

Paste the Result Back Without Reintroducing Breaks

The clipboard can carry invisible line breaks along with the visible characters, which is why the final paste matters. In Google Docs, click into the destination paragraph and press Ctrl+Shift+V on Windows or Chrome OS, or Command+Shift+V on macOS, then choose Paste unformatted text. The pasted block drops down with ordinary paragraph spacing only, so the cleaned output is what survives. For larger documents, paste into a temporary blank document first, scan it once with View, Show non-printing characters, and copy it into the final location only when the marks look right.

When to Reach for a Different Tool

Line Break Remover is a string-level transform. It does not parse Markdown, HTML, CSV quoting, source-code syntax, postal addresses, or semantic document structure, so a break that carries business meaning will be removed the same way as a visual wrap. If the goal is to clean horizontal spacing rather than line breaks, Whitespace Remover collapses or strips spaces and tabs while leaving breaks alone. If the goal is to convert visible breaks into literal characters such as \n, the related Line Break Converter does the opposite mapping. Pairing the right tool with a quick visual review of formatting marks keeps the cleanup honest without losing the structure that mattered.