Translate keeping the tone
A slogan translated word-for-word usually survives the meaning and loses the reason anyone wrote it in the first place — the punch, the rhythm, the wink. This endpoint reads the tone already present in your source copy and carries that same energy into the target language, instead of flattening everything into neutral, correct, forgettable sentences.
Run it online
Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.
Why marketing copy breaks in ordinary translation
A tagline built around a pun, an exclamation that's meant to feel like a friend talking, or a product description written with deliberate swagger all depend on more than their literal meaning — they depend on a register the writer chose on purpose. Run that through a translator built to preserve meaning above all else, and the words survive while the voice doesn't: the pun disappears, the exclamation reads as generic enthusiasm, the swagger flattens into a plain product spec. Marketing teams, brand copywriters and anyone localizing an ad campaign have felt this exact loss — the translation is 'correct' and somehow says nothing.
What tone-preserving translation actually targets
POST /translate/tone-preserve with the source text and target language, no separate tone parameter required — the endpoint reads the register your copy is already written in, whether that's playful, urgent, warm, irreverent or confident, and carries that same feel into the translation rather than defaulting to a neutral tone. A task_id comes back immediately, the job runs in the background, and the result arrives by webhook or a signed link valid for 24 hours, same as every other translation endpoint.
Tone as a real, separate translation problem
Professional literary and advertising translation has always treated tone as its own discipline distinct from literal accuracy — a translator handling a novel or an ad campaign is trained to ask what effect a line produces on the reader, not just what it denotes, because a technically accurate rendering that lands as flat or awkward has failed at the actual job. That distinction between meaning and effect is exactly what separates a tone-aware translation approach from a general-purpose one: it optimizes for the reaction the copy is supposed to produce, not only for dictionary correctness.
Where it earns its keep in a real campaign
A global product launch that ships the same landing page copy, ad headlines and email subject lines into a dozen markets needs every version to hit with the same energy, not just say the same thing — a joke that lands in English and reads as confused in another language undermines the whole campaign, no matter how accurate the translation technically is. At $0.003 per request plus $0.0135 per 1000 words, running an entire campaign's copy through tone-preserving translation costs little enough to do for every market launch, not just the flagship one, so smaller regional campaigns get the same care as the headline market instead of a rushed literal pass.
What you can do with it
Ad campaign headlines
A brand translates its ad headlines and taglines to a new market while keeping the same playful energy that made the original campaign work.
Email marketing subject lines
An e-commerce company translates urgent, high-energy sale subject lines so they still create the same sense of urgency in each target language.
Product landing pages
A startup translates a confident, casual landing page voice into new markets without it turning stiff or overly formal in translation.
Social media captions
A consumer brand translates witty social captions while preserving the humor, so jokes still land instead of falling flat in another language.
FAQ
How does tone-preserving translation work in the API?
POST your text and target language to /translate/tone-preserve; the endpoint detects the tone already in your source copy and carries it into the translation, delivered by webhook or a signed link valid for 24 hours.
Is the tone-preserving translation API free?
No, there is no free tier or trial; it costs $0.003 per request plus $0.0135 per 1000 words, and a failed job is never charged.
Do I need to specify the tone manually?
No, the endpoint reads the tone already present in your source text automatically rather than requiring a separate tone parameter.
How is this different from formality-controlled translation?
Tone-preserving translation carries over whatever register your source copy already has; formality control instead lets you explicitly choose formal or informal regardless of the source tone.
Will it preserve jokes and wordplay exactly?
It aims to keep the same energy and effect on the reader, but wordplay and puns are inherently language-specific, so an equivalent joke rather than a literal one is often the honest outcome.
Can I use this for long-form marketing copy, not just headlines?
Yes, it works on any length of marketing text, from a short tagline to a full landing page, and price scales with word count.
Can I run tone-preserving translation across a whole campaign in bulk?
Yes, submit one asynchronous task per piece of copy and collect each result by webhook as it finishes, which suits multi-market campaign launches.
Is my marketing copy stored after translation?
No, submitted text is deleted after the retention window and is never used for training.
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, and soon from our app, email and Telegram.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/translate/tone-preserve \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"…"}'const res = await fetch("https://api.kit.forhosting.com/translate/tone-preserve", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "…"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/translate/tone-preserve",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "…"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/translate/tone-preserve", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"…"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"…"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/translate/tone-preserve", 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": "…"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "translate.tone_preserve",
"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_tokens | 20000 |
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. |
422 | task_failed | The task failed after 3 retries. You are never charged for it. |