Wrap each line with text
Paste alpha, beta and gamma on three lines and get "alpha", "beta" and "gamma", each wrapped in straight double quotes by default. Swap in backticks, HTML tags, bullets or brackets, up to 64 characters per side. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Text
- alpha beta gamma
- Input
- alpha beta gamma
- Text
- "alpha" "beta" "gamma"
- Prefix
- "
- Suffix
- "
Wrapping every line of a paste with the same prefix and suffix is everyday work for people who quote logs, tag list items, build delimited rows, or turn a column of words into quoted values. This tool takes any non-empty block of text, splits it on normalized newlines, and puts your chosen prefix before each line and your chosen suffix after it. Defaults wrap every line in straight double quotes so a list becomes a quoted list without extra setup. You can switch to backticks, HTML tags, markdown bullets, parentheses, or any short strings you need.
What wrapping each line means and when it helps
Most editors can wrap a whole selection in one pair of quotes, but that leaves interior line breaks untouched and does not put a prefix and suffix on every row. The search intent behind wrap each line with text is different: you already have one item per line and you want the same decoration on each item.
After the input is checked, newlines are normalized from Windows CRLF and classic Mac CR into a single LF form, the string is split on every LF, and each resulting segment is concatenated as prefix plus original line plus suffix. You can instead send a markdown bullet as the prefix and an empty suffix, or opening and closing HTML tags, or a left parenthesis and a closing comma for a value list. Interior characters of a line never change; only the edges receive the affixes.
Blank lines still exist after the split. By default they become prefix plus suffix, which is correct when you want every visual row decorated. The design matches everyday chores such as quoting a column, wrapping log lines for a ticket, or turning a checklist into tagged markup, without opening a full IDE search-and-replace.
Practical tips, limits, and related searches
Use this capability when the search intent is wrap each line with text, add prefix and suffix to every line, quote each line online, or wrap lines with HTML tags. Paste a column of names and keep the default quotes to produce a quoted list. Set prefix to a greater-than sign and a space with an empty suffix to turn notes into a markdown block quote.
Set prefix to an opening list-item tag and suffix to the matching close tag to build markup rows. Extremely long single lines still count as one line each; the tool does not wrap by character width. HTML and Markdown source are treated as raw strings; strip tags first if you only want visible prose lines.
This landing is not a full-document wrap that only touches the first and last characters of the whole paste, not a line numberer, not a per-line trimmer, and not an AI rewriter. Prefer adding line numbers when reviewers must cite indices; prefer trimming line edges when you only need whitespace gone; prefer this capability when humans already separated items by line and you need the same decoration on each one.
When teaching students or onboarding reviewers, show the same sample with quotes, then with tags, so they see that only the edges change and that the original line body is left alone.
What you can do with it
Decorate log excerpts for tickets
Wrap each log line with a chosen marker or code fence fragment so a support paste stays line-aligned and easy to cite in a bug report.
FAQ
What does wrapping each line do?
Each line becomes prefix plus the original line plus suffix. Interior characters never change. Defaults put a straight double quote on both sides of every line.
Can I add only a prefix or only a suffix?
Yes. Pass an empty string for the side you do not want.
How are empty lines handled?
By default an empty line becomes prefix plus suffix.
What happens if the text field is blank?
Provide a non-empty string that has at least one non-whitespace character.
Is the wrap-each-line tool free?
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/wrap-each-line \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"alpha\nbeta\ngamma"}'const res = await fetch("https://api.kit.forhosting.com/str/wrap-each-line", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "alpha\nbeta\ngamma"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/str/wrap-each-line",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "alpha\nbeta\ngamma"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/str/wrap-each-line", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"alpha\\nbeta\\ngamma"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"alpha\nbeta\ngamma"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/str/wrap-each-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": "alpha\nbeta\ngamma"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "str.wrap_each_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.
Limits
max_chars | 100000 |
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 or whitespace-only input is rejected with a clear invalid_input error so a blank form never looks like a successful wrap.
What wrapping each line means and when it helps
Defaults use a straight double quote on both sides so three names become three quoted names, ready to paste into JSON, CSV, or a config file. When skip_empty is true, a zero-length line stays an empty line so paragraph gaps survive while content lines are wrapped. Empty or whitespace-only whole input is a hard error: there is no meaningful wrapped document to return, and callers should treat that as invalid_input rather than a zero-line success.
How to call the API and what the response contains
When prefix or suffix is omitted, each defaults to a straight double quote. When you pass an explicit empty string for one side, that side stays empty so you can prefix only or suffix only. Prefer sending the raw multi-line body rather than pre-joining everything when you want true per-line semantics. Send a JSON body with a required string field text (aliases input, value, string, s, content, and body). Optionally include prefix (aliases pre and left) and suffix (aliases post and right) as strings of at most sixty-four characters each, and skip_empty (aliases skip_blank, ignore_empty, and skip_blanks) as a boolean. If both sides resolve to empty strings the call is rejected, because wrapping with nothing is not a wrap. The text value must be non-empty after overall whitespace is trimmed and must not exceed one hundred thousand characters so a single request cannot exhaust Worker or browser memory on huge paste dumps. On success the response echoes input as the original string you sent, text as the fully wrapped result joined with LF, prefix and suffix as the effective affixes, skip_empty as the effective flag, line_count as the number of segments after the split, wrapped_count as how many of those segments actually received the affixes, lines as an ordered array of the wrapped strings, and message as a short English summary. Failed validation—missing text, a non-string value, an oversize payload, empty content after overall trim, a non-string or oversize affix, both affixes empty, or a non-boolean skip_empty—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item. When integrating, assert on text or lines for the wrapped content, on wrapped_count when skip_empty is in play, and treat invalid_input as a client bug for blank form submissions rather than a billing event.
Practical tips, limits, and related searches
Round-trip checks for tests are easy: feed three short lines and expect three quoted lines with line_count three and wrapped_count three; feed a blank line between two words with skip_empty true and expect the middle line to stay empty; deliberately send empty string or only spaces to confirm invalid_input and the message that asks for a non-empty string; send empty prefix and empty suffix together to confirm the both-empty rejection. Keep intentional trailing newlines in mind: a final LF creates an empty last segment that is wrapped unless skip_empty is true. Failed tasks that return invalid_input do not consume prepaid balance, which keeps form validation and CI negative tests cheap.
Integration use cases
Quote a column for JSON, CSV, or SQL
Paste one value per line and wrap each row in quotes so the list is ready for a config file, spreadsheet import, or IN-list without hand-editing every row.
Tag lines as HTML or markdown
Turn a checklist into list-item tags, or prefix notes with a block-quote marker, while leaving blank separators empty when skip_empty is on.