Remove Newlines Tool

Remove newlines is the process of handling or deleting line break characters in text. Line breaks are special characters that control text display formatting. Different systems use different line break standards: Windows uses CRLF (\r\n), Unix/Linux uses LF (\n), and early Mac used CR (\r). This tool supports processing all common line break formats, providing four processing modes: remove all newlines, newlines to spaces, remove empty lines, and merge empty lines to meet various text organization needs. When removing newlines, it matters whether paragraphs should be joined with spaces or collapsed directly. CSV snippets, logs, copied articles, prompts, code fragments, and form text may each need different handling. Removing line breaks blindly can merge words, destroy list structure, change meaning, or make structured data harder to read. Before sending important text onward, compare the result with the original and decide whether empty lines, indentation, and paragraph boundaries should be preserved.

Each mode is one call to String.prototype.replace with a global regular expression. Remove-all uses /[\r\n]+/g and replaces with the empty string; newlines-to-spaces uses /[\r\n]+/g and replaces with a single ' '; merge-empty uses /(\r?\n){2,}/g and replaces with '\n\n' to collapse three or more line breaks into one blank line; remove-empty splits on /\r?\n/, filters out trimmed-empty entries, and rejoins on '\n'. The character-class form [\r\n] is deliberate because the three classic line endings — CRLF (\r\n, Windows since DOS), LF (\n, Unix and modern macOS), and lone CR (\r, classic Mac OS up to System 9) — must all be absorbed even when they appear mixed in the same file (a common artefact of copy-pasting between platforms or editing a Unix file in Notepad). Two additional Unicode break points exist but are rare in practice: U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR, defined by the Unicode UAX #14 line-breaking algorithm and recognised by JavaScript string literals since ES2019. The tool currently treats them as ordinary characters, which matches what most users expect when they paste from a chat app. The BOM (U+FEFF) at the start of a UTF-8 file is also passed through unchanged — strip it separately if the downstream parser is strict. Real-time updating is driven by a React useState/useMemo pair: a controlled textarea writes input, the memo recomputes the result on every keystroke, and React's reconciliation only repaints the output panel. Because regex replacement on strings up to a few hundred KB completes in under a millisecond on a modern V8, no debouncing is needed; for multi-megabyte inputs the cost is still well under the 16 ms frame budget at 60 Hz.

• Remove-all: text.replace(/[\r\n]+/g, '') — collapses runs of line breaks into nothing, fine for JSON string literals and .env values
• Newlines-to-spaces: text.replace(/[\r\n]+/g, ' ') — preserves word boundaries from wrapped paragraphs without doubling spaces
• Merge-empty: text.replace(/(\r?\n){2,}/g, '\n\n') — squashes runs of blank lines down to a single blank, preserving paragraph rhythm
• Remove-empty: split(/\r?\n/).filter(l => l.trim() !== '').join('\n') — keeps content lines and normalises endings to LF in one pass
• Line-ending zoo: CRLF (Windows \r\n, originally typewriter carriage-return + line-feed), LF (Unix \n since the 1970s), CR (classic Mac up to System 9) — the [\r\n] character class catches all three; Unicode U+2028 and U+2029 from UAX #14 are recognised by ES2019 string literals but rare in user input
• BOM (U+FEFF) at file start is left untouched — strip it with text.replace(/^\uFEFF/, '') if the next stage is a strict JSON or CSV parser
• Git's core.autocrlf=true normalises CRLF↔LF on checkout — use this tool when the file already arrived on your machine with the wrong endings and Git did not catch it