← Back to blog

Translating Japanese: 10 Pitfalls That Quietly Change the Meaning

A bad translation from French or Spanish usually looks bad: a clumsy phrase, a wrong word, something a reader trips over. A bad translation from Japanese often reads well. The output is fluent and grammatical, and the only way to spot the error is to go back to the source.

A translator on Hacker News described one case:

Dalewyn on Hacker News, in a thread on how manga was translated for America.

Two phrases, one said before the meal and one after, end up as the same English sentence, and the English reader has no way to tell which one the speaker used.

A single Japanese sentence with an empty subject slot fanning out into three different valid English sentencesA single Japanese sentence with an empty subject slot fanning out into three different valid English sentences
好きです (suki desu) with three valid English translations. The surrounding context decides which one is right.

Below are ten places where this happens, in both directions, each with an example and a check you can run on a finished translation. The romanizations follow Hepburn.

Grammar: what the Japanese source does not say

The first three problems have nothing to do with vocabulary. Japanese grammar leaves out information that English grammar requires, and the translator has to fill the gap.

1. The subject is missing, and the translator guesses

Japanese sentences often have no subject and no pronoun, because the speaker expects the listener to know from context. Take two words:

好きです。(suki desu)

That is a complete, natural Japanese sentence. It can mean "I like it," "I like you," or "she likes him," depending on what came before.

A machine translator has to output a subject, so it picks one. In isolation it tends to pick "I like it," the most frequent reading. If the paragraph before was about someone else, you now have a grammatical English sentence that says the wrong thing.

Short texts make this worse. One Hacker News commenter summed it up as "the smaller the chunks of texts are the worse a computer will do". UI strings, button labels, chat messages and subtitle lines are short and come without context, and Japanese omits the most in exactly those places.

The check: for each "I," "you," "he," "she" or "they" in the English output, find the matching word in the Japanese source. If it is not there, the translator inferred it, and you should confirm the inference against the paragraph around it.

2. Number is optional, and counters are not

Japanese nouns do not normally mark singular or plural. 猫がいます (neko ga imasu) can mean "there is a cat" or "there are cats." Plural markers exist (たち, ら, and reduplication as in 人々), but they are optional and mostly used for people. English makes you choose singular or plural for each noun, so each English plural is a guess the translator made.

English to Japanese has the opposite problem. Japanese cannot say "three files" without a counter, and the counter depends on the physical shape of the thing:

Counter Used for Example
冊 (satsu) bound volumes 本を三冊 (hon o san-satsu), three books
枚 (mai) flat, thin things 紙を三枚 (kami o san-mai), three sheets of paper
本 (hon) long cylindrical things ペンを三本 (pen o san-bon), three pens
台 (dai) machines, vehicles 車を三台 (kuruma o san-dai), three cars
匹 (hiki) small animals 猫を三匹 (neko o san-biki), three cats

本 is both the word for "book" and the counter for pen-shaped objects, and its reading changes with the number: 三本 is san-bon, not san-hon. To translate "three files" you need to know whether a file is a sheet of paper, a bound document or an icon on a screen. Generic counters exist (三つ, 三個), but they read as vague in product copy. A translator working from a spreadsheet of UI strings has no way to know which one you mean.

The check: search the Japanese output for numbers. For each one, confirm the counter matches what the thing is in your product.

3. The verb comes last, and so does the negation

Japanese is subject-object-verb, and the verb carries tense, politeness and negation. All of it comes at the end of the sentence:

彼は明日の会議に出席します。(kare wa ashita no kaigi ni shusseki shimasu), He will attend tomorrow's meeting.

彼は明日の会議に出席しません。(kare wa ashita no kaigi ni shusseki shimasen), He will not attend tomorrow's meeting.

The two sentences are identical until the last syllable. A human reading the whole sentence has no trouble. Anything that handles Japanese in fragments does: subtitle lines split across two frames, a UI string built from two variables, a chat interface that streams half a sentence, or a translator paid per line who works line by line.

It also means you cannot start the English sentence until you have read the Japanese one to the end, because the English has to be restructured around the verb.

The check: never translate a Japanese sentence that has been split across two strings, two subtitle lines or two table cells. Put it back together first.

Register: the decisions Japanese forces you to make

In English you can write a sentence without deciding how you stand with the reader. In Japanese the verb form encodes that relationship, so you have to decide.

4. Politeness is a choice on every verb

