How to use it
- Paste your text into the input panel.
- Choose what to join lines with: a space, nothing at all, or a comma.
- Leave Keep paragraphs on if blank lines in your text mark real paragraph boundaries.
The problem this actually solves
Text copied out of a PDF, an email client, or a terminal arrives with a line break at the end of every visual line. Those breaks were never part of the content — they were the renderer's decision about where the column ended. Paste that text somewhere with a different width and it looks broken:
Base64 is an encoding,
not encryption. Anyone can
decode it without a key.
You want one flowing paragraph. But a naive find-and-replace of every newline destroys the structure that does matter: the blank lines between paragraphs. That is what Keep paragraphs exists for. It splits the text on blank lines first, joins within each block, and puts the paragraph breaks back.
Line endings, briefly
Three conventions are still in circulation. Unix and macOS use a single LF (\n). Windows uses CRLF (\r\n). Classic Mac OS, up to version 9, used a lone CR (\r).
This matters because a tool that only looks for \n will leave a stray \r at the end of every line when fed Windows text. The result looks correct in most editors and then breaks something downstream — a string comparison that fails for no visible reason, a CSV column with an invisible character, a shell script that reports command not found on a command that is plainly there. This tool normalises all three to LF before doing anything else.
Turning a column into a list
A specific use worth knowing: copy a column of IDs from a spreadsheet, paste it here, choose Comma as the joiner, and you get 1001, 1002, 1003 ready for a SQL IN clause or a config array. It takes a second and avoids the usual manual editing.
The same trick works in reverse for reading: take a long comma-separated line, and any tool that splits on the delimiter gives you back one item per line.
What this tool deliberately does not touch
Non-breaking spaces and zero-width characters survive. They are a frequent source of confusion — a copied non-breaking space looks exactly like a space but fails an equality check — but they are not line breaks. Removing them here would be a silent, unrequested change to your text, and silent changes are worse than a second pass through a dedicated whitespace tool.