English to German Translation
German is the pair that breaks layouts. Word count usually falls when English becomes German, while the space the text occupies grows — often 20 to 35 percent for short strings — because German builds single long compound nouns that cannot be hyphenated at will.
Why does German text overflow when the word count drops?
German replaces multi-word English phrases with one compound noun. Fewer words, more characters, and no valid break point in the middle of the compound. A button or a table column sized to fit English will clip the German, and the usual fix of shortening the text is not always available.
Running prose typically expands 20 to 35 percent in character count. Short strings are worse, because there is no surrounding text to absorb the overflow: a six-character English label routinely becomes a twenty-character German one.
What actually solves it is deciding the rule before translation, not after. Either the interface allows the string to wrap and the container to grow, or the German copy is written to a character budget as a deliberate constraint — which is a copywriting task, not a translation one, and it is priced that way.
- Give UI strings a character limit in the source file if the container is fixed
- Allow two-line wrapping on buttons and navigation labels
- Widen table columns and form labels rather than truncating with an ellipsis
- Test with pseudo-localisation before the real translation arrives
Sie or du in business German?
Default to Sie for anything commercial, legal or technical, and treat du as a deliberate brand decision rather than a default. Some consumer and developer-facing German brands use du successfully, but it has to be consistent across every string, and switching mid-product reads as an error.
This is the single most common thing companies forget to specify, and it cannot be fixed by search and replace — the pronoun choice changes verb forms, possessives and imperatives throughout. We ask for it up front and record it in the glossary so every later file matches.
Does the German market have specific documentation rules?
Yes, and they bite hardest in manufacturing. Under EU Regulation 2023/1230 on machinery, instructions and the declaration of conformity must be supplied in the language required by the member state where the machinery is placed on the market, which makes German documentation a condition of sale, not an extra.
The regulation becomes mandatory in January 2027 and permits digital instructions, with every language version carrying equal legal weight. In practice this raises the bar on terminology consistency: if the German and English manuals disagree about a safety instruction, both versions are still the instruction.
What about Austrian and Swiss German?
Written standard German is largely shared, so one version usually serves all three markets. The differences are specific rather than pervasive: Swiss usage drops the ß entirely in favour of ss, and legal, administrative and food terminology varies by country.
Frequently asked questions
Can you keep German UI strings inside a character limit?
Yes, if you give us the limit per string. Hitting a hard cap in German often means rewriting the label rather than translating it, so we flag the strings where the cap forces a wording change and propose alternatives instead of silently truncating.
How do you keep technical terminology consistent?
With a glossary and a translation memory maintained across your documents. For machinery and equipment work this is not optional — part names and safety wording have to be identical in the manual, the parts catalogue, the interface and the training material.
Do you provide certified German translations?
For official use in Germany, a beglaubigte Übersetzung is issued by a translator sworn before a regional court. Tell us the receiving authority and we confirm whether that is required or a standard certified translation is accepted.
Need English to German translation?
Send the file and any character limits. We flag the strings that will not fit.
Request a quote