One Hacker News commenter joked that Japanese speakers speak four languages: "casual speech, normal polite desu/masu speech, humble speech, and keigo". The standard Japanese classification draws the lines differently: keigo (敬語) is the umbrella term, and it covers polite desu/masu forms, humble forms and respectful forms. Humble and respectful language point in two directions (lowering yourself, raising the other person) rather than sitting on one scale. For the request "please check this," you have at least these forms:

Form Japanese Reads as
Plain 確認して。(kakunin shite) A close friend, or a senior speaking to a junior
Polite (丁寧語) 確認してください。(kakunin shite kudasai) Neutral polite, safe with a stranger
Respectful (尊敬語) ご確認ください。(go-kakunin kudasai) To a customer, or to someone above you
Humble (謙譲語) ご確認いただけますか。(go-kakunin itadakemasu ka) Business email to a client
Four Japanese renderings of the English sentence "please check this": plain, polite, respectful and humble, with the last three grouped as keigo and each labelled with how it readsFour Japanese renderings of the English sentence "please check this": plain, polite, respectful and humble, with the last three grouped as keigo and each labelled with how it reads
"Please check this" in four Japanese forms. The English source does not say which one it needs.

The translator has to supply the level, and a machine supplies whatever its training data makes most likely. One commenter compared two systems on this point and wrote that "often times the tone from gpt4 are little bit 'rude'/direct or 'weird' in en to jp, deepl is as good as an example sentence they would put into a textbook".

Textbook polite can still be wrong for the situation. Business Japanese is hard enough that, as another commenter put it, "even Japanese themselves have to be instructed in how to use it when they enter corporate jobs". In a business email to a Japanese client, the wrong level can come across as rude or as oddly stiff, and the client will notice before they read your actual request.

A translated cover letter can fail the same way. Japanese gives you more levels to get wrong, and they do not sit on one scale.

The check: decide the register before you translate. Then read the Japanese output and confirm each sentence sits at that level. If the level changes partway through a message, a machine probably produced it and nobody reviewed it.

5. There is no neutral word for "you"

English "you" carries no tone. Japanese あなた (anata) does. Depending on context it reads as distant, textbook-like or confrontational, and in some households it is what a wife calls her husband. English-to-Japanese machine output uses it often, and a Japanese writer would rarely choose it.

Japanese usually handles the second person in one of three other ways:

  1. Leave it out. お時間ありますか (o-jikan arimasu ka), literally "is there time," is the normal way to ask "do you have time?"
  2. Use the person's name plus さん. 田中さんはどう思いますか (Tanaka-san wa dō omoimasu ka), "what do you think, Tanaka-san," said directly to Tanaka.
  3. Use their title. 部長 (buchō, department head) instead of a pronoun.

Marketing copy suffers most. English landing pages address the reader as "you" in every other sentence, and a direct rendering fills the Japanese page with あなた, which reads like a badly dubbed advertisement.

The check: count the occurrences of あなた in your Japanese output. In business or marketing text, the right number is usually zero or close to it.

6. Honorifics do not survive the trip

さん (-san), 様 (-sama), 先生 (-sensei), 先輩 (-senpai), 君 (-kun), ちゃん (-chan): each carries information English has no slot for.

田中さん (Tanaka-san) is the clearest case. The suffix says nothing about gender, so "Mr. Tanaka" or "Ms. Tanaka" each adds a fact the Japanese did not state. "Tanaka" alone drops the politeness and, in an English business context, reads as curt. "Tanaka-san" keeps everything but marks the text as a translation.

先輩 (senpai) is harder, because English has no equivalent word. It means someone who entered the same school or company before you, and the relationship carries obligations in both directions. "Senior colleague" is the dictionary answer and sounds flat. "Mentor" implies a relationship that may not exist.

You have to make a decision here, and you have to make the same one on every page.

The check: pick one policy per project (keep honorifics, drop them, or convert them) and grep for exceptions. The defect is a document that mixes policies.

7. Speech style encodes gender, age, and role

Japanese fiction and dialogue use 役割語 (yakuwarigo), role language: the way a character talks tells you who they are. The first-person pronoun does a lot of this. 俺 (ore) is blunt and masculine, 僕 (boku) is softer and male, often younger or more reserved, 私 (watashi) is neutral-polite, and わたくし (watakushi) is formal. Sentence-final particles and endings like ぜ, わ and のよ add gender and attitude on top, at least in standard Tokyo speech.

