Skip to main content

When Claude Refuses to Translate: How to Diagnose and Fix It

If Claude refuses to translate text or replies in the wrong language, the cause is usually one of four things: content filtering, copyrighted text, language settings, or a session length limit. Here's how to tell which one and fix it.

By
🌐 This article was machine-translated and may contain inaccuracies. Read the Korean original if in doubt.

💬 1 copy-ready prompt in this article →

Have you ever asked Claude to translate a sentence, a set of lyrics, or a document, only to get a refusal message instead — or a reply in a language you never asked for? The cause is usually one of four things, and each has its own way to check and fix it. This guide walks through them in order.

🟢 Model references match the current lineup · model notice · Fable subscription
🟢 Model references match the current lineup · Claude Opus 5.5 / Claude Sonnet 5 / Claude Haiku 4.5 (higher tier: Claude Fable 5.1). This notice changes only when Anthropic ships a new model.

Fable 5 and 5.1 subscription (updated September 7, 2026): Claude Fable 5.1, released September 1, 2026, is the current Fable model and Fable 5 is now legacy. Plan terms are the same for both — Max and Team Premium plans include Fable at up to 50% of the weekly usage limit; Pro and Team Standard use usage credits (

🟢 Model references match the current lineup · Claude Opus 5.5 / Claude Sonnet 5 / Claude Haiku 4.5 (higher tier: Claude Fable 5.1). This notice changes only when Anthropic ships a new model.
0/M input, $50/M output tokens). The one-time
🟢 Model references match the current lineup · Claude Opus 5.5 / Claude Sonnet 5 / Claude Haiku 4.5 (higher tier: Claude Fable 5.1). This notice changes only when Anthropic ships a new model.
00 credit applied only to the Fable 5 transition and is not offered for 5.1. Some coding and debugging requests may be answered by an Opus model due to a security classifier (both models). See the Fable 5.1 guide and the Fable 5 availability guide for details.

Translation request → odd result Filtering policy message shown Whole lyrics/book requested Reply comes in wrong language Reply cuts off or never arrives ① Content filtering ② Copyrighted text ③ Language mix-up ④ Session/length limit

What you'll be able to do after reading this

When a translation is refused or comes out strangely, you'll be able to look at the message and situation and tell which of four causes it is — content filtering, copyrighted text, language mix-up, or a session/length limit — and re-ask in a way that fits the cause. Reading and applying this takes about 5-10 minutes.

Before you start

  • You'll need to be logged into your Claude account, in a chat window on the web or app.
  • If you can still see the exact message or response you got when the translation was refused, diagnosing the cause is much easier — don't clear the conversation before you check it.
  • This applies the same way across the Free, Pro, and Max plans.

Quick terms

  • Content filtering policy — an automatic check that blocks requests or responses containing content that violates Claude's usage policies, such as violent, sexual, or hateful material.
  • Session — everything exchanged in a single chat window. The longer a conversation runs, the less room Claude has to reference earlier parts of it (its context window).
  • Response language — the language Claude actually writes its answer in, which is separate from your interface language (the language of menus and buttons on screen).

Why translations get refused: four causes

When Claude refuses to translate or answers oddly, the cause generally falls into one of four buckets: content filtering, copyrighted text, a language mix-up, or a session/length limit. The table below summarizes the signs and fixes for each.

CauseWhat you'll seeHow to fix it
① Content filtering policyA message like "Output blocked by content filtering policy," or the conversation simply stops with no explanationExplain your purpose/context, or re-ask with only the unproblematic portion
② Copyrighted textAsking for a full translation of song lyrics or a book excerpt gets refused or only partly translatedAsk for a portion instead of the whole thing, or shift to a summary/meaning-focused request
③ Language/response mix-upNot a refusal, but the reply comes in a different language than requestedState the target language explicitly in your message; check your preferred language setting
④ Long text/session limitThe reply cuts off mid-way, or no reply arrives at allSplit the text and ask in sequence, or start a new conversation

Checking each cause in detail

① Hitting the content filtering policy

If the text you're translating contains material Claude's usage policies restrict — violent or sexual language, hate speech, and similar — the translation itself can be blocked. This can show up as an on-screen filtering notice, or simply as the response stopping with no explanation.

To work around it, explain why you need the translation (citing academic material, analyzing a news article, and so on), and try re-asking with just the portions that don't contain flagged content rather than the whole passage. If it's still blocked, asking for a summary or a description of the tone instead of a literal translation can also work.

② Text protected by copyright

Asking Claude to translate song lyrics or a full book passage from start to finish can get refused, or come back only partially translated, because that text is protected by copyright. Even if you just want to understand what the lyrics mean, breaking the request into a few lines at a time — or asking "what does this passage mean" instead of "translate this" — improves your odds of getting a response.

③ Confusing language settings or response language

This is different from an outright refusal. Here, the reply comes back in a language other than the one you asked for, or the translation mixes in words from a different language than the source text. According to Anthropic's support article, How to use Claude in your preferred language, Claude determines its response language based on conversation context and your settings. If you need a specific language, the most reliable approach is to state the target language directly and explicitly in your message — for example, "translate this sentence into English."

④ Long source text or a session limit

If the text you're translating is very long, or the same chat window has already carried a lot of back-and-forth, the reply may cut off mid-way or never arrive. This isn't a refusal so much as a limit on how much can be processed at once. Try splitting the source text into paragraphs or chapters and asking in sequence, or start a fresh conversation and try again.

Three steps to resolve it

1 Diagnose cause 2 Apply a fix 3 Ask again

Whatever the cause, the order is the same: first read the message and situation to figure out the cause, then apply the fix that matches it (explaining context, splitting the passage, stating the language, or splitting the source text), then — starting a new conversation if needed — ask again.

Common sticking points and what to do

  • Resending the exact same request without diagnosing first — repeating the identical message is likely to get refused for the same reason each time. Check the table above for the sign that matches your situation first.
  • Continuing to try in an already-long conversation — the longer the session runs, the harder it is to isolate the cause. Opening a new chat window and re-asking with just the source text makes the situation clearer.
  • Not being sure why it was refused — if there's no explanation and simply no response, it's hard to pin down the exact cause. In that case, splitting the source text into shorter pieces and narrowing down where it stops working is the safer approach.

Don't confuse this with other error messages

A translation refusal is different from a temporary server-side error. Messages like a "529" error or "Something went wrong" reflect a temporary issue with the Claude service itself, and can appear regardless of what you're asking for. If you're seeing one of those, see how to handle a Claude 529 error or how to handle a "Something went wrong" error instead of this guide.

Frequently asked questions

Q. What exact message shows up when a translation is refused?
You may see a message like "Output blocked by content filtering policy," or the response may simply stop with no explanation. The exact wording can vary by situation, so checking what's actually displayed on your screen is the most reliable way to tell.

Q. Why don't song lyrics translate well?
Asking for a full translation of lyrics or a book passage — text protected by copyright — can get refused or only partly translated. Breaking the request into shorter portions and asking about meaning rather than a literal translation improves your odds of a response.

Q. Does changing my language settings fix translation refusals?
No. Language/response-language issues have a different cause than a content-filtering refusal. If replies keep coming in the wrong language, explicitly stating your target language in the message is the more reliable fix.

Q. Are a 529 error or "Something went wrong" message the same as a translation refusal?
No. Those messages reflect a temporary issue with the service itself and can appear regardless of what you're asking for. If you keep seeing them unrelated to translation content, check the dedicated error-handling guides instead.

💬 Prompts for this problem

Copy, paste into Claude, and swap the parenthesised bits for your own situation.

  • 번역을 거부당했어, 왜 그런지 같이 보자

    Use when: 클로드가 번역을 거부하거나 중간에 멈출 때

    클로드에 번역을 시켰는데 거부당했어. 내가 넣은 원문은 뉴스 기사 일부이고, 폭력 사건을 다룬 내용이 들어 있어. (여기를 네 상황으로 바꿔 써)
    
    왜 막혔을 만한지 가능한 이유를 짚어주고, 내용을 왜곡하지 않으면서 다시 요청할 수 있는 방법이 있으면 알려줘. 규칙을 우회하는 방법 말고, 목적을 분명히 밝혀서 정상적으로 처리되게 하는 쪽으로.

All prompts →

Was this helpful?

Keep reading