There is a gap between correct Japanese and natural Japanese. Closing the second half of that gap is what separates apps that get adopted from apps that quietly underperform in Japan. This article covers seven techniques that make app copy sound like it was written, not translated.
For the diagnosis side — what makes copy sound translated — see why AI translation fails for Japanese app copy.
Technique 1: Drop the Subject Aggressively
English builds sentences around a subject. Japanese builds sentences around context. If the subject is clear, drop it.
❌ あなたのアカウントを削除しますか？ ✅ アカウントを削除しますか？
❌ 私たちはあなたに通知を送ります。 ✅ 通知をお送りします。
This rule applies even when the subject is implied to be the app:
❌ アプリは新しい更新を確認しています。 ✅ 更新を確認中です。
The fastest way to make any Japanese copy sound more native is to delete every 「あなた」 「あなたの」 「私たち」 「アプリ」 unless its absence creates real ambiguity.
Technique 2: Replace 「することができます」 With 「できます」
「することができます」 (literally "is able to do") is a grammatical construction that's correct but verbose. Native writers shorten to 「できます」.
❌ ファイルを共有することができます。 ✅ ファイルを共有できます。
❌ アカウントを削除することができます。 ✅ アカウントを削除できます。
❌ 通知をオフにすることができます。 ✅ 通知をオフにできます。
This single substitution eliminates 4 characters per occurrence and tightens the rhythm. Apply it everywhere it appears.
Technique 3: Use Compound Verbs to Pack Meaning
Japanese has highly productive compound verbs that pack two actions into one word. Native writers use them; MT typically does not.
| English (multi-step) | Awkward translation | Native compound |
|---|---|---|
| "Send the file by email" | ファイルをメールで送る | ファイルをメール送信する |
| "Continue reading" | 読み続ける (correct, native uses this) | 読み続ける ✓ |
| "Save and exit" | 保存して終了する (fine) | 保存して終了 (drop する) |
| "Search and select" | 検索して選択する | 検索して選ぶ |
| "Sign up and start" | 登録して開始する | 登録してスタート |
Compound forms collapse multi-step actions into single phrases that flow more naturally.
Technique 4: Prefer Action Nouns Over Action Verbs in Headers
English: "Edit Profile." Japanese app convention: 「プロフィールを編集」 (object + noun-form action) rather than 「プロフィールを編集する」 (object + full verb).
The noun form is shorter, looks cleaner in headers and buttons, and matches what shipping apps actually use.
| English header | Verb form (less native) | Noun form (more native) |
|---|---|---|
| Edit Profile | プロフィールを編集する | プロフィールを編集 |
| Add Friend | 友だちを追加する | 友だちを追加 |
| Delete Account | アカウントを削除する | アカウントを削除 |
| Send Message | メッセージを送信する | メッセージを送信 |
Save the verb form for body sentences that need a complete sentence rhythm.
Technique 5: Use 「〜中」 for Progressive States
English progressive ("loading," "saving," "syncing") translates awkwardly with 「〜しています」. The native shortcut: 「〜中」 ("in the middle of").
| English | Awkward | Native |
|---|---|---|
| Loading… | 読み込んでいます… | 読み込み中… |
| Saving… | 保存しています… | 保存中… |
| Syncing… | 同期しています… | 同期中… |
| Updating… | 更新しています… | 更新中… |
| Connecting… | 接続しています… | 接続中… |
「〜中」 is shorter, looks cleaner in compact UI, and is universally understood.
Technique 6: Rewrite Idioms, Don't Translate Them
English marketing leans on idioms. Japanese marketing has its own idioms, but they're different. Rewriting requires understanding the underlying message and choosing a Japanese idiom (or non-idiomatic alternative) that fits.
"Game-changing feature." ❌ ゲームを変える機能。 ✅ 使い方が変わる、新機能。 (literal: "the way you use it changes — a new feature.")
"We've got you covered." ❌ 私たちはあなたをカバーしています。 ✅ あなたに必要なものはすべて揃っています。 (literal: "everything you need is here.")
"Set it and forget it." ❌ 設定して忘れてください。 ✅ 一度設定すれば、あとはおまかせ。 (literal: "set once, leave the rest to us.")
"Easy as 1-2-3." ❌ 1、2、3のように簡単です。 ✅ たった3ステップで完了。 (literal: "completes in just 3 steps.")
Rewriting requires you (or your translator) to know what the English source is trying to do — establish ease, scale, completeness — and pick the Japanese phrasing that does that. There is no formula.
Technique 7: Match the Sentence Rhythm to the UI
This is the subtlest technique and the highest-leverage. Japanese apps have a rhythm of short sentences in compact UI, longer sentences only in body content. Western copy that gets transplanted unchanged often has the wrong sentence length for the UI surface.
Examples
A modal title in Western copy:
"Are you sure you want to delete this account? This action cannot be undone."
Translated faithfully:
このアカウントを削除してもよろしいですか？この操作は元に戻せません。
This is correct. It's also wrong for the surface. The native version splits across two lines with sharper rhythm:
アカウントを削除しますか？ 削除した内容は復元できません。
Two short sentences, each on its own logical line. The user reads each one in 1–2 seconds. The Western version asks the user to parse a 25-character question + a 14-character disclaimer in one breath.
Push notification
Western:
"Don't forget to log your meals today! Your streak is at risk."
Faithful translation:
今日の食事を記録するのを忘れないでください！ストリークが危険です。
Native version:
今日の食事、記録しましたか？ 連続記録が途切れそうです。
The native version is two short statements, conversational, with the same emotional content packed differently. The faithful version reads as alarmist; the native version reads as concerned.
This rewriting cannot be done by translation tools. It requires a writer who has internalized Japanese app rhythm.
Putting It Together: A Worked Onboarding Screen
Source English:
Welcome to FocusFlow! FocusFlow helps you stay productive by blocking distracting apps and tracking your deep work time. You can customize your blocking schedule and review your productivity stats at any time. Are you ready to get started?
Faithful translation (acceptable but not great)
FocusFlowへようこそ！ FocusFlowは、気を散らすアプリをブロックして集中時間を計測することで、あなたの生産性を高めるお手伝いをします。 あなたはいつでもブロックスケジュールをカスタマイズしたり、生産性の統計を確認したりすることができます。 始める準備はできましたか？
Native rewrite
ようこそ、FocusFlowへ。 集中したい時間に、邪魔になるアプリをブロック。 深い集中時間を、自然と積み上げられます。 ブロック時間や統計はいつでも変更・確認できます。 さっそく始めましょう。
The rewrite:
- Drops 「あなた」 and 「あなたの」.
- Replaces 「することができます」 with 「できます」.
- Splits long sentences into shorter ones.
- Uses noun-form headers where appropriate.
- Replaces "are you ready?" with the more natural 「さっそく始めましょう」.
It's about the same length. It just sounds like a person.
A Self-Check You Can Run
For any Japanese string longer than a single button label, ask:
- Is there an 「あなた」 or 「あなたの」? If yes, can it be deleted? If yes, delete.
- Is there 「することができます」? Replace with 「できます」.
- Is there a Japanese idiom that doesn't translate the English idiom? Rewrite.
- Is the sentence longer than 30 characters and would feel better split? Split.
- Does the rhythm match the surface? Modal title = short. Empty state = inviting. Push = conversational. Body = readable.
Run this on your existing Japanese strings. Each pass tightens the copy. Three passes is usually enough.
Where to Go Next
- Why AI Translation Fails for Japanese App Copy
- Keigo in Apps: When to Use Polite, Plain, or Casual Japanese
- Japanese UX Writing: Microcopy That Feels Native
- The 12 Most Common Mistakes in Japanese App Localization
We rewrite app copy with the techniques above as part of every Japanese localization engagement. Contact us if your existing strings need a native pass.