Japanese Push Notification Localization:
Character Limits, Verb Forms, and Why Urgency Language Backfires

▶ 60-Second Slide Summary Prefer the 10-slide version of this article? Tap to read in 60 seconds. View slides →

TL;DR

Japanese push notifications fail not because they are grammatically wrong, but because they import English urgency language, ignore multi-byte character expansion, and apply a verb register that conflicts with the rest of the product. Each Japanese character occupies the same pixel width as two or three Roman characters, which means a 45-character Japanese notification title displays as if it were a 90–135 character English string — truncating silently on most devices. Fixing push notifications requires three separate decisions: character budget, register, and tone — and none of the three transfers automatically from English copy.

Key Takeaways

• Multi-byte character budget — A Japanese push notification title fits roughly 15–20 full-width characters before truncation on iOS, compared to 40–50 Roman characters; body copy has a similar compressed budget.
• Urgency language reads as pressure — Phrases like 「今すぐ！」 and 「急いで」 feel aggressive to Japanese users in a notification context; softer alternatives convert better while maintaining action intent.
• Verb-ending register must match the product — Notification copy that uses a different politeness level than the in-app UI creates an inconsistency Japanese users notice immediately, even if they cannot articulate why.
• Opt-in and opt-out wording carries legal weight — Japanese users read permission prompts carefully; wording that feels coercive suppresses opt-in rates and can trigger complaints under Japan's Act on Protection of Personal Information.
• Personalization tokens require honorific context — Inserting a user's name into a Japanese notification without the correct honorific suffix (様, さん) or with incorrect particle placement produces copy that reads as careless or rude.

Why Push Notifications Are the Hardest Japanese Copy Surface to Get Right

Push notifications sit at the intersection of every constraint that makes Japanese localization difficult. The character budget is tighter than any other UI surface. The copy has to work without surrounding context — a notification title has no adjacent paragraph to soften a poor word choice. The tone has to signal urgency without feeling intrusive, which means calibrating to Japanese norms around unsolicited communication. And the whole thing has to render correctly on iOS and Android, which apply different truncation rules in Japanese.

Most localization teams treat push notifications as a translation afterthought. They hand off a spreadsheet of English strings, receive Japanese translations in return, and ship. The notifications pass a grammar check. They fail in the market. In our QA engagements, open rates for Japanese push notifications at foreign SaaS companies routinely run below what the same companies achieve in English-speaking markets. Most of the gap closes to near parity once push copy is reworked with Japanese-native copywriting and a proper character budget.

The fixes aren't complicated. They require understanding three things that standard translation workflows don't address: how Japanese characters consume screen space, how Japanese users respond to urgency language, and what register consistency means for notification copy specifically.

The Multi-Byte Character Problem: What Truncation Actually Looks Like

Every Japanese character — hiragana, katakana, kanji — is a full-width character. On screen, each one occupies roughly double the horizontal space of a Roman letter. A 20-character Japanese notification title displays at the visual width of a 40-character English title. iOS truncates push notification titles at around 40–50 pixels of text width, which works out to about 15–20 Japanese characters on a standard device before the title is cut with an ellipsis.

Android behavior varies by manufacturer and OS version. But the practical limit on most devices used in Japan (Sharp, Sony, Fujitsu Android variants remain common in corporate contexts) is similarly tight. A notification title that renders as "Your invoice is ready — click to view" in English becomes, in naïve Japanese translation, 「お客様の請求書の準備が完了しました。クリックして...」 — truncated before delivering its core call to action.

The problem compounds in the notification body. Body text truncates earlier than the title, typically after 2–3 lines on lock screen and 1–2 lines in the notification tray. An English body of 120 characters may use 40–45 Japanese characters to convey the same information. The Japanese version then fits the budget naturally, or it balloons to 80+ characters if the translator didn't condense. Translators working from a character count specified in Roman characters consistently exceed the Japanese budget.

Surface	Approx. English character limit	Approx. Japanese character limit	Common failure
Notification title (iOS)	40–50 chars	15–20 chars	CTA truncated before the verb
Notification title (Android)	50–65 chars	18–22 chars	Key noun (product name, amount) cut
Notification body (lock screen)	100–130 chars	35–45 chars	Action context missing entirely
Notification body (tray, expanded)	240+ chars	80–90 chars	Verbose translation; key information buried

The fix is to specify Japanese character limits in full-width character counts. Not byte counts, not Roman character equivalents. Brief your translator with "notification title: maximum 18 full-width characters" and ask for Japanese-first copy, rather than a translation of an English string that was never written with the Japanese budget in mind.

Why Urgency Phrases Backfire with Japanese Users

English push notification copywriting has converged on urgency as a core technique. "Last chance," "Act now," "Don't miss out," "Expires in 3 hours" — these phrases work in English markets because they create perceived scarcity without feeling rude in an opt-in notification context. The psychology translates to Japanese. The specific language that triggers it doesn't.

「今すぐ！」 (right now!), 「急いで」 (hurry), 「お急ぎください」 (please hurry) — these are grammatically standard Japanese but tonally aggressive in a notification context. Japanese B2B users in particular read them as pushy or disrespectful. The same users who would respond to a well-framed deadline notification will unsubscribe from a service that sends notifications perceived as shouting at them.

The distinction matters because urgency itself isn't the problem. The delivery mechanism is. Japanese users respond to deadline framing that respects their agency and positions the action as serving their interest, not the sender's conversion rate. The before/after pairs below show the practical difference.

Notification Title vs. Body: Register Must Match the In-App Voice

Push notifications don't exist in isolation. They're the first interaction a user has after leaving the app. When the notification arrives in a different politeness level than the product UI, Japanese users read the mismatch as a sign that different teams wrote the copy without coordination. That impression chips away at confidence in the product's quality.

The most common mismatch: a product using polite ます-form throughout its UI sends notifications in dictionary form, or vice versa. A product that uses 「〜できます」 in its feature descriptions shouldn't send notifications that say 「〜できる」. The content is identical. The tone isn't, and Japanese readers feel the inconsistency.

The title and body of a push notification also carry different register expectations from each other. The title is closer to a headline — it can be more compact and nominalized. The body is closer to a message and should keep the conversational register of the in-app UI. A common mistake is writing both in the same style, producing a body that feels like a continuation of a headline rather than a complete thought.

Opt-In and Opt-Out Wording: Where Localization Becomes a Legal Issue

Japanese users grant push notification permission at lower rates than Western markets. The main reason is that permission prompts are often translated literally from English, producing wording that feels either vague about what the user is consenting to or misleading about how to decline. Japanese users read permission copy carefully — more carefully, on average, than users in English-speaking markets — and ambiguous opt-in language triggers refusal.

The iOS and Android system permission dialogs can't be modified, but the pre-prompt — the in-app explanation that appears before the system dialog — is fully under the product team's control. This is where most SaaS teams leave significant opt-in rate on the table. A pre-prompt written in Japanese-native copy, explaining specifically what notifications the user will receive and how to turn them off, consistently outperforms a translated English pre-prompt in opt-in rate across the engagements we've reviewed.

Opt-out wording carries additional weight. Under Japan's Act on Regulation of Transmission of Specified Electronic Mail (特定電子メール法) and the Act on Protection of Personal Information (個人情報保護法), product teams have to provide a clear, accessible opt-out mechanism and can't obscure the unsubscribe path. Translated English legal language ("You may opt out at any time from your notification settings") frequently fails to meet the specificity the Japanese regulatory framework expects. Write opt-out instructions in Japanese from the source, not translated from English legal boilerplate.

Personalization Tokens and Japanese Honorifics

Personalized push notifications — those that include the user's name, company name, or specific account data — need special handling in Japanese. The challenge is that Japanese honorific conventions attach to names in ways that depend on context, and most personalization token systems insert the stored value without adjusting surrounding text.

Japanese names in a B2B SaaS context should carry the suffix 様 (sama) in formal notification copy, or さん in slightly less formal contexts. A notification that says 「田中さん、新しいメッセージが届いています」 reads as professional and attentive. A notification that says 「田中、新しいメッセージが届いています」 — without the honorific — reads as abrupt to the point of rudeness in a business context. Most personalization templates insert the raw name without suffix, producing the latter.

Particle placement is the second issue. Japanese sentences require particles (は, が, に, を, の) to mark grammatical relationships, and the correct particle after a name in a notification depends on the sentence structure around it. Inserting a name token into a Japanese sentence template without verifying particle correctness produces grammatically wrong output that no amount of translation QA will catch — because the token value isn't present during translation review.

Personalization pattern	Wrong output	Correct output	Issue
User name (B2B formal)	田中、ご確認ください	田中様、ご確認ください	Missing 様 honorific
User name (B2B semi-formal)	田中さんのレポート	田中さんのレポート ✓	Correct — さん + の is standard
Company name	株式会社〇〇のアカウント	〇〇様のアカウント	Remove 株式会社 from token if suffix follows
Amount variable	¥{{amount}}の請求書	¥{{amount}}の請求書 ✓	Amount variables are format-safe

The practical fix is to test every personalization token combination with a Japanese native reviewer before push notifications go live — and to document the honorific convention in the notification style guide so that future campaigns inherit the correct pattern.

The Push Notification QA Checklist for Japan Builds

Before any push notification template ships to Japanese users, run this audit against the rendered output in a staging environment — not the translation spreadsheet. Many of these issues only appear when the notification renders on an actual device.

Frequently Asked Questions