Remove line breaks from text
Three lines reading Hello, world and from KIT become the single line Hello world from KIT, because each of the 2 breaks is replaced by a space. Leave the replacement empty to join lines with nothing in between. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Text
- Hello world from KIT
- Result
- Hello world from KIT
- Length
- 20
- Original length
- 21
- Line breaks removed
- 2
Removing line breaks is a daily hygiene step when you paste multi-line text into a single-line field, flatten a paragraph for a CSV cell, prepare a search query, or strip hard wraps from an email body before storing it. This tool takes the text you enter, finds every line break—including Windows CRLF, Unix LF, classic Mac CR, and Unicode line or paragraph separators—and replaces each break with a space by default so words do not glue together. You can pass an empty replacement to hard-join lines with no separator when you need a compact token. The result is always a single-line string plus clear metadata: original text, result, lengths, how many breaks were removed, the replacement used, and a changed flag.
How line-break removal works under the hood
Line-break removal is a short deterministic scan, not a full text layout engine. The default replacement is a single ASCII space so that Hello on one line and world on the next become Hello world rather than Helloworld. Second, the engine matches line terminators in a fixed order: the two-character Windows sequence carriage return plus line feed is treated as one break so a CRLF file does not inject a double space under the default replacement.
Remaining lone line feeds, carriage returns, Unicode next-line (NEL), line separator U+2028, and paragraph separator U+2029 are each replaced once. Soft hyphen characters and ordinary spaces inside a line are left alone; this tool does not reflow, justify, or collapse interior runs of spaces. Empty strings fail validation before any transform runs.
Because the path is pure parse work over strings, latency stays sub-millisecond for typical form sizes and the published cost model is analytic rather than model-token based.
Where remove-line-breaks tools show up in real work
Product and support teams paste multi-line ticket bodies into single-line title fields, search boxes, and chat inputs that reject or truncate on newlines. Data engineers cleaning CRM exports, spreadsheets, and legacy databases often force free-text columns into single-line forms before loading warehouses that treat newlines as record separators inside CSV. Content and localization teams flatten hard-wrapped paragraphs from email clients and rich editors before storing copy in CMS fields that display as one line.
Automation scripts that assemble prompts, log lines, or queue messages strip accidental wraps so downstream parsers see one logical string.
What you can do with it
Flatten pasted paragraphs for single-line fields
Turn multi-line ticket notes, email bodies, or chat pastes into one line before saving titles, search queries, or form fields that reject newlines.
Normalize CSV and free-text columns
Strip line breaks from export cells so warehouses and CSV parsers do not split records on embedded newlines.
FAQ
What line breaks does this tool remove?
Windows CRLF (treated as one break), Unix LF, classic Mac CR, Unicode NEL (U+0085), line separator U+2028, and paragraph separator U+2029.
What happens if text is empty?
Empty input is treated as a client error so callers that forgot to bind a field get a clear validation response instead of a silent empty result.
Can I join lines without inserting a space?
The default is a single space so ordinary paragraphs keep word boundaries.
Does it collapse multiple spaces inside a line?
No. Interior spaces and tabs are left unchanged. Only line-break characters are replaced. Trimming or space-collapsing is a different intent.
What does it cost?
The browser tool is free and runs locally.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/str/remove-line-breaks \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Hello\nworld\r\nfrom KIT"}'const res = await fetch("https://api.kit.forhosting.com/str/remove-line-breaks", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "Hello\nworld\r\nfrom KIT"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/str/remove-line-breaks",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "Hello\nworld\r\nfrom KIT"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/str/remove-line-breaks", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"Hello\\nworld\\r\\nfrom KIT"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"Hello\nworld\r\nfrom KIT"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/str/remove-line-breaks", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "Hello\nworld\r\nfrom KIT"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "str.remove_line_breaks",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Empty input is rejected with a clear validation error instead of silently returning an empty payload, which protects clients that forgot to bind a field. No network round-trips inside the engine, no random seeds, and no clock dependence—identical text always produces identical JSON.
How line-break removal works under the hood
First the capability reads the required text field and optional replace_with string. An empty replace_with is allowed when you intentionally want characters from adjacent lines to touch, for example when joining split codes or base64 fragments. Third, it counts how many break units were replaced, builds the single-line result, and sets a boolean changed flag so pipelines can detect no-ops without re-scanning the string. Extremely long payloads above the documented character cap also fail with invalid_input so a single request cannot monopolize Worker memory.
What you send and what you get back
Send a single required field named text containing the non-empty string whose line breaks you want to remove. Numbers and booleans for text are coerced to their decimal or true/false text forms; objects, arrays, NaN, and Infinity are rejected. Classic checks include Hello newline world becoming Hello space world, mixed CRLF and LF paragraphs flattening to one line with spaces, and hard-join mode turning A newline B into AB. Aliases such as input, value, data, s, message, string, content, and body are accepted for convenience when wiring older clients. Optional replace_with defaults to one space; pass an empty string to hard-join without a separator. On success the response echoes the original text, the single-line result, the result length, the original length, line_breaks_removed as the count of break units replaced, replace_with as the string actually used, a boolean changed flag, and operation set to remove_line_breaks. When the input already had no line breaks, result equals text, changed is false, and line_breaks_removed is zero—useful as a no-op detector in ETL guards. Wire the free browser form for quick paste-and-copy work, then call the identical contract from scripts when you normalize bulk CSV cells, chat messages, or API payloads. Pricing for successful API calls is the published base of $0.002 per item; validation failures including empty text do not consume prepaid balance.
Where remove-line-breaks tools show up in real work
Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance. If you later need to remove only duplicate lines, count words and paragraphs, convert case, strip accents, or minify JSON whitespace, treat those as separate search intents and landings rather than overloading this remove-line-breaks page.
Integration use cases
Hard-join split tokens and codes
Set replace_with to empty to reassemble codes or base64 fragments that were wrapped across lines without inserting spaces.