TL;DR
Modal and dialog localization fails Japanese users in four consistent patterns: titles that restate the action without explaining the consequence, button labels that are literal translations of "OK" and "Cancel" without matching Japanese decision grammar, body copy that uses a register too casual for the severity of the action being confirmed, and alert banners that mix error severity levels through inconsistent Japanese phrasing. None of these require more than targeted copy revision — but each one, left unfixed, introduces friction at the exact moment Japanese users need to trust the product most.
Key Takeaways
- Modal titles should state the consequence, not just the action — "削除の確認" (Delete Confirmation) describes the UI pattern; "このデータを削除しますか？" (Delete this data?) states the decision the user is being asked to make.
- "OK" and "Cancel" are not good Japanese modal button labels — Japanese confirmation dialogs in enterprise software use action-specific labels that name what the button does: 削除する, キャンセル, 保存する — not generic OK.
- Modal body copy should match the severity of the action — a destructive action confirmation needs formal register (丁寧語) with explicit consequence statement; an informational modal can use lighter copy without sacrificing clarity.
- Warning and error modals require distinct Japanese phrasing patterns — Japanese users distinguish between a warning (注意) and an error (エラー) and an alert (アラート) based on the vocabulary and structure of the message, not only the color of the modal header.
- The close button matters more in Japanese modal UX than it does in English — Japanese users who are unsure what a modal is asking them to do default to closing it; a missing or ambiguous close affordance creates user paralysis at a decision point.
- Why is "OK" a localization failure in Japanese modals?
- A generic "OK" button forces users to recall what they're confirming. Japanese modal buttons should name the consequence (e.g. 削除する / キャンセル), matching the copy's severity to the action's severity.
- Should Japanese modals use formal keigo or teineigo?
- Teineigo (です・ます) is usually sufficient and reads naturally; over-formal keigo can feel stiff. The key is calibrating register to the action — destructive actions warrant more careful, serious phrasing.
- How should modal titles be written in Japanese?
- Lead with the consequence, not the category. A title that states what will happen (and whether it's reversible) helps Japanese users decide, whereas a vague category label leaves them guessing.
Why Japanese Users Read Modals Differently
In English SaaS design, modal dialogs occupy a middle ground between system alerts and inline UI. Users have been trained by years of browser dialog abuse — every site that asked "Leave this page?" — to dismiss modals quickly without reading them carefully. English-language UX research consistently shows that users click through confirmation dialogs rapidly, often without reading the body text.
Japanese business software users behave differently. Modal dialogs in Japanese enterprise contexts carry an implicit social and procedural weight: this is a system asking you to make a decision, and Japanese professional norms treat system prompts as requiring genuine attention before response. A Japanese admin who is not sure what a modal is asking will not guess and click — they will read, and if the copy is unclear, they will close the modal without proceeding. This is not indecision; it is a learned response to a professional environment where making the wrong choice in a system prompt has real consequences.
The practical consequence is that modal copy in Japanese SaaS needs to be clearer and more precise than in English. The investment in clear modal copy is not optional; it is the difference between a Japanese user completing a critical action and abandoning it. For products in free trial periods or during enterprise onboarding, a Japanese user who closes a confusing modal and does not return is a lost activation, not a UX footnote.
Modal Titles: Consequence Over Category
English modal titles tend to name the UI pattern: "Confirm Deletion," "Warning," "Are you sure?", "Changes Saved." These titles work in English because users have enough context from the surrounding product to infer what the modal is about. Japanese users, particularly those less familiar with the product, need the title to carry more informational weight.
The modal title is the first thing Japanese users read, and it determines how they calibrate their attention for the rest of the modal. A title that names the consequence — "このフォルダを削除すると、中のファイルもすべて削除されます" (Deleting this folder will also delete all files inside it) — tells the user immediately what decision they are making and what is at stake. A title that names the pattern — "削除の確認" — tells the user only what type of modal this is, leaving the consequence for the body copy that they may or may not read before clicking.
For simple, low-stakes confirmation modals, a clear question in the title is sufficient: "変更を保存しますか？" (Save changes?). The question format is direct and unambiguous. Japanese users respond well to question-form modal titles because they mirror the conversational register of a colleague asking for confirmation — appropriate for a synchronous decision request, which is what a modal interrupt represents.
Button Labels: Why "OK" Is a Localization Failure
The button pair "OK / Cancel" is the default confirmation dialog pattern in English. It is also one of the most pervasive localization failures in Japanese SaaS. "OK" in a Japanese modal is accepted — it is widely recognized — but it is not a good button label for any action that carries real consequence.
Japanese enterprise software convention for confirmation dialog buttons follows a consistent pattern: the primary action button names the action with a verb, and the secondary button names the cancellation explicitly. 削除する / キャンセル for a delete confirmation. 保存する / 変更を破棄 for an unsaved changes dialog. 送信する / 戻る for a form submission. This pattern has two advantages over OK/Cancel. The primary button tells the user exactly what pressing it will do, eliminating any ambiguity about whether OK means "confirm" or "acknowledge." The secondary button options give Japanese users a precise exit — not just "cancel" (キャンセル, which can sound abrupt) but sometimes "go back" (戻る) or "don't save" (保存しない), which is more linguistically precise about what the dismissal means.
| Modal Type | English Convention | Japanese Enterprise Convention |
|---|---|---|
| Delete confirmation | Delete / Cancel | 削除する / キャンセル |
| Unsaved changes | Save / Discard | 保存する / 保存せずに終了 |
| Send confirmation | Send / Cancel | 送信する / キャンセル |
| Logout confirmation | Log out / Stay | ログアウト / キャンセル |
| Plan upgrade | Upgrade / Not now | アップグレード / 後で |
| Information acknowledged | OK / Close | 閉じる（single button is fine for pure information） |
Register Calibration: Matching Copy Severity to Action Severity
Japanese has a formal register system that maps well onto modal severity levels — but using it requires deliberate choices rather than consistent teineigo (丁寧語) throughout. Modals fall into four broad severity categories, each with different Japanese register expectations.
Informational modals — "Changes saved," "Export complete," "Email sent" — can use lighter, slightly warmer copy. "変更が保存されました。" (Changes have been saved.) Plain statement of fact, no elaboration needed. The desu/masu form maintains politeness without adding unnecessary weight to a routine notification.
Warning modals — "Your trial expires in 3 days," "Storage is nearly full" — require a tone that conveys relevance without alarm. Japanese warning copy uses 注意 (attention/caution) as a heading when the situation needs action but is not critical. "ストレージの空き容量が少なくなっています。" (Storage space is running low.) No exclamation marks, no urgency language, clear statement of the condition and an implicit or explicit path to resolution.
Error modals — "Payment failed," "File upload failed," "Connection error" — require acknowledgment of the problem and a specific recovery path. The error heading (エラー or 処理に失敗しました) signals severity. The body should state what failed, why if known, and what the user should do next — in that order. Japanese error modal copy that only states the error without a recovery path leaves Japanese users uncertain whether to retry, contact support, or wait.
Destructive action confirmations — "Delete account," "Remove all data," "Cancel subscription" — require the most formal and specific copy in the modal. These should use formal compound verb forms (削除されます, 失われます), explicit consequence statements, and in some cases a visual reinforcement of irreversibility (この操作は取り消せません — this action cannot be undone).
エラーが発生しました。
削除してもよろしいですか？
エラー：ファイルのアップロードに失敗しました。もう一度お試しください。
このデータを削除しますか？この操作は取り消せません。
Alert Banners: Severity Without Vocabulary Confusion
Inline alert banners — the yellow, red, or blue bars that appear at the top of a page or within a form — use a different vocabulary set from modal dialogs. Japanese users parse alert severity from both visual cues (color) and vocabulary cues (the Japanese terms used). When vocabulary does not match visual severity level, Japanese users may misread the urgency of an alert.
Japanese alert vocabulary follows a rough severity hierarchy: お知らせ (information, lowest urgency), ご注意 or 注意 (caution, medium urgency), 警告 (warning, higher urgency), エラー (error, highest urgency). Products that use エラー for informational notices, or お知らせ for critical errors, signal to Japanese users that the vocabulary has not been calibrated — which makes them uncertain about the true severity of any alert they encounter. This uncertainty is itself a trust problem: if Japanese users cannot reliably gauge alert severity from vocabulary alone, they compensate by reading every alert more carefully, which takes more time and creates more interruption, or by dismissing all alerts quickly, which means they may miss a genuinely critical one.
Practical note on 警告 vs. エラー: 警告 (warning) is often confused with エラー (error) in translated Japanese SaaS because English uses "warning" and "error" with overlapping meanings in some contexts. In Japanese, 警告 signals a situation requiring attention before proceeding — the action has not yet failed. エラー signals that something has already failed. A payment that declined is an エラー. A credit card about to expire is a 警告. Getting this distinction right in alert copy prevents Japanese users from treating genuine errors as optional notices.
Modal and Dialog QA Checklist for Japanese Localization
Modal titles state the specific object and consequence, not just the action category
Titles like "削除の確認" have been replaced with titles that name the specific object being acted on and pose the decision as a direct question to the user.
Button labels use action-specific Japanese verbs, not "OK"
Every confirmation dialog button names the action it performs (削除する, 保存する, 送信する). "OK" has been replaced with an action verb except in purely informational modals where 閉じる is appropriate.
Destructive action modals include explicit irreversibility statement
Any modal confirming an action that cannot be reversed includes the phrase "この操作は取り消せません" or equivalent, explicitly stating that the action is permanent.
Alert banner vocabulary matches visual severity level
The Japanese vocabulary in alert banners — お知らせ, 注意, 警告, エラー — corresponds to the visual severity indicated by the banner color and icon. Mismatched severity vocabulary has been corrected.
Error modals include recovery path, not only error statement
Every error modal states what failed, provides a reason if known, and tells the user what to do next — retry, contact support, or wait. Modals that only state the error without a recovery path have been revised.
Close button present and labeled appropriately for modal type
Every modal has a clearly visible close affordance. Informational modals use 閉じる. Confirmation modals label the dismissal action specifically (キャンセル, 戻る, 保存せずに終了) rather than a generic ×.
Frequently Asked Questions
Should Japanese modals always use formal keigo or is teineigo sufficient?
Teineigo (丁寧語, desu/masu form) is the correct baseline for all modal copy in B2B SaaS products. Keigo (respectful or humble forms) is not appropriate in UI context and sounds unusual coming from a software system. The distinction that matters is not between teineigo and keigo — it is between the lighter end of teineigo (routine notifications) and the more precise, consequence-explicit form of teineigo used for destructive action confirmations and critical errors. Both are polite; they differ in specificity and structural formality, not in honorific level.
How should I handle modal copy for actions that affect multiple users in a team account?
When a modal describes an action that affects other team members — removing a user, deleting shared data, changing a permission that affects the whole team — Japanese modal copy should explicitly state the scope of impact. "このユーザーをチームから削除すると、そのユーザーはすべてのプロジェクトにアクセスできなくなります。" (Removing this user from the team will revoke their access to all projects.) The impact statement before the confirmation button is a small addition that Japanese admin users particularly appreciate because it helps them assess whether the action requires coordination with other team members before proceeding.
What is the correct Japanese for "Are you sure?" in a modal?
The direct translation "本当によろしいですか？" is grammatically correct and widely used, but it is not the strongest modal title for consequential actions. The word 本当に (really/truly) has a slightly casual, spoken-language quality that can feel out of place in enterprise software. Better alternatives depending on context: "〜を削除しますか？" (a direct question naming the action), "〜を実行してよろしいですか？" (more formal, suitable for irreversible operations), or "〜を確認してください" (please confirm, for review-type modals). Reserve 本当に for situations where the cautionary tone is intentional, such as "本当にアカウントを削除しますか？この操作は取り消せません。"
Should confirmation modals for upgrades or purchases use different copy than functional confirmations?
Yes. Modals that involve financial commitment — upgrading a plan, purchasing add-ons, renewing a subscription — require copy that acknowledges the commercial nature of the action. In Japan, business transactions have a formal weight that functional UI actions do not. Including the specific amount and billing date in the modal body — "プロフェッショナルプランに変更します。月額 ¥15,000（税抜）が次回の請求日（2026年6月1日）に請求されます。" — matches the standard Japanese B2B purchase confirmation register and reduces the rate at which Japanese users abandon upgrade modals due to uncertainty about what they are agreeing to.
How long should a Japanese modal dialog body be?
Japanese modal body copy should be concise but complete. The standard is: one sentence stating the consequence of the action, one sentence stating any irreversibility or significant side effects, and one sentence with the recovery or contact path if an error occurred. Three sentences total for consequential actions. Informational modals can be a single sentence. The common failure mode is translating English modal body copy that was written to be brief — sometimes just one clause — into Japanese, where the same information takes more characters and may read as incomplete without the structural context that Japanese business writing conventions expect.
Related Articles
- Japanese Error Message Localization
- Japanese Settings Page Localization: Destructive Action Confirmations
- Japanese UI Microcopy: The Strings That Define Product Polish
Are your modals earning or losing Japanese user trust?
Modal and dialog copy is reviewed in every Hiraki Localization mini audit — including button labels, severity vocabulary, and confirmation phrasing.
Request a Mini Audit