Claude has no dedicated translate button like a typical translation app. Instead, you translate by asking in the regular chat or uploading a document. That may sound like a drawback, but it actually lets you direct exactly how the translation should read — matching tone, formality, and terminology. This guide covers how to translate well with Claude, plus its limits.
Three basic ways to input text
Translation is a conversation, not a special mode. You'll use one of three methods.
- Paste text — For short sentences or paragraphs, paste them into the chat and state the target language.
- Upload a file — Attach a PDF, Word, or text file to translate the whole document, or summarize then translate.
- Target a section — Translate only a specific passage, or set conditions like "leave tables as-is, translate body text only."
Five prompt elements that improve quality
The same text yields very different results depending on how you ask. The more you specify, the more natural it reads.
- Target language and direction — Be explicit: "into English," "into Korean."
- Audience and formality — Specify tone: "business email tone," "casual message to a friend," "academic style."
- Terminology consistency — Pin proper nouns and jargon: "keep as in the original" or "follow this glossary."
- No translationese — State it: "natural, as a native speaker would write, not literal."
- Preserve formatting — Ask to keep "tables, lists, line breaks" or "keep markdown."
Translating long documents
Claude can handle a large context of hundreds of thousands of tokens at once, so long reports, contracts, and papers can be uploaded whole to translate, or to summarize and translate together. For very large volumes, we recommend:
- Split by chapter or section — Asking for too much at once can degrade quality toward the end; work in chunks.
- Pin a glossary first — Agree on key term translations in the first message, then apply that standard throughout for consistency.
- Use Projects — For repeated translation in the same style, store instructions and a glossary in a project so you don't re-explain each time.
Limits and when human review is needed
AI translation is fast and convenient, but not infallible. Keep these in mind.
- Translationese may remain — You may see noun stacks, English-like sentence structures, or long dashes (—). Asking "revise to read more naturally" cleans it up.
- Technical, legal, medical — Fields where accuracy is critical need a human expert's review. Treat AI output as a draft.
- Sensitive data — Don't paste personal or confidential documents as-is; mask them first.
- New proper nouns — Recently coined names or neologisms may be rendered inconsistently; verify them.
Summary
The key to translating with Claude isn't a "feature" — it's how you instruct. Each line you add (audience, tone, terminology, no translationese) makes the result more natural. For long documents, pin a glossary first and split by chapter for consistency. And always have a human review documents where accuracy matters.
Related: Summarizing long documents, How to write better prompts, Does Claude support Korean.