English has no equivalent, so a translator going from English dialogue to Japanese has to invent a voice for each character. If they pick the wrong one, the character comes out miscast. Legends of Localization collects examples: a man in Stardew Valley who switches between feminine and masculine speech, a demon who talks in a feminine register, and a Harry Potter character who sounds female in Japanese while female characters sound male.

Each line in those examples can be accurate on its own. The problem shows up across lines, in who the character sounds like.

The check: if you are localizing anything with a voice, a character or a brand persona, write a one-paragraph brief per speaker before translation starts: pronoun, politeness level, age, and relationship to the listener. Translators cannot infer this from an English string table, and different translators on the same project will guess differently.

Try Fink for your next translation

See the translation, every change, and the why on one screen.

Open App

Vocabulary: words that look safe and are not

The last three problems are about words. A word crosses into the other language looking intact while its meaning changes, and this happens in both directions.

8. Katakana loanwords are false friends

Japanese borrows heavily from English and then shifts the meaning. Some of these words are 和製英語 (wasei-eigo), English coined in Japan. More often they are ordinary loanwords whose meaning drifted after borrowing. They look like easy translations and mislead in both directions.

Katakana Looks like Actually means
マンション (manshon) mansion a concrete apartment or condo, the step up from アパート
クレーム (kurēmu) claim complaint
サービス (sābisu) service free of charge, on the house (the ordinary sense survives too)
ナイーブ (naību) naive sensitive, innocent, mildly critical but without the English sting
コンセント (konsento) consent electrical outlet
スマート (sumāto) smart slim, slender
バイキング (baikingu) Viking buffet
Six katakana loanwords shown with the English word they resemble and the different thing they actually meanSix katakana loanwords shown with the English word they resemble and the different thing they actually mean
Six of the loanwords from the table, with the English word each one resembles.

A Japanese customer support log full of クレーム records complaints, not insurance claims. A restaurant sign that says ドリンクはサービスです is offering a free drink. Machine translation handles the famous cases and misses the rest, and because the output is a real English word in a plausible sentence, nothing looks wrong.

The check: in Japanese-to-English work, flag each katakana word that resolves to an English cognate and look it up in a Japanese dictionary.

9. Over-translating what should have stayed in English

This is the opposite mistake. Japanese software, games and signage keep a lot of English. Buttons say Save, Start, Cancel, and Japanese readers expect that. If you translate all of it into kanji, the product can read as amateur or old-fashioned.

Legends of Localization records a player's reaction to a Western game that translated the spell "Flash Heal" as 瞬間治療 (shunkan chiryō) instead of leaving it in katakana: "As soon as I saw that, I immediately got turned off." The translation was accurate, but it broke a genre convention: Japanese fantasy games usually keep spell names as phonetic English.

The check: before translating a string table into Japanese, look at two or three comparable Japanese products in the same category and note which terms they left in English. Follow their convention.

10. Set phrases that have no English counterpart at all

The itadakimasu problem from the opening belongs here, and mealtimes are only one example.

  • お疲れ様です (otsukaresama desu) opens internal emails, greets a colleague you pass in the hallway, and thanks someone for work done. Arriving in the morning, you say おはようございます instead. When you leave for the day, you say お先に失礼します, and the colleagues who stay answer お疲れ様でした. English has no single phrase that covers these uses.
  • よろしくお願いします (yoroshiku onegaishimasu) closes most Japanese business emails. It means something like "I am counting on your goodwill going forward." "Best regards" carries none of that.
  • いただきます / ごちそうさま (itadakimasu / gochisōsama) are a pair, one before the meal and one after. English has at most one phrase for both.

One commenter explains why いただきます resists translation: it is kenjōgo, humble language, and the verb 頂く lowers the speaker relative to whoever provided the food. The politeness sits inside the verb, and English verbs have no form for it.

Japanese speakers also do not treat these phrases as universal rituals. Another commenter pushes back on that picture: many people say ごちそうさまでした on leaving more reliably than they say いただきます on being served, and TV dramas make the custom look more uniform than it is. So a translator can get a set phrase wrong, and a writer can also get it wrong by explaining it as a national rule.

The check: when you hit one of these, skip the search for an equivalent phrase. Work out what the phrase does in this sentence (greeting, thanks, closing, acknowledgement) and write English that does that job in that position.

When the output is fluent and wrong

In all ten cases, the output reads fine. The English is fluent, the Japanese is fluent, and no tool flags anything.

Machine translation has gotten more fluent faster than it has gotten more accurate. One Hacker News commenter who works with Japanese wrote: "In my experience with Japanese, DeepL is good at making plausible but inaccurate sentences." Another, comparing DeepL with a prompted language model for Japanese to English, wrote: "for Japanese to English translation, DeepL is hot garbage compared to a top class LLM with the right prompt."

