Insights
Text Expansion by Language: How Much Your Layout Will Grow
By Asiatis · Published 24 August 2026 · Last updated 24 August 2026
Text changes length when it is translated, and the change is large enough to break layouts. English typically expands by 10–35% into most European languages, with German, Finnish, Polish and Greek at the upper end and Dutch and Swedish nearer the middle. Short strings expand far more in percentage terms than long paragraphs — a five-character English button label can double.
The reference table
Expansion is measured against English source text. Figures are typical ranges for running prose; individual segments vary widely.
Click a column header to sort.
| Notes for design | ||
|---|---|---|
| German | +20 to +35% | Worst case in Europe. Compound nouns also produce very long unbreakable words |
| Finnish | +20 to +30% | Agglutinative; long single words, difficult hyphenation |
| Polish | +20 to +30% | Also affects line breaking in narrow columns |
| Hungarian | +15 to +30% | Agglutinative, similar constraints to Finnish |
| Greek | +15 to +25% | Different script; check font coverage and diacritic clipping |
| French | +15 to +25% | Consistent, predictable expansion |
| Spanish | +15 to +25% | Similar to French |
| Portuguese | +15 to +25% | PT-PT slightly longer than PT-BR |
| Italian | +10 to +25% | — |
| Czech | +10 to +25% | Diacritics increase line height in tight layouts |
| Slovak | +10 to +25% | Diacritics increase line height in tight layouts |
| Romanian | +10 to +25% | Diacritics increase line height in tight layouts |
| Croatian | +10 to +25% | Diacritics increase line height in tight layouts |
| Dutch | +10 to +25% | Compound nouns, as in German |
| Estonian | +10 to +25% | Small linguist pool, plan lead time |
| Latvian | +10 to +25% | Small linguist pool, plan lead time |
| Lithuanian | +10 to +25% | Small linguist pool, plan lead time |
| Bulgarian | +10 to +20% | Cyrillic; verify font coverage |
| Swedish | +5 to +20% | Among the most layout-friendly European targets |
| Danish | +5 to +20% | Among the most layout-friendly European targets |
| Norwegian | +5 to +20% | Among the most layout-friendly European targets |
Methodology: typical expansion ranges for running prose vs English, compiled from standard localisation references and Asiatis project experience. Individual segments and subject areas vary; short strings expand far more (see below). Table licensed CC BY 4.0 — reuse with attribution to Asiatis Singapore.
Contraction, for context
Not every language expands. Translating into English from a European language generally contracts by 5–15%, and Asian source languages behave differently again — Chinese and Japanese source text expands substantially in character count when rendered into European languages, because a single character carries more information than a Latin letter. A Chinese product manual will produce a visibly longer German document than its length suggests.
The rule everyone gets wrong: short strings expand most
Expansion percentages published for running text badly understate the problem for interface labels, buttons, table headers and packaging.
| English source length | Expect expansion up to |
|---|---|
| 1–10 characters | +200 to +300% |
| 11–20 characters | +180% |
| 21–30 characters | +160% |
| 31–50 characters | +140% |
| 51–70 characters | +130% |
| Over 70 characters | +130% and falling toward the language average |
The reason is statistical rather than linguistic: a long paragraph averages out across many words, while a single short word has no averaging effect. “OK” and “Save” have no short equivalent in several European languages. This is why a user interface designed to fit English exactly will break in German long before a brochure does.
What actually breaks
Buttons and navigation. Fixed-width buttons truncate. Navigation bars wrap to two lines and push content below the fold.
Table headers. Column widths set for English headers force awkward abbreviations that then differ per language.
Packaging and labels. Physical space is fixed. This is the one case where text cannot expand at all, and where the constraint has to be handled before translation, not after.
Charts and infographics. Legends and axis labels are usually placed manually, so every language becomes a manual rework unless the labels sit outside the graphic.
PowerPoint. Text boxes autofit by shrinking the font, so slides do not visibly break — they silently become unreadable at 9pt.
Line height with diacritics. Czech, Polish, Romanian, Hungarian and Vietnamese stack diacritics above and below. A tight line height that looks elegant in English clips them.
Unbreakable compounds. German and Dutch compound nouns can exceed a narrow column width with no valid break point. Requires soft hyphens in the source or a wider column.
How to design for it
- Budget 35% headroom in any layout intended for European translation, and 200% for individual UI strings under ten characters.
- Pseudo-localise before you translate. Replace source strings with artificially lengthened accented placeholder text and run the build. It exposes truncation, hard-coded strings and clipping in an afternoon, before a single word has been paid for.
- Never centre text vertically in a fixed box unless the box can grow.
- Keep text out of images. Text baked into a graphic means re-exporting the graphic for every language, at design rates rather than translation rates.
- Avoid concatenating strings in software. "Delete" + " " + item name produces broken grammar in inflected languages such as Polish, Czech and Finnish, where the word form changes with case.
- Give translators a character limit per string, not an instruction to "keep it short". A limit is actionable; a request is not.
- Set line height for the worst case, not for English.
- Review in context. A string that fits in a spreadsheet may still be wrong on screen. In-context linguistic review catches what a character count cannot.
Key facts
- English expands 20–35% into German, the largest expansion among major European languages.
- Strings under 10 characters can expand by 200–300% — far more than running prose.
- Nordic languages expand least among European targets, typically 5–20%.
- Translating into English from a European language usually contracts by 5–15%.
- Physical packaging is the only case where expansion cannot be absorbed, so it must be constrained before translation.
- Pseudo-localisation exposes most layout breakage before translation costs are incurred.
Related: labelling and instructions for the EU market, how desktop publishing is quoted, and the European languages we translate into.
Frequently asked questions
How much does English expand when translated into German?+
Typically 20 to 35% for running prose, and considerably more for short strings. German also produces long compound nouns with no valid break point, so a narrow column that works in English can overflow even when the overall expansion is within budget. German is the standard worst case to design against for European markets.
Which European language expands the least?+
The Nordic group — Swedish, Danish and Norwegian — typically expands least, around 5 to 20% from English. If you are testing a layout against a single language and cannot test against all, test against German for the worst case rather than a Nordic language for the best.
Does text expansion affect translation cost?+
Not directly, when the quote is per source word: the price is set by the original document, so the length of the translation does not change it. It affects cost indirectly through desktop publishing, because each language needs its layout rebuilt, and that rework is where expansion turns into money.
How do I plan for expansion in packaging where space is fixed?+
Constrain at the source. Set a character limit per element before the English copy is written, verify it against the longest target language, and treat the limit as a design requirement rather than a translation request. Where a mandatory warning cannot be shortened without changing its regulatory meaning, the layout has to change, not the wording.
Can I just reduce the font size?+
For one language on one page, occasionally. As a strategy, no — it produces inconsistent typography across your language versions, and on safety-critical documentation legibility is a compliance requirement, not an aesthetic preference. Design for the expansion instead.