Claude translates fluently between major languages, and fluency is exactly the trap: the output reads smoothly even where it is wrong. It is genuinely useful for first drafts, for keeping terminology consistent across a long job, and for explaining what it changed. It is weakest on idioms, on terms that mean two things, and on the unwritten rules of a specific market. Use it with a brief (language variant, audience, formality), a glossary you approve before translation starts, and a back-translation check in a fresh chat. For anything that needs a sworn or certified translator, it is a draft at best.
На этой странице
- What do you tell Claude before it translates a word?
- How do you keep terms identical across fifty pages?
- How do you check a translation in a language you do not read?
- What is the difference between translating and localizing?
- An option for quick, controlled text
- Where does Claude fail at this?
- Which translation skill fits which job?
- How do you install a translation skill in Claude?
- Related guides
- Frequently asked questions
Our running example is invented: an English email for a small online bakery shop, "Your order is on its way", going into Spanish for customers in Mexico and in Spain. The Spanish is short on purpose, so a native reader can check it in seconds.
What do you tell Claude before it translates a word?
"Translate this into Spanish" leaves five decisions to chance, and each one changes the text:
Which Spanish. "Your order is on its way" is Tu pedido va en camino in Mexico and Tu pedido está de camino in Spain. The same split runs through vocabulary: celular or móvil, computadora or ordenador. A language name is not a market.
Who is reading. Retail customers, lawyers and teenagers need different registers.
Formal or informal address. Spanish has tú and usted; German, French, Polish and Japanese make a similar choice on every line. If you do not say, Claude picks one and may drift between the two halfway through.
What must not change. Product names, brand terms, placeholders such as {first_name}, and anything in code.
Where the text lives. Email body, button, subtitle and legal clause have different length and tone rules.
Put these in one brief and make Claude ask before it writes:
The numbered question list is the valuable part: a brief that seems complete almost always has two holes.
How do you keep terms identical across fifty pages?
Inconsistent terminology is the quiet failure of long translation jobs. The same "basket" becomes carrito on one page and cesta on another, and a customer wonders whether they are different things. Claude does not reliably hold your wording once the text is long, and it does not carry it to the next session.
Build the glossary first, approve it, and paste it into every later request.
For Dana's bakery the table might contain basket → carrito (MX) and track my order → rastrear mi pedido, each marked "proposed" until a Spanish speaker confirms them. You then paste the approved table at the top of every batch. Keep it in a Claude Project or a file, not in a chat that will scroll away.
The AI Translator (text) prompt below builds this loop in: tone control, a glossary and a back-translation.
How do you check a translation in a language you do not read?
Use a back-translation, but only in a clean session. In the same chat, Claude has seen your source and will quietly steer the English back toward it. Open a new chat, paste only the target text, and ask for a literal return to English:
Then compare the English you get with your original, line by line. Differences point to a problem in the translation, or in a source that was never clear. If a phrase comes back as nonsense, someone who reads the language should look at it.
A back-translation has limits. Two mistakes can cancel each other out and return a perfect-looking English sentence. It cannot catch a phrase that is correct but sounds odd in the target market. Treat it as a smoke test for non-readers, not as proof. If the text matters, pay a native reviewer for twenty minutes.
What is the difference between translating and localizing?
Translation moves the words. Localization changes what is needed so the reader behaves as if the text had been written for them: date format (03/04 means March 4 to an American and 3 April to most of Europe), currency, units, the sports metaphor that means nothing outside the US, the "free shipping over $50" line that needs a different threshold. Claude can do this well if you ask for it as a separate pass and require a log, because a silent adaptation looks like a mistake in the review.
The log lets a non-reader audit the work. The "needs a human decision" list shows which choices it was quietly making for you.
What the output looks like (illustration only)
Invented example for the bakery email, shown so you can see the format. Have a native speaker check any real text.
An option for quick, controlled text
For quick tone-controlled translation
AI Translator (text) · $5
A beginner-level prompt: you paste the text, name the target language and tone, and it returns a context-aware translation with glossary support for terms that must stay fixed, then checks the result with a back-translation. Per its product page, the back-translation step gives you a way to check output in a language you do not read.
Where does Claude fail at this?
It translates idioms literally, or over-corrects them. "Hit the ground running" can come out word for word, or get replaced with a local saying that sounds forced. Ask for a plain-meaning equivalent and review every idiom flagged in the log.
It mishandles words with two meanings when the sentence is short. A button that says "Order" (noun or verb?), "Table" (furniture or data) and "Bank" have no context to settle them. Give it the screen, the role of the string and a note on who will see it.
It drifts on register. In a long text it may start with usted and slip into tú, or mix regional vocabulary. Ask for a register check at the end and a search for the forbidden variants.
It misses false friends and near-miss terms. Words that look the same across languages but differ in meaning are a classic trap, and the confident tone gives no warning. Domain terms (medical, financial, technical) are worse: a reasonable-sounding word may not be the term professionals actually use. Make a specialist confirm any glossary entry that matters.
It does not know your string limits. Languages often expand: German and Spanish text can run longer than English. Give it the character limit and ask for the count, and verify the count yourself in a tool.
It is uneven across languages. Quality is generally strongest in widely used languages and lower for smaller ones, so for a less-common language assume more errors and budget for review.
It is not a certified translator. Contracts, court documents, immigration papers, patents, medical records and drug information may need a sworn, certified or specialist translator for the document to be accepted or to be safe. Use Claude to understand such a document and to prepare a working draft, never to submit one. This guide is not legal advice and does not replace a qualified professional.
Which translation skill fits which job?
| Skill | Best for | Price |
|---|---|---|
| AI Translator | A real job: asks the variant and formality first, lists what it adapted and why, builds a glossary | $19 |
| AI Translator (text) | Quick translation with tone control, a glossary and a back-translation check | $5 |
| International Expansion & Localization Specialist - Kwabena | Market-by-market launch planning rather than translating a text | $19 |
How do you install a translation skill in Claude?
With an All-in-one subscription there is nothing to download. Add KissMySkills to Claude once as a connector: open Customize → Connectors, click +, then Add custom connector, and paste https://mcp.kissmyskills.com/mcp. Sign in with your email, then ask for the skill by name, for example "load AI Translator". The same connector works in ChatGPT, Claude Code, Codex and Cursor; the step-by-step setup for each is on the connector page. Signing in is free, and your first skill call starts a 7-day free trial with every skill.
Bought the single file? You download one .skill file, which is a ZIP archive with SKILL.md inside. In Claude, turn on code execution under Settings → Capabilities, then open Customize → Skills, click +, choose Upload a skill, pick the file as it is and toggle the skill on. In ChatGPT, Gemini or another chat, open the file as a ZIP and paste SKILL.md into custom instructions. AI Translator (text) is a .txt prompt: paste it into a Project or a new chat. A Claude Project works best, since it keeps your glossary between jobs.
Need more than one specialist?
Buying AI Translator gets you one file. The All-in-one subscription loads every skill in the catalog through one connector, in Claude, ChatGPT Business, Enterprise or Edu, Claude Code, Codex or Cursor, and keeps each skill updated when we improve it. $12 a month or $69 a year, with 7 days free and every skill included.
Start the free trial → Why a subscription beats buying filesRelated guides
- How to Use Claude as a UX Writer
- How to Use Claude as a Copywriter
- How to Write Product Descriptions
- How to Use Claude as a Legal Assistant
Frequently asked questions
Is there a Claude skill for translation?
Yes. AI Translator ($19) asks for the language pair with its regional variant, the audience, the text type and the formality level before writing, then returns the translation, a list of what it adapted and why, open questions and a glossary table. AI Translator (text) ($5) is a lighter prompt with tone control, a glossary and a back-translation check.
Can Claude translate with a consistent glossary?
Yes, if you build the glossary first and paste it into every request. Ask Claude to extract terms from your source, show both options for terms with two translations, and mark each as proposed until a speaker of the language approves it. Keep the approved table in a Claude Project so it carries between sessions.
How do I check a translation in a language I cannot read?
Open a new chat, paste only the translated text and ask for a literal back-translation into your language, plus a list of unnatural or regional phrases. Compare it to your original. It is a smoke test, not proof, since two errors can cancel out, so pay a native reviewer for anything important.
What is Claude bad at when translating?
Idioms, words with two meanings in short strings, register drift (formal switching to informal), false friends and specialist terms, and languages with less training material. It also sounds equally confident when it is wrong. Give context for every short string, require a log of what it adapted and have a native speaker review text that matters.
Can Claude produce a certified or legal translation?
No. Contracts, court documents, immigration papers, patents and medical records may need a sworn or certified translator, depending on the country and the use. Claude can help you understand such a document or prepare a draft for the translator, but it does not replace the professional, and this guide is not legal advice.
AI Translator
Or get it with every other skill in All-in-one: $12/month, 7 days free, every skill.