Language models are good at translation, and their strongest skill is producing text that sounds natural. When the source language leaves out information as often as Japanese does, natural-sounding output can still be wrong.

Back translation catches a lot of these errors, and most people skip it. Translate the output back into the source language and read the result for what is missing, not for awkwardness. If the round trip loses the subject you meant, drops a clause or comes back at a different politeness level, you have found an error before your reader does.

Back translation has limits. DeepL is strong on Japanese and widely used in Japan, and a good language model with a careful prompt handles long Japanese prose well. Both will still produce fluent, wrong output on the ten patterns above, because the missing information was never in the source text. For anything that matters, have a native speaker read it.

Fink shows a back translation and meaning notes next to each translation, so you can do this round trip without running a second translation yourself.

The checklist

Run this on a finished translation, in either direction, before it ships.

  • Pronouns. For each "I," "you," "he," "she," "they" in the English, find the corresponding word in the Japanese. If it is not there, the translator inferred it. Check it against the context.
  • Number. Each English plural came from a Japanese noun that did not mark plurality. Confirm each one.
  • Counters. Each number that counts objects takes a counter. Confirm it matches the physical shape of the thing in your product.
  • Split sentences. No Japanese sentence was translated while broken across two strings, two subtitle lines or two table cells.
  • Register. One politeness level, chosen on purpose, held from the first sentence to the last.
  • あなた count. Close to zero in business and marketing text.
  • Honorific policy. One rule for the whole document, with no leftovers from an earlier pass.
  • Speech style. Each speaker's pronoun and sentence endings fit that character in all of their lines.
  • Katakana. Each katakana word that looks like an English word was checked in a dictionary.
  • Untranslated English. You left in English the terms comparable Japanese products leave in English.
  • Set phrases. Each one was rendered by what it does in that position.
  • Back translation. Round-tripped and read for missing information.

Questions people ask about this

Why is Japanese so hard to translate into English? Japanese grammar omits information that English grammar requires. Sentences often leave out subjects and pronouns, nouns do not mark singular or plural, and the verb carrying tense and negation comes at the end of the sentence. The translator has to supply all of that from context, and when the context is missing, you cannot see the guess in the finished text.

Is it harder to translate Japanese to English, or English to Japanese? They are hard in opposite ways. Japanese to English means recovering information the source never stated: who did what, how many, to whom. English to Japanese means adding information the source never needed: politeness level, speech style, counters, and how to address the reader.

Can Google Translate or DeepL handle Japanese? Both produce fluent Japanese. DeepL is often rated better on this pair and is widely used in Japan. Both will still guess a subject, default to one politeness level, and render katakana false friends as their English lookalikes, without flagging any of it. Use them, then check the output against the list above.

Why do Japanese sentences have no subject? Japanese speakers leave the subject out when context makes it clear, the way English drops it in "Sounds good" or "Been there." Japanese does this far more often, including in formal writing, so a sentence that looks like a fragment to an English reader is complete and ordinary in Japanese.

Do I need to keep honorifics like -san and -chan in English? It depends on the text; what matters is consistency. Keeping them preserves gender neutrality and politeness but marks the text as a translation, which is normal in manga and subtitles and unusual in business documents. Converting さん to "Mr." or "Ms." adds a gender the Japanese did not state. Pick one policy per project and apply it throughout.

What is the most useful check for a Japanese translation? Back translation. Translate the result back into the original language and read the round trip for missing information rather than for style. Without a native speaker, it is the best way to catch dropped subjects, dropped clauses and shifted register.

Sources and further reading

The translator quotes in this post are verbatim from public Hacker News comments: Dalewyn on translating itadakimasu and gochisousama, stevefan1999 on itadakimasu as kenjōgo, unsignedint on how the custom is actually used, TheDong on Japanese politeness levels, codyrobbins on business keigo, cehrlich on short-chunk translation, methou on English-to-Japanese register, CarVac and yesco on machine translation quality. The game localization examples come from Legends of Localization, Common Problems When Translating Games Into Japanese. For typography and layout constraints when publishing Japanese, the W3C's Requirements for Japanese Text Layout is the reference. For reading Japanese in the Latin alphabet, see Hepburn romanization; for why machine translation is fluent before it is accurate, see why LLMs are good at translation; and for back translation as a routine check, see how to use a translator to learn a language.