Insights
Which Languages Does the EU Legally Require?
By Asiatis · Published 24 August 2026 · Last updated 24 August 2026
The European Union has 24 official languages, and EU product legislation almost never names them. Instead, it requires information to be supplied in the language or languages determined by the Member State where the product is made available. Each country then decides. In practice, a product sold in five EU markets needs five complete documentation sets, and the list follows your commercial footprint rather than a fixed rule.
The rule nobody states plainly
Manufacturers preparing for the European market usually look for a list of required languages. There isn’t one, and the absence is structural rather than an oversight.
EU product regulations are written centrally and applied nationally. The typical formulation — used across product safety, machinery and medical device legislation — is that information must be provided in a language determined by the Member State where the product is made available to the user. Brussels sets the obligation; each capital sets the language.
Three consequences follow, and they are the ones that matter operationally:
- Your language list is a function of your distribution plan. Add a country, add a language set. This is a commercial decision with a documentation cost attached, and it is better made with the cost visible.
- There is no “European version”. A single English or multilingual booklet is not a compliance strategy. It is a common one, and it is why documentation is a recurring finding in market surveillance.
- The rules move. Member States notify changes, and reference tables are revised. A language plan built on a reading from two years ago is a risk, not a plan.
Which regulations impose language obligations
General Product Safety Regulation (EU) 2023/988
The baseline for consumer products not covered by more specific legislation. Manufacturers must ensure products carry instructions and safety information in a language easily understood by consumers in each Member State where the product is made available, where that is necessary for safe and intended use. Digital labels such as QR codes may complement physical labelling; they cannot replace it.
Machinery Regulation (EU) 2023/1230 — the 20 January 2027 deadline
This is the change worth planning around now. Regulation (EU) 2023/1230 replaces Machinery Directive 2006/42/EC in full from 20 January 2027, with no transition period and no possibility of falling back on the old rules. Machinery placed on the market before that date stays under the Directive; machinery placed on the market on or after it must comply with the Regulation. There is no overlap window — the placement date determines the regime.
Because it is a Regulation rather than a Directive, it applies directly in every Member State with no national transposition. National rules survive only where the Regulation makes room for them — and language is precisely one of those areas. So the shift to a uniform regime does not centralise language requirements; those remain national.
Every language version now has equal legal standing. The Directive distinguished “original instructions” from “translations”, which gave manufacturers a fallback: the original was authoritative. The Regulation removes the distinction. If a translated manual is unclear, incomplete or wrong, there is no original version to point to.
Digital instructions are permitted, with obligations attached. Instructions may be supplied digitally, but the format must allow the user to print, download and save; the digital version must remain accessible for the product’s expected lifetime and for at least ten years after it is placed on the market; any user may request a free paper copy at purchase and receive it within one month; and for non-professional users, essential safety information must still be supplied on paper.
Medical Device Regulation (EU) 2017/745 and IVDR (EU) 2017/746
Article 10(11) MDR requires manufacturers to ensure that the device is accompanied by the information set out in Section 23 of Annex I — labels and instructions for use — in an official Union language or languages determined by the Member State where the device is made available to the user or patient. Label particulars must be indelible, easily legible and clearly comprehensible to the intended user or patient.
The European Commission maintains a table of national language provisions notified by Member States under the MDR, revised as authorities inform it of changes. Patient- and layperson-facing information must be in the national language. Some Member States accept English for devices intended exclusively for professional use, but this remains a per-country, per-device-type position, not a general permission.
Building a language plan that survives an audit
- Derive the list from the distribution plan. Map every Member State where the product will be placed on the market, including via distributors and online marketplaces. Marketplace sales into a country count.
- Check the requirement per country and per regulation. A company selling both machinery and medical devices into the same country can face different obligations for each. Document the source and the date checked, per country and per product line.
- Separate professional-use from consumer-facing content. Where a Member State permits English for professional users, the exemption normally covers only content that reaches professionals.
- Freeze the source before translating. Every source revision multiplies across every language.
- Build terminology before volume. One termbase per product family, governing manual, declaration, labelling, datasheet and software strings in every language.
- Design for expansion. English expands substantially into German, Finnish and Polish. Flag expansion risk per language before layout is finalised.
- Version-control every language together. When the product changes, every language version changes. Under a regime where all versions carry equal standing, an outdated Danish manual is not a minor inconsistency.
The six most expensive mistakes
- Assuming English is enough. Sometimes true for professional-use products in some countries; never a default; always to be verified per market.
- Softening or shortening a warning to fit a layout. Mandatory safety wording is not editorial content.
- Translating last. Documentation planned as a final step is documentation that will be redone.
- One supplier per language. Fragmented terminology, no shared memory, no consistency across the set.
- Ignoring the declaration of conformity. It carries language obligations set by the destination Member State, and is frequently overlooked because it is short.
- Publishing digital instructions without a maintenance plan. A ten-year accessibility obligation is a hosting and version-control commitment, not a one-off upload.
Key facts
- The EU has 24 official languages; product legislation sets obligations, and Member States determine the languages.
- Regulation (EU) 2023/1230 applies from 20 January 2027, replacing Machinery Directive 2006/42/EC with no transition period.
- The Machinery Regulation removes the distinction between original instructions and translations — every language version carries equal legal standing.
- Digital instructions must remain accessible for the product’s expected lifetime and at least 10 years after placing on the market, with a free paper copy on request at purchase.
- MDR Article 10(11) requires labels and instructions in the official language(s) determined by the Member State where the device is made available.
- A product sold in five EU markets normally needs five complete documentation sets.
Related: EU compliance translation service, the European languages we translate into, what a five-language documentation set costs, how much your layout will grow.
Official sources
- EUR-Lex — Regulation (EU) 2023/1230 (Machinery)
- EUR-Lex — Regulation (EU) 2017/745 (MDR)
- EUR-Lex — Regulation (EU) 2023/988 (GPSR)
- European Commission — national language requirements under the MDR
Official sources accessed 24 August 2026.
Frequently asked questions
Is there a single list of languages required for CE marking?+
No, and this is the most common misunderstanding. CE marking legislation sets the obligation to provide information in a language the user understands, and each Member State determines which language that is. Your list is derived from the countries where the product is placed on the market, so two manufacturers of identical products can have entirely different language obligations.
We already translate into German and French. Is that a reasonable baseline?+
It covers Germany, Austria, France and part of Belgium, and nothing else. It is a starting point for a first market entry, not a European baseline. Adding the Netherlands, Italy, Spain and Poland means four more full documentation sets, and Nordic and Central European markets add more again.
What happens to documentation for machinery already on the market before 2027?+
Machinery placed on the market before 20 January 2027 remains under Machinery Directive 2006/42/EC and does not require re-certification. Machinery placed on the market on or after that date must comply with Regulation (EU) 2023/1230. The placement date determines the regime; there is no period during which you may choose.
Can we use machine translation for compliance documentation?+
Not without qualified human post-editing against the source, and not for safety-critical content at all. Under the Machinery Regulation, where every language version carries equal legal standing, a fluent but incorrect translated warning is a liability with no fallback. Machine translation with full post-editing can be appropriate for supporting documentation with a mature termbase; it is not appropriate for warnings, declarations or labelling.
How many languages should we budget for in year one?+
Budget by market, not by language count. A realistic first-year European entry covers three to five markets, which is three to five documentation sets plus shared terminology setup and per-language desktop publishing. The second year is materially cheaper for the same markets, because translation memory covers most of an updated document.
Who checks that our translations comply?+
No authority pre-approves translations. Compliance is verified after the fact — by market surveillance authorities, by notified bodies reviewing technical files, or in a liability dispute. That is why the process needs an audit trail: who translated, who revised, against which terminology, on which date, from which source version.