Text Expansion in Translation: Language Expansion Rates and Layout Risks
You've laid out a clean 12-page brochure. Every text box fits. Then the German translation arrives, and half the headlines overflow, captions spill into the margins, and the call-to-action button reads like a legal clause.
This is text expansion, one of the most common causes of broken multilingual layouts. This article covers what it is, how much room to plan for, and how to design around it before the file goes to translation.
What is text expansion in translation?
Text expansion happens when a translation is longer than its source. Grammar, compound words, longer articles and prepositions, and abbreviations that have to be spelled out all push the length up.
Text can also get shorter. Hebrew usually runs shorter than English, and Chinese and Japanese use far fewer characters. Shorter text brings its own problems: too much white space, loose grids and layouts that look unfinished. Longer text in a fixed frame ends up as overset text, one of the most common issues in translated InDesign files.
Expansion and contraction both need layout work. Longer text overflows its frames; shorter text leaves gaps that make the page look unfinished.
How much does text expand?
The most widely cited figures come from IBM's guidelines for global design, published by the W3C Internationalization Activity. They measure text translated from English into European languages, and they depend on how long the English source is, not on the target language.
| English source | Translation, as % of the source length |
|---|---|
| Up to 10 characters | 200 – 300% |
| 11 – 20 characters | 180 – 200% |
| 21 – 30 characters | 160 – 180% |
| 31 – 50 characters | 140 – 160% |
| 51 – 70 characters | 151 – 170% |
| Over 70 characters | 130% |
Source: IBM, Guidelines to design global solutions, as published by the W3C in "Text size in translation". Figures are for European target languages.
The shorter the source, the bigger the change. A button, a menu item or a column header of up to 10 characters can come out two to three times as long. For running text, plan for about 30% more.
By language: typical ranges for running text
The bars below show how much space running text typically takes on the page compared with English. They are planning values from production work on InDesign files, not research data. Real documents vary with the subject, the translator and the font.
Real-world example: one word on a button
Here is the English word "Settings" as it appears in German, Spanish, Italian and Japanese software, and what each version does to a fixed-width button. Japanese is measured in width, counting each character as two Latin characters, as the W3C does.
German deserves special mention. Its compound nouns are long and break only at a hyphenation point, while an English phrase can wrap between any two words. A narrow column that works in English often fails in German.
Where text expansion breaks your layout
Expansion does the most damage in four places, and each one needs a different fix.
How to design for it from the start
Fixing expansion after translation means doing the same work again for every language. Planning for it in the source layout means doing it once.
If a document is going into 5 or more languages, have a DTP specialist review the InDesign source file before translation begins. One review costs less than fixing the same problems in every target language.
A note on CJK languages
Chinese and Japanese use far fewer characters than English, which leads many people to expect less layout work. Each character is about twice as wide as a Latin letter, though, and the lines need more space between them.
Desktop
Publishing
Services
Latin characters
桌面出版
服务
→ Taller glyphs
→ Fixed frames still overflow
→ Vertical space increases
→ White space needs design adjustment
A paragraph that is narrower in Chinese can still need more height than the English, so fixed-height frames break in CJK too, only in the other direction. Short strings can even come out wider: in a W3C example, the Chinese word for "views" takes 1.2 times the width of the English. Korean, written in Hangul with spaces between words, usually takes about as much width as English. For right-to-left languages like Arabic and Hebrew, text direction, frame mirroring and length change all have to be handled together.
Quick reference: expansion by language group
Use this as a planning reference when scoping multilingual DTP projects. The ranges are typical values for running text, as in the bars above.
| Language group | Typical change | Main layout risk | Buffer to design in |
|---|---|---|---|
| Swedish, Norwegian, Danish | +5 – 15% | Compound words in narrow columns | 20% |
| French, Spanish, Italian | +15 – 25% | Headlines, buttons | 25% |
| Portuguese, Polish, Arabic | +15 – 30% | Text frames, tables; for Arabic also RTL mirroring and line height | 30% |
| German, Dutch, Finnish | +20 – 35% | Narrow columns and long compound nouns | 35 – 40% |
| Hebrew | −10 – −25% | White space, RTL mirroring | Design flexibly; don't rely on tight text fill |
| Chinese, Japanese | −10 – −30% in width | Vertical space, leading, fixed frame heights | Increase frame height; adjust leading separately |
| Korean | About the same width | Vertical space, leading | Increase frame height; adjust leading separately |
These are averages for running text. Short strings such as buttons, labels and headers change far more than paragraphs, and marketing copy tends to grow more than legal or technical text. When in doubt, plan for the top of the range.
The short version
Text expansion is settled at the layout stage, before the translator opens the file. Handled there, it costs a few hours once. Handled after translation, the same hours repeat in every target language.
Plan for about 30% more space for running text in most European languages and more for German, Dutch and Finnish. Allow two to three times the length for single words, and treat Chinese, Japanese and Korean as a question of width and line height. Build that room into your InDesign source file, use flexible frames and consistent paragraph styles, and keep all type live.
A review of the source file catches expansion risks once, before they turn into problems in every language. The first look at your files is free.
Request a free assessment