A streaming app localizes a simple English tab label: “Watchlist.” The Spanish version, “Lista de seguimiento,” is accurate, natural, and easy to understand. On paper, it looks perfect. But inside the actual mobile navigation bar, the label wraps into two lines, pushes the other tabs out of alignment, and makes the entire bottom menu feel broken.
The translation is correct, but the interface cannot use it.
The same issue happens across many types of localized content. A webtoon speech bubble becomes overcrowded after translation and covers part of the artwork. A subtitle line is so long that viewers cannot read it before the scene changes. A checkout button expands beyond its container. A product card cuts off the most important detail. A push notification loses its meaning because the final words are hidden on the lock screen.
Length problems are frustrating because they often appear after the linguistic work is already finished. The wording may be accurate, the tone may be right, and the terminology may follow the glossary. But once the text appears in the real layout, it becomes too long, too dense, too slow to read, or visually awkward.
That is why Length QA is essential in localization. It checks whether translated text actually fits the space, timing, and format where users will see it. The goal is not only to produce a good translation. The goal is to make sure the translation still works inside the real product, panel, subtitle, button, screen, or notification.
The Quick Answer: The "Expansion Factor"
The primary reason for length issues is that different languages take up different amounts of space to say the same thing. This phenomenon is known as "text expansion" (or contraction).
As a general rule of thumb, when translating from English, you should anticipate expansion factors like these:
German, Russian, Polish: Can expand by 30% or more.
French, Spanish, Italian: Can expand by 15-20%.
Japanese, Chinese, Korean: Can contract significantly in character count, but may require larger font sizes for readability, effectively using similar horizontal space.
If your UI is designed with tight English-sized boxes, you are setting yourself up for failure in almost every other language.
Practical Rules: Designing for Expansion
Preventing length issues requires a proactive approach involving both design and linguistic strategies. You cannot simply react to broken UIs after the fact.
Rule 1: Design with Flexibility in Mind (The 30% Rule)
The most effective solution is to design your UI to accommodate expansion from the start.
Avoid Fixed-Width Containers: Never use hard-coded pixel widths for text boxes, buttons, or menu items. Use relative sizing (like percentages or flexbox in CSS) so containers can expand as needed.
Plan for Multi-Line Text: If a string is likely to be long, design the UI to handle line wraps gracefully. Don't assume everything will fit on one line.
Leave White Space: A good rule of thumb is to leave at least 30% extra white space around English text blocks in your initial design. This provides a buffer for expansion without breaking the layout.
Rule 2: Provide Context to Translators
Translators are often working in spreadsheets with no visibility into where their translations will appear.
Contextual Information: Always provide notes about where the text is used. Is it a button? A title? A tooltip?
Character Limits: If a hard limit exists (e.g., for a database field or a specific UI element), explicitly state the maximum character count in the translation instructions.
Visual Aids: Whenever possible, provide screenshots or access to a live build so translators can see the space constraints themselves. This is a core principle of effective Quality Control for Localization: Catch Errors Before Users Do.
Rule 3: The "Creative Abbreviation" Protocol
Sometimes, expansion is unavoidable, and the UI cannot budge. In these cases, translators must be empowered to use creative abbreviations or concise synonyms.
Define Acceptable Abbreviations: Create a glossary of approved abbreviations for common terms (e.g., "Info." for "Information").
Prioritize Meaning Over Literalism: If a literal translation is too long, encourage translators to rephrase the concept more concisely, even if it means sacrificing some nuance. The goal is usability. This is particularly important in constrained media like webtoons, as explored in LQA for Short Drama, Webtoons, and Web Novels.
Use Icons: Where appropriate, replace text with universally understood icons (e.g., a gear icon instead of the word "Settings").
Examples in Action: The Length Crunch
Let's look at how a simple English string expands across different languages and how to handle it.
Source (EN-US): "Settings" (8 chars)
UI Constraint: A small gear icon button with space for ~10 characters.
German Translation: "Einstellungen" (13 chars) -> Too long.
Solution: Abbreviate to "Einst." or use just the gear icon without text.
French Translation: "Paramètres" (10 chars) -> Fits tightly.
Russian Translation: "Настройки" (9 chars) -> Fits.
Japanese Translation: "設定" (2 chars) -> Fits easily.
The Length QA Checklist for Editors
Before finalizing any localized product, editors must run a dedicated pass focusing solely on length and layout. While this should be part of your comprehensive Localization QA: The Checklist That Prevents Bad Releases, it is worth isolating.
Visual Scan: Scroll through every screen of the localized build. Look for any text that is cut off, truncated with ellipses (...), or overflowing its container.
Button Check: Are all button labels fully visible and centered?
Menu Verification: Do navigation menus wrap correctly without breaking the layout?
Tooltip/Hover Test: Do tooltips display their full text without being cut off by the edge of the screen?
Abbreviation Review: If abbreviations were used, are they clear and understandable to a native speaker?
Conclusion
Length constraints are the physical reality of localization. A translation that doesn't fit is a translation that fails. By designing for expansion, providing context to translators, and empowering them to use creative brevity, you can ensure that your localized product is not just linguistically accurate, but also functionally usable and visually professional.
Is text expansion breaking your localized UI? Download Feels Local and try it on your next project for free. When you’re ready to catch length issues, protect your layout, and improve the user experience across languages, subscribe to Feels Local.
