A shipment of industrial adhesive worth EUR 120,000 has been sitting at Rotterdam customs for two weeks. The reason - the Safety Data Sheet (SDS) was submitted in English, but the Netherlands requires Dutch. While the manufacturer scrambles to find a translator with chemistry expertise, daily container demurrage fees of EUR 150-200 keep piling up. One logistics manager shared on Reddit how a mistranslated H-statement (Hazard Statement) in a safety data sheet into Hungarian got a paint shipment blocked at Budapest customs for three weeks - the losses exceeded the value of the goods themselves.
According to Data Horizon Research, the global SDS management market is valued at $2.7 billion in 2024 with projections to reach $7.9 billion by 2033. And the chemical industry, per analyst estimates, will hit $1.4 trillion by 2035. Every chemical product crossing a border needs an SDS in the importing country’s language. Let’s break down what translation requirements apply in different regions, how to avoid terminology mistakes, and what it costs.
What’s SDS/MSDS and why translation isn’t just “translating text”¶
A Safety Data Sheet (SDS) is a document describing a chemical substance or mixture: what it is, how dangerous it is, how to store it, what to do if it spills or gets on your skin. Before 2015, it was called MSDS (Material Safety Data Sheet) - now the international GHS standard uses the term SDS.
A safety data sheet isn’t a marketing brochure or a technical manual. It’s a regulatory document with legal force. If a warehouse worker gets a chemical burn and the SDS turns out to have an incorrectly translated “First Aid” section - the manufacturer bears full liability.
Under GHS (Globally Harmonized System) requirements developed by the UN, every SDS has a standard structure of 16 mandatory sections:
| # | Section | What it contains | Translation difficulty |
|---|---|---|---|
| 1 | Identification | Product name, manufacturer, emergency phone | Low |
| 2 | Hazard identification | Classification, H- and P-statements, pictograms | High - official translations required |
| 3 | Composition | Chemical composition, CAS numbers, concentrations | Medium - chemical nomenclature |
| 4 | First-aid measures | Actions for contact, ingestion, inhalation | High - medical terminology |
| 5 | Firefighting measures | Extinguishing media, special hazards | Medium |
| 6 | Accidental release | Actions for spills/leaks | Medium |
| 7 | Handling and storage | Storage conditions, incompatibilities | Medium |
| 8 | Exposure controls / PPE | Occupational Exposure Limits (OELs), PPE | High - national standards |
| 9 | Physical and chemical properties | Boiling point, flash point, pH | Low - numerical data |
| 10 | Stability and reactivity | Incompatible materials, decomposition products | High - chemical terminology |
| 11 | Toxicological information | LD50, carcinogenicity, mutagenicity | High - toxicological terminology |
| 12 | Ecological information | Aquatic toxicity, bioaccumulation | Medium |
| 13 | Disposal considerations | Disposal methods, waste codes | Medium - national waste codes |
| 14 | Transport information | UN number, hazard class, packing group | Low - standardized |
| 15 | Regulatory information | Country-specific legislation | High - full localization needed |
| 16 | Other information | Revision date, changes, sources | Low |
As ECHA explains (European Chemicals Agency) in their SDS guidance, “the language used in the safety data sheet shall be simple, clear and precise, avoiding jargon, acronyms and abbreviations.” The paradox is that the document itself is packed with specialized terminology requiring precise translation.
Here’s the key difference from other documents - H-statements (Hazard Statements) and P-statements (Precautionary Statements) have official translations for each EU language. You CANNOT translate them “by meaning” - only the official version is accepted. For example, H302 “Harmful if swallowed” in German must be exactly “Gesundheitsschadlich bei Verschlucken” - not a paraphrase, not a synonym, the exact official wording.
SDS translation requirements by region: who needs what language¶
European Union: REACH + CLP¶
In the EU, SDS requirements are governed by two main regulations:
- REACH (Regulation EC 1907/2006) - regulates SDS format and content, Annex II describes the exact structure
- CLP (Regulation EC 1272/2008) - defines classification and labelling criteria
Article 31(5) of REACH explicitly requires: the safety data sheet must be provided in the official language(s) of the Member State where the substance or mixture is placed on the market. As ECHA notes, each country can set additional requirements.
Here’s what that means in practice:
| Country | SDS language requirement | Notes |
|---|---|---|
| Germany | German | German only, English not accepted |
| France | French | French only |
| Spain | Spanish (Castilian) | Catalan, Basque - by regional requirement |
| Italy | Italian | Italian only |
| Netherlands | Dutch | English sometimes accepted for B2B |
| Belgium | French + Dutch + German | Depends on region: Flanders, Wallonia, Brussels |
| Finland | Finnish + Swedish | Both official languages |
| Luxembourg | French, German, or Luxembourgish | In practice usually French or German |
| Poland | Polish | Polish only |
| Czech Republic | Czech | Czech only |
| Greece | Greek | Greek only |
For a company exporting chemical products to 10 EU countries, that means 10 (and sometimes 12-15) language versions of a single SDS. Multiply by number of products - and that’s why the SDS translation market is so large.
As MSDS-Europe emphasizes, the exposure scenario that’s part of an extended SDS (eSDS) is subject to the same language requirements - meaning it also needs translation.
Heads up: from May 1, 2026, new hazard classes for mixtures take effect in the EU (ED, PBT, vPvB, and others). If you’re translating an SDS, make sure you’re using the updated classification per the CLP Regulation, not the old version.
USA: OSHA HCS¶
In the US, SDS requirements are governed by OSHA’s Hazard Communication Standard (HCS), aligned with GHS. The SDS must be in English. But here’s the catch - if workers on site don’t read English (which is very common in the US chemical industry), the employer is obligated to provide access to information in a language they understand. In practice, large manufacturers often translate SDSs into Spanish as the second most common language.
For US imports, SDS doesn’t require certified translation, but it must conform to the OSHA HCS format - 16 sections in the correct order with correct terminology.
United Kingdom: GB CLP post-Brexit¶
After Brexit, the UK implemented its own GB CLP Regulation, based on EU CLP but with its own nuances. SDS must be in English. If you were previously using an EU SDS in English for the UK market - check whether it meets GB CLP requirements, since references to EU regulations may no longer be valid.
Asia: varying levels of GHS adoption¶
As Lingua Technologies International notes, Asian countries have very different requirements:
| Country | SDS language | Specifics |
|---|---|---|
| China | Chinese (simplified) | GB/T 16483 - own format, significantly different from EU |
| Japan | Japanese | JIS Z 7253 - GHS with Japanese specifics |
| South Korea | Korean | KOSHA - mandatory registration + SDS in Korean |
| Taiwan | Chinese (traditional) | CNS 15030 - differs from mainland China |
| Vietnam | Vietnamese | Labeling in Vietnamese + SDS in original or English |
| Singapore | English | SS 586 - if SDS in another language, English translation needed |
| India | English or Hindi | In practice, English is accepted |
What makes SDS translation hard: terminology, phrases, nomenclature¶
Translating a safety data sheet isn’t a case where you can open DeepL and get a ready result. Here’s why.
H- and P-statements: official translations only¶
The most critical element of an SDS is the Hazard Statements (H-statements) and Precautionary Statements (P-statements). As profpereklad.ua explains, these phrases have official translations approved for each EU language, and a translator has NO right to rephrase them.
Example: H301 “Toxic if swallowed”: - German: “Giftig bei Verschlucken” (official) - French: “Toxique en cas d’ingestion” (official) - NOT acceptable: any paraphrase, synonym, or “creative” translation
IUPAC chemical nomenclature¶
Chemical substance names follow IUPAC (International Union of Pure and Applied Chemistry) rules. For example, “sodium hypochlorite” has specific translations in each language following IUPAC conventions. CAS numbers remain the same in any language - they’re your anchor for verifying the correct translation of substance names.
National standards in Section 8¶
Section 8 (Exposure controls / Personal protection) is the hardest to translate because it contains Occupational Exposure Limits (OELs) that differ by country. For example, the OEL for toluene: - EU: 50 ppm (IOELV) - Germany (AGS): 50 ppm - USA (OSHA PEL): 200 ppm - UK: 50 ppm (WEL)
The translator doesn’t just translate text - they need to insert the correct national standards for the destination country.
Section 15: full localization¶
Section 15 (Regulatory information) isn’t really “translated” at all - it’s rewritten for the target country’s legislation. For the EU, it references REACH and CLP; for the US, TSCA and state regulations; for South Korea, K-REACH.
As Eurideas warns, even a minor error in an SDS can lead to “regulatory non-compliance, delayed product launches, or serious legal liability.”
Common SDS translation mistakes and their consequences¶
According to a study, analysis of over 650 safety data sheets found that 30% contained inaccurate chemical hazard warnings. Here are the most common translation-specific errors:
1. Freelance translation of H/P-statements¶
As Lengua Translations writes:
One of the most frequent mistakes is assuming that SDS translation is comparable to general technical documentation. In reality, SDS texts follow strict legal, regulatory, and linguistic conventions that differ significantly from standard manuals or specifications.
In plain terms: the translator approaches the SDS like regular technical documentation and translates H-statements “by meaning” instead of using the official translation. Result - the SDS fails regulatory review.
2. Using outdated classification¶
An SDS translated 3 years ago might use old DSD/DPD classification (Directive 67/548/EEC) instead of current CLP. Or H-statements from an old GHS revision instead of the current one. Since January 1, 2023, all SDSs in the EU must comply with the updated requirements of Regulation 2020/878.
3. Incorrect units and OELs¶
The translator leaves OELs from the source document instead of inserting the destination country’s limits. Or confuses ppm with mg/m³ (these are different units for different substances - the conversion factor depends on molecular weight).
4. Ignoring Section 15¶
Section 15 is often “translated” literally, keeping references to the source country’s legislation. But if an SDS for the French market references American TSCA instead of REACH - that’s a direct violation.
5. Machine translation without review¶
One of the most dangerous approaches - running an SDS through Google Translate or DeepL and submitting it as a finished document. AI translators can confuse chemical names (acid vs acidity), translate brand names, and don’t know official H/P-statements. As x-doc.ai notes, even specialized AI tools for SDS need human verification.
Pro tip: if you’re a translator taking on SDS work - always verify H/P-statements against the official ECHA database. CAS number + official statement translation = minimum insurance against errors.
How much does SDS translation cost and what affects the price¶
Safety data sheet translation is a specialized service, and prices are higher than for regular technical translation.
Approximate 2027 prices¶
| Service | Price | Notes |
|---|---|---|
| SDS translation (1 language, standard) | EUR 80-200 | 10-16 pages, depends on language pair |
| SDS translation (1 language, with Section 8 & 15 localization) | EUR 150-350 | Includes OEL adaptation and regulatory references |
| Translation + chemistry editor review | EUR 200-450 | Recommended for hazardous substances |
| Package 10+ languages (for EU) | EUR 1,200-3,500 | 20-30% savings vs. individual |
| Update of existing translation (revision) | EUR 40-100 | After classification or formula change |
According to translation agencies, typical SDS translation rates run from $0.12 to $0.25 per word, depending on language pair and complexity. Rare language pairs (Korean, Japanese, Arabic) cost 30-50% more than European ones.
For comparison: the average rate for technical translation in Europe in 2025 is EUR 0.08-0.18 per word. SDS translation costs 20-40% more due to the chemistry expertise requirement.
What affects pricing¶
- Language pair: EN→DE costs less than EN→Japanese or EN→Korean
- Number of products: many SDSs from one manufacturer share similar structure - TM (Translation Memory) reduces pricing by 30-50% for subsequent documents
- Review level: basic translation vs. translation + chemistry editor vs. translation + regulatory review
- Urgency: standard 5-7 business days, rush (1-2 days) - +50-100%
- Section 8 & 15 localization: if OEL and regulatory reference adaptation is needed - that’s extra work
If you’ve got dozens or hundreds of products and need translation into multiple languages - look for an agency with specific experience in chemical documentation that uses CAT tools with terminology databases for H/P-statements.
Who can translate SDS: translator requirements¶
Unlike legal documents, an SDS doesn’t require a sworn (beeidigter Übersetzer) or notarized translation. But that doesn’t mean any translator can handle it.
Minimum requirements¶
- Chemical terminology knowledge in both languages - IUPAC substance names, GHS classification, units of measurement
- Regulatory framework knowledge for the target country - REACH/CLP for the EU, HCS for the US, the relevant national standard for Asia
- Access to official H/P-statement translations - ECHA databases, national CLP annexes
- CAT tool experience - Translation Memory for SDS is critical because up to 40% of text repeats between products from the same manufacturer
Who typically translates SDS¶
- Specialized agencies (MSDS-Europe, Nexreg, GTS Translation) - have chemistry editors on staff, terminology databases, regulatory compliance experience
- Freelancers with chemistry degrees - translators with a chemistry or pharmacy background specializing in technical documentation
- Regulatory consultants - companies offering full regulatory compliance services, including SDS translation as part of the package
As The SDS Factory notes, the ideal SDS translator is someone who understands the language, the chemistry, and the regulatory requirements of the target country. Finding such a person for rare language pairs (say, Ukrainian→Korean) is a quest in itself.
If you’re a translator looking to specialize in SDS - it’s a profitable niche with a high barrier to entry. Start by studying GHS structure, official H/P-statements for your language pair, and take at least a basic chemical safety course. We covered more about choosing a specialization in our article on finding your translation niche.
How to organize SDS translation for a large product portfolio¶
If you’ve got 50 products and need translation into 10 EU languages - that’s 500 documents. Without a systematic approach, it’s chaos. Here’s how to avoid it.
Step 1: Create a master SDS in English¶
The English version is your gold standard from which all other languages are translated. Make sure it complies with current REACH Annex II requirements (Regulation 2020/878).
Step 2: Build your Translation Memory (TM)¶
CAT tools (we covered them in our Trados, MemoQ, and Smartcat comparison) let you store previously translated segments. For SDS this is critical - standard phrases in sections 1, 5, 6, 7, 14 repeat at 60-80% between products from the same manufacturer.
Step 3: Create a terminology database¶
A separate glossary with H/P-statements, IUPAC substance names, and units of measurement for each target language. More on this in our article on terminology management for translators.
Step 4: Isolate localized sections¶
Sections 8 and 15 need a separate approach for each country. Create templates with national OELs and regulatory references for each market.
Step 5: Establish a revision process¶
SDSs need updating when: substance classification changes, destination country OELs change, the product formula changes, or new scientific data emerges. The EU recommended review period is every 5 years, but in practice changes happen more frequently.
AI and machine translation for SDS: can you or can’t you?¶
Short answer - you can use AI as a first draft, but submitting such a translation to a regulator without human review by a chemistry editor is a no-go.
As x-doc.ai notes, even specialized AI tools for SDS translation have limitations: they may not know current official H/P-statement translations, can confuse chemical nomenclature across countries, and don’t account for national standards in sections 8 and 15.
Where AI actually helps: - First drafts for standard sections (1, 5, 6, 7, 9, 14) - Checking terminology consistency across documents - Comparing SDS versions after revisions
Where AI is dangerous without human oversight: - H/P-statements (exact official translations needed) - IUPAC chemical names (AI may “normalize” or simplify) - Sections 8 and 15 (require knowledge of national legislation)
If you’re a buyer looking to save money - ChatsControl can help with first drafts of standard sections, but for full SDS translation with regulatory compliance you need a specialist with chemistry training.
FAQ¶
Do I need a sworn or notarized translation for an SDS?¶
No, a safety data sheet doesn’t require sworn or notarized translation. But the translation must be done by a competent person with knowledge of chemical terminology and the target country’s regulatory requirements. Responsibility for SDS accuracy lies with the manufacturer or importer, not the translator.
How many language versions of an SDS do I need for selling chemicals in the EU?¶
As many as the EU countries you’re selling to. Each country requires an SDS in its official language(s). For full EU/EEA coverage - that’s at least 24 languages. In practice, most companies start with the 5-10 largest markets (Germany, France, Spain, Italy, Poland, Netherlands) and add languages as they expand.
Can I use Google Translate or DeepL for SDS translation?¶
As a rough draft for internal use - sure, but submitting machine translation as an official SDS for regulatory purposes - no. H- and P-statements have official translations that machine translation may not reproduce accurately. An error in an SDS means a potential fine and your product getting blocked at customs.
How often do I need to update SDS translations?¶
Every time the source SDS changes (new classification, formula change, new scientific data), and also when the destination country’s national standards change (e.g., new OELs). The minimum EU review period is 5 years, but in practice updates happen more frequently, especially now with new CLP hazard classes being introduced.
What’s the liability for an SDS translation error?¶
Under REACH, liability for SDS accuracy sits with the manufacturer, importer, or downstream user who placed the product on the market. The translator bears contractual liability to their client, but ultimate liability to the regulator falls on the company. Fines for SDS non-compliance in the EU range from several thousand to hundreds of thousands of euros depending on the country and severity of the violation.