Remove first line from text
Paste a CSV and the header row name,age,city is dropped, leaving only the data rows Ada,36,London and Bob,41,Paris. The rest of the text, line endings included, stays untouched. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Text
- name,age,city Ada,36,London Bob,41,Paris
- Result
- Ada,36,London Bob,41,Paris
- First line
- name,age,city
- First line length
- 13
- Result length
- 26
Pasted data almost always arrives with one line too many at the top: a CSV header, a table title, a report label, or a column-name row that your next tool does not want. Manually deleting that line in an editor is slow, error-prone, and hard to automate when the same pattern repeats in scripts and pipelines. This capability takes the text you provide, identifies the first line using real-world line endings (Windows CRLF, Unix LF, and classic Mac CR), removes only that leading line, and returns everything after the first break unchanged. Single-line input is accepted and yields an empty remainder, which makes it safe to chain when a source sometimes ships without a body.
How first-line removal works under the hood
First-line removal is a short deterministic scan, not a full document editor or spreadsheet importer. If that pair is absent, a lone line feed or a lone carriage return is used instead. When the input has no break at all, the whole string is treated as the first line and the result is the empty string—this is intentional success, not an error, because dropping a title-only paste should leave nothing rather than fail.
Soft spaces, tabs, and blank content on the first line are not special-cased: a blank first line still counts as the line to drop, which is the correct behavior when someone pastes a leading empty row above data. 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-first-line tools show up in real work
Analysts paste spreadsheet selections into chat tools and tickets and want the header dropped so colleagues see only the values. Support and ops teams strip a human-readable title line from incident pastes before attaching the body to an automated classifier. Content teams remove a markdown H1 or a pasted document title before storing the body in a CMS field that has its own title property.
Automation scripts that assemble queues, prompts, or multi-step transforms drop the first line when a previous stage always emits a status banner. If you later need to reverse line order, remove duplicate lines, join all breaks into one line, count lines, or trim each line, treat those as separate search intents and landings rather than overloading this remove-first-line page.
What you can do with it
Strip CSV and TSV header rows
Drop the column-name line from pasted exports so loaders and scripts receive pure data rows without re-opening a spreadsheet.
Remove titles from pasted reports
Cut a leading title or label line from logs, tickets, and document pastes before storing or classifying the body.
Normalize multi-stage ETL inputs
Guarantee every batch loses exactly one leading line in pipelines where upstream stages always emit a banner or header.
FAQ
What counts as the first line?
Everything from the start of the text up to—but not including—the first line break. The first break may be Windows CRLF (one unit), Unix LF, or classic Mac CR. Everything after that break is returned in result.
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.
Are line endings in the remainder changed?
No. Only the first break is used as the cut point. The remainder is returned as a substring, so CRLF or LF sequences after the first line stay as they were.
What does it cost?
The browser tool is free and runs locally.
How do I delete the header row from pasted CSV data?
Paste the data and the first line, where the column names usually sit, is removed while the rows below come back unchanged. Even a file exported from Excel does not leave a stray hidden character on the first data row.
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-first-line \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"name,age,city\nAda,36,London\nBob,41,Paris"}'const res = await fetch("https://api.kit.forhosting.com/str/remove-first-line", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "name,age,city\nAda,36,London\nBob,41,Paris"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/str/remove-first-line",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "name,age,city\nAda,36,London\nBob,41,Paris"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/str/remove-first-line", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"name,age,city\\nAda,36,London\\nBob,41,Paris"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"name,age,city\nAda,36,London\nBob,41,Paris"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/str/remove-first-line", 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": "name,age,city\nAda,36,London\nBob,41,Paris"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "str.remove_first_line",
"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 strings are rejected with a clear invalid_input error so missing fields fail loudly instead of inventing success. No network calls inside the engine, no random seeds, and no clock dependence—identical text always produces identical JSON at $0.002 per successful API item.
How first-line removal works under the hood
The engine reads the required non-empty text field, optionally resolved through common aliases such as input, value, data, content, or body when older clients use those names. It then searches for the first line-break sequence in a fixed priority: the two-character Windows CRLF pair is treated as a single break so a CSV exported from Excel does not leave a stray carriage return on the first data row. Everything before that first break becomes first_line; everything after it becomes result, with original line endings in the remainder preserved exactly so downstream tools that care about CRLF versus LF keep their expected shape. Extremely long payloads above the documented character cap 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 first line you want to remove. Mixed endings after the first break are left intact: only the first break is consumed as the cut point; the rest of the blob is a faithful substring. Numbers and booleans for text are coerced to their decimal or true/false forms; objects, arrays, NaN, and Infinity are rejected. On success the response echoes the original text, the remainder in result, the dropped first_line string, first_line_length and result_length for quick asserts, original_length, original_line_count and remaining_line_count so pipelines can verify how many logical lines survived, break_kind as lf, crlf, cr, or null when there was no break, a boolean changed flag, and operation set to remove_first_line. Classic checks include a three-line CSV header plus two data rows returning only the two data rows, a title line above a paragraph becoming the paragraph alone, and a single-line string becoming an empty result with remaining_line_count zero. Empty text fails validation before any transform runs so clients that forgot to bind a field get a clear error instead of a silent empty payload. Wire the free browser form for quick paste-and-copy work, then call the identical contract from scripts when you strip headers from bulk exports, log dumps, or API responses. 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-first-line tools show up in real work
Data engineers cleaning CSV and TSV exports often need the column-name row gone before loading a warehouse stage that already has a schema, or before feeding a parser that expects pure data rows. 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.
Technical questions
What if my text has only one line?
That whole string is treated as first_line and result is the empty string. This is a successful response, not an error, so single-line pastes do not fail your pipeline.