How do you translate a Safety Data Sheet correctly without changing the chemical risk? Treat the SDS and GHS label as structured hazard communication, not ordinary technical prose. Accurate SDS translation must preserve product identity, hazard classes and categories, signal words, hazard statements, precautionary statements, pictograms, ingredient identities, concentrations, exposure limits, physical properties, transport information, regulatory references and revision control. One changed qualifier or number can make the target document describe a different risk from the source.
People searching for SDS translation, Safety Data Sheet translation, MSDS translation, GHS label translation, hazard statement translation, chemical label translation, multilingual SDS and GHS translation are dealing with a regulated document family. The current UNECE GHS framework addresses harmonised hazard communication through labels and safety data sheets, and the familiar SDS architecture uses a structured 16-section format. Translation therefore has to preserve controlled terminology, structured data and cross-document consistency rather than merely make the wording fluent.
This guide explains how to translate SDSs and GHS labels without changing hazard meaning. It covers section structure, identifiers, classifications, controlled statements, chemical names, numbers, emergency information, exposure data, transport information, regulatory context, label alignment, version control and final QA. The aim is simple: the target-language SDS should communicate the same approved hazard information as the source and remain traceable to the same product and revision.
Why SDS Translation Is a Hazard-Communication Problem
A Safety Data Sheet is not ordinary product copy. It is structured hazard communication. The target version has to preserve the identity of the substance or mixture, the hazard classification, signal words, hazard statements, precautionary statements, composition data, first-aid information, firefighting information, spill response, exposure controls, physical properties, stability, toxicology, ecological information, disposal, transport, regulatory information and revision history. The translator’s job is therefore to keep the same risk picture visible in another language. A fluent sentence that weakens a hazard, changes a concentration range or disconnects a precaution from its hazard is not a stylistic issue; it changes the safety document.
1. Start With the Governing SDS Structure
Modern SDS practice commonly uses a 16-section format, and that structure gives the translation team a control framework. Preserve the section order and headings required by the applicable jurisdiction or organisational standard. Do not merge sections because the content feels repetitive. Do not move transport data into a handling section simply because the target language reads better that way. The structure helps workers, emergency responders, safety professionals and regulators locate information quickly. Treat the section number as a protected identifier and review target headings against the project’s approved terminology before translating the body.
2. Identify the Regulatory Context Before Translating
The Globally Harmonized System provides a common hazard-communication framework, but jurisdictions implement it through their own rules, revisions and local terminology. Record the target market, applicable GHS revision or local implementation, document owner and product version before work begins. Do not assume that a target-language SDS prepared for one country is automatically suitable for another. Regulatory terminology, required phrases, national exposure limits and supplier information can differ. Translation should reproduce the source hazard communication while respecting the target jurisdiction’s approved language and structure, not silently harmonise everything to the translator’s home market.
3. Protect the Product Identifier
The product identifier on the SDS should align with the product label and the organisation’s controlled product naming. Do not translate a trade name as if it were a descriptive noun unless the manufacturer officially localises it. Preserve catalogue numbers, internal codes and model identifiers. If a product has both a commercial name and a chemical description, keep the distinction clear. A user should be able to match the target SDS to the container or shipment without guessing whether two names refer to the same material.
4. Preserve Supplier and Emergency Contact Information
Supplier name, address, telephone number and emergency contact details are factual fields. Translate address elements only according to the organisation’s policy and do not alter phone numbers. If a local emergency number is added for the target market, that is a regulatory or business update, not a linguistic substitution, and should be controlled by the document owner. Check time-zone or availability statements such as “24-hour emergency number” carefully. Contact data should receive a separate final verification because ordinary language review often skips blocks of numbers and addresses.
5. Translate Recommended Use and Restrictions Precisely
Section 1 can include recommended uses and restrictions on use. Preserve the scope. A product intended for industrial use only should not become “professional use” unless the source or regulatory terminology supports that equivalence. “Not recommended for consumer use” is different from “prohibited for consumer use.” These phrases can affect risk management and distribution. Translate the intended-use language by meaning, not by broad category labels, and keep it consistent with labels, technical data sheets and product documentation.
6. Treat Hazard Classification as Controlled Data
Hazard classes, categories and classifications are structured regulatory outputs. Do not paraphrase them for naturalness. If the source says a material is classified in a specific hazard class and category, use the approved target-language classification term and preserve category numbers or letters. Do not infer a different classification from the narrative. The translation team communicates the source classification; it does not recalculate it. Classification changes belong to qualified chemical or regulatory specialists and should be handled as source-content changes, not translation edits.
7. Protect Signal Words
Signal words such as the GHS equivalents of “Danger” and “Warning” can have defined meanings. Use the official target-language wording prescribed by the relevant framework or organisation. Do not soften a signal word to sound polite, and do not intensify it because the hazard feels serious. Signal-word consistency should be checked between the SDS and the label. If the source label and SDS disagree, flag the discrepancy rather than choosing one silently.
8. Preserve Hazard Statement Codes and Meaning
Hazard statements can have standard codes and standardised wording. Protect the code and use the approved target-language phrase where available. Do not rewrite standard wording into a more literary or explanatory sentence inside the formal hazard statement field. If the organisation adds supplementary explanatory text, keep that text visibly separate from the controlled statement. A terminology database should store both the code and the approved target phrase to prevent variation across products.
9. Preserve Precautionary Statement Codes and Meaning
Precautionary statements are similarly controlled. They can address prevention, response, storage and disposal. Preserve codes, sequence and official wording where applicable. Do not combine two statements into one shorter sentence if the official implementation keeps them separate. Do not omit a qualifier such as “if exposed” or “if inhaled.” Translation should maintain the same relationship between hazard and precaution as the source.
10. Keep Pictograms and Text Aligned
Pictograms are visual hazard elements, but they do not make the words optional. Check that the target hazard text, signal word and precautionary statements are consistent with the pictograms present on the label or SDS. A design workflow can accidentally reuse an old pictogram while the text has changed, or vice versa. Translation review should therefore include rendered label artwork, not just extracted strings. The final target package should tell one consistent hazard story across words, codes and symbols.
11. Translate Supplemental Hazard Information Separately
Some labels and SDSs contain supplemental hazard information beyond the core standardised statements. Translate it carefully, but do not make it look like a controlled statement if it is not. Use the project style guide to distinguish standard GHS language from manufacturer-specific safety information. This helps reviewers know which text must match regulatory phrase libraries exactly and which text can be adapted for natural target-language clarity.
12. Preserve Composition and Ingredient Identity
Section 3 can include chemical names, common names, CAS numbers, EC numbers or other identifiers, along with concentration or concentration ranges. Protect identifiers and numbers. Use established target-language chemical nomenclature where required, but do not translate a trade-secret placeholder or internal identifier as though it were a chemical name. Ingredient identity should remain traceable across the SDS, technical specifications and regulatory records.
13. Protect CAS and Other Registry Numbers
Registry numbers are identifiers, not translatable content. Preserve punctuation and digit order. Review them separately because a single transposed digit can point to a different substance. If the source contains several identifiers, keep each attached to the correct ingredient. A bilingual table can help reviewers verify source and target line by line without relying on visual similarity.
14. Preserve Concentration Ranges
Concentration ranges may be expressed as percentages, ranges, less-than values or upper/lower limits. Keep the mathematical relationship intact. “1–5%,” “<1%,” “up to 5%” and “at least 5%” are not interchangeable. Do not localise a decimal separator without checking the target document convention. Numerical QA should include every concentration, exposure limit, temperature, pressure and quantity in the document.
15. Translate First-Aid Measures Without Rewriting Them
Section 4 communicates response information by exposure route or condition. Preserve whether information applies to inhalation, skin contact, eye contact or ingestion. Do not merge routes because the instructions look similar. Do not add treatment advice from outside sources. The translator’s role is to reproduce the source information clearly and consistently. If the source is ambiguous or appears contradictory, raise a query to the document owner or qualified safety reviewer.
16. Preserve Medical-Attention Triggers
Phrases such as “seek medical attention,” “call a poison centre,” “if symptoms persist,” or “immediately” carry timing and conditional meaning. Preserve the trigger and urgency exactly. Do not turn “if symptoms persist” into an unconditional instruction, and do not weaken “immediately.” Target-language urgency should sound natural but should not change the source threshold for action.
17. Translate Firefighting Measures by Information Type
Section 5 can include suitable extinguishing media, unsuitable media, special hazards and protective equipment for firefighters. Preserve those categories. Do not translate a medium name into a broader generic word if the source is specific. Do not infer firefighting techniques. If the source distinguishes hazards arising from combustion products from ordinary product hazards, preserve that distinction. The section should remain easy for a qualified reader to scan quickly.
18. Keep Accidental-Release Information Structured
Section 6 can separate personal precautions, environmental precautions and methods for containment or cleanup. Preserve these headings and relationships. Do not combine them into one narrative paragraph if the structure helps users locate information. Translation should retain conditional limits and role-specific language. Again, do not add operational spill instructions beyond the source; safety decisions belong to the document owner and qualified responders.
19. Preserve Handling and Storage Distinctions
Section 7 often separates precautions for safe handling from conditions for safe storage, including incompatibilities. Keep those functions distinct. “Keep container closed” and “store in a cool place” do different jobs. If the source names incompatible materials, use approved target terminology and maintain the same list. Do not generalise precise storage conditions into vague advice.
20. Translate Exposure Controls as a Technical System
Section 8 can contain occupational exposure limits, engineering controls and personal protective equipment information. Preserve the identity of each limit, unit, averaging period and jurisdiction. A time-weighted average, short-term exposure limit and ceiling value are not interchangeable. Where PPE categories are named, use standard target-language terminology. Do not convert one type of protection into another because the general word sounds similar.
21. Keep Exposure Limits Linked to Their Sources
Exposure-limit tables may include regulatory or advisory sources. Preserve the authority name, value, unit and notation. If an authority name has an official target-language form, use it. If not, retain the official name and explain only when project policy permits. Do not mix limits from different jurisdictions during translation. If the target market requires a local limit update, that is a regulatory-content task separate from translating the source.
22. Preserve PPE Terms Consistently
Respiratory protection, eye protection, gloves, protective clothing and other PPE terms can vary by industry and target language. Build a controlled glossary and match the source specificity. A generic “mask” should not replace a specific respiratory-protection term if the source is precise. Translation should stay within the source level of detail and should not imply a different protection standard.
23. Translate Physical and Chemical Properties as Data
Section 9 is heavily numerical and categorical. Appearance, odour, pH, melting point, boiling point, flash point, vapour pressure, density, solubility and other properties must retain values, units, qualifiers and test conditions. Protect symbols such as greater-than, less-than and approximate markers. Avoid converting units unless the document owner requires it. When localisation changes decimal separators, verify every row after layout.
24. Preserve “Not Available,” “Not Applicable” and “Not Determined” Distinctions
These status phrases can mean different things. “Not applicable” says the field does not apply; “not available” says information is unavailable; “not determined” says the value was not established. Do not translate them all as one generic “N/A.” Where the regulatory system prescribes wording, use it. Status precision matters because readers may interpret missing information differently depending on the phrase.
25. Translate Stability and Reactivity Relationships Carefully
Section 10 can include reactivity, chemical stability, possibility of hazardous reactions, conditions to avoid, incompatible materials and hazardous decomposition products. Preserve which item belongs to which category. Do not move an incompatible material into a condition-to-avoid list or vice versa. Use chemical terminology consistently with the composition and hazard sections.
26. Preserve Toxicological Endpoints
Section 11 may cover routes of exposure, symptoms, acute toxicity, skin and eye effects, sensitisation, mutagenicity, carcinogenicity, reproductive effects, target-organ effects and aspiration hazards, depending on the source framework. Translate endpoint names using approved terminology and do not replace a technical endpoint with a general health word. Preserve evidence qualifiers such as “based on available data” when present.
27. Keep Test Data and Classification Separate
An SDS can contain both numerical test data and a hazard classification. Do not assume one can be recalculated from the other during translation. Keep source data, species or test references, units and classification statements distinct. If a reviewer notices apparent inconsistency, flag it to the chemical or regulatory owner rather than “correcting” the target based on personal interpretation.
28. Translate Ecological Information Consistently
Section 12 can include ecotoxicity, persistence, degradability, bioaccumulative potential and mobility. Use established environmental terminology and preserve numeric endpoints and species references. Do not convert an environmental hazard description into a human-health statement. If the target jurisdiction uses official phrases for aquatic hazard classes, keep them aligned with Section 2 and the label.
29. Preserve Disposal Language Without Inventing Local Advice
Section 13 can describe disposal considerations, but local waste rules vary. Translate the source faithfully and preserve any instruction to follow local or national regulations. Do not insert a disposal method that is not in the source. If the target market requires localisation of disposal guidance, that change should be reviewed by the responsible regulatory or environmental specialist.
30. Translate Transport Information as Regulated Data
Section 14 can include UN number, proper shipping name, transport hazard class, packing group, environmental hazard status and special precautions. Protect codes, class numbers and shipping names. Use official target terminology where required by the applicable transport system. Do not infer transport classification from the product’s general hazard description. Shipping data is regulated information and should be checked against the authoritative source.
31. Preserve UN Numbers and Proper Shipping Names
UN numbers are protected identifiers. Proper shipping names can have controlled regulatory wording. Store both in the glossary or structured termbase. Do not translate a proper shipping name creatively. If an official target-language form exists, use it; otherwise follow the organisation’s regulatory policy. Cross-check Section 14 against shipping labels and dangerous-goods documents if they are part of the same project.
32. Translate Regulatory Information by Jurisdiction
Section 15 can contain laws, inventories or regulatory statuses. Preserve the named jurisdiction and authority. Do not replace a source-country law with a target-country law during translation unless the project explicitly includes regulatory localisation. Translation and regulatory adaptation are different tasks. A bilingual reviewer should be able to see which statements came from the source and which, if any, were added through an authorised localisation process.
33. Protect the Revision Date and Change History
Section 16 commonly includes the preparation or revision date and may include change notes. Preserve dates accurately and follow the target date-format policy. If the SDS is updated, record which source revision the target represents. A translated SDS without clear version control can remain in circulation after the source changes. Keep revision identifiers in filenames, document-control systems and final PDFs where required.
34. Keep SDS and Label Terminology Synchronized
The target label and target SDS should use the same product identifier, signal word, hazard statements and key precautionary terminology where the regulatory framework requires alignment. Build the label and SDS from one controlled terminology source. Do not translate them in separate teams without shared governance. A worker should not see one hazard phrase on the container and a different phrase in Section 2 for the same hazard.
35. Distinguish SDS Translation From SDS Authoring
Translators transfer approved source content. SDS authors or regulatory specialists determine classification, missing data, local legal requirements and hazard statements. Keep responsibilities separate. If a source SDS lacks information required in the target market, do not invent it. Escalate the gap. This division of responsibility protects both accuracy and accountability.
36. Distinguish SDS Translation From Regulatory Localisation
A document can be linguistically translated yet still require target-market regulatory adaptation. Localisation may involve supplier identity, national emergency contacts, local exposure limits, specific regulatory references or prescribed phrasing. Those changes should be authorised, documented and reviewed separately. Do not hide them inside ordinary translation edits, because future reviewers need to know what came from the source and what came from the target-market compliance process.
37. Build an SDS Termbase Around Codes and Concepts
A good SDS glossary stores more than source and target words. Include hazard-statement codes, precautionary-statement codes, hazard classes, signal words, approved synonyms, prohibited variants, product names, ingredient names, PPE terms and section headings. Add context fields and source authority. This prevents translators from making different choices across hundreds of products and allows automated QA to flag deviations.
38. Use Translation Memory With High-Risk Filters
SDSs contain repeated language, so translation memory can save time. But repeated text can be dangerous when a small number or qualifier changes. A near-match that differs only in concentration, temperature, category or code must be reviewed carefully. Configure workflows so high-percentage matches containing numbers, codes or negation still receive active human review. Reuse should accelerate consistency, not create copy-forward mistakes.
39. Protect Negation and Limiting Words
Words such as “not,” “no,” “only,” “unless,” “if,” “avoid,” “except,” “below,” “above,” “at least” and “no more than” can reverse or limit safety meaning. Search for them explicitly during QA. A missing “not” in a compatibility statement or a changed inequality in a property table can create a serious mismatch. These small tokens deserve the same attention as technical terminology.
40. Run a Numerical QA Pass
Extract every number, range, unit, percentage, date, code and identifier from the source and compare it against the target. This includes concentrations, pH, temperatures, flash points, exposure limits, phone numbers, UN numbers and revision dates. Do not rely on visual proofreading alone. Automated checks can help, but a reviewer should confirm context because some numbers legitimately change through authorised localisation.
41. Review Tables After Layout
SDS translation often involves table-heavy formatting. Text expansion can shift a value into the wrong row, wrap a header ambiguously or separate an ingredient from its concentration. Review the rendered PDF or final document, not only the CAT-tool bilingual view. Table alignment is meaning. A correct translation in the wrong cell is incorrect information.
42. Protect Superscripts, Subscripts and Symbols
Chemical formulas, units and scientific notation can contain superscripts, subscripts, Greek letters, degree symbols and special characters. Preserve them during file conversion and font substitution. A missing subscript can change a chemical formula. A lost degree symbol can change a temperature display. Technical typography should be included in final QA.
43. Keep Chemical Names Distinct From Trade Names
A trade name may remain unchanged while the chemical ingredient name follows target-language nomenclature. Do not assume the same translation policy applies to both. Maintain separate fields in the terminology database. This helps users connect the commercial product to its chemical composition without confusing branding and substance identity.
44. Handle Trade-Secret Language Exactly
Some SDSs use trade-secret or confidential-business-information statements in place of full ingredient disclosure where permitted. Translate the legal or regulatory wording exactly and preserve any generic chemical description. Do not attempt to infer the hidden ingredient. Confidentiality language is controlled content, not a puzzle for the translator to solve.
45. Preserve Emergency Information Priority
SDS users may consult the document under time pressure. Keep urgent information easy to locate and do not bury it in long target sentences. Natural target-language phrasing can improve readability, but it should not change content. Section headings, bullets and route-specific first-aid labels should remain visually clear. In high-risk safety communication, document design and translation work together.
46. Translate Labels With Space Constraints Without Weakening Meaning
Chemical labels have limited space. Do not solve text expansion by dropping hazard or precautionary meaning. Use approved standard phrases and authorised abbreviations only. If target-language text cannot fit, the label design should be adjusted or the responsible regulatory team should decide the compliant presentation. The translator should not unilaterally shorten controlled hazard text.
47. Review Right-to-Left and Complex-Script Labels in Final Artwork
For right-to-left or complex scripts, text order, punctuation, numbers and code placement can shift unexpectedly in design software. Hazard codes and product identifiers must remain legible and correctly associated with their statements. Review the final artwork in the target script with a qualified native-language reviewer. Do not assume the exported PDF preserves the order shown in the translation tool.
48. Maintain Product-Family Consistency
Manufacturers may have many related products with similar hazards and ingredients. Create shared terminology and templates, but keep each product’s identity and data distinct. A copy-forward error from one SDS to another can transfer the wrong concentration, emergency number or hazard classification. Product-family workflows should combine reuse with strong product-specific checks.
49. Use a Query Log for Chemical and Regulatory Ambiguity
When the translator encounters an unclear chemical name, contradictory hazard phrase, missing value or unfamiliar regulation, log the query with source location and proposed options. Route it to the appropriate subject-matter or regulatory owner. Keep the answer with the project record so the same question is not resolved differently in another language. Query governance is part of multilingual consistency.
50. Version-Control Target SDSs Across Markets
One source product may have target SDSs for several countries and languages. Track each market, language, source revision, local regulatory adaptation and release date. When the source changes, identify which target versions require update. Avoid replacing one country’s target file with another simply because the language is the same. Regulatory context can differ even within one language.
Worked Example: Signal Word and Hazard Statement
Imagine the source uses a regulated signal word plus a coded hazard statement. The target should use the approved target-language signal word and official equivalent wording for the hazard statement while preserving the code. Do not replace the formal statement with a conversational paraphrase such as “can be harmful” if the controlled statement has a more precise scope. The code, wording and pictogram should be checked together.
Worked Example: Concentration Range
If Section 3 lists an ingredient at 1–5%, the target must preserve the same range. “Up to 5%” is broader and “5%” is a single value. Check decimal separators and percent signs after layout. If the ingredient name changes through official target nomenclature, keep the registry number aligned so reviewers can confirm identity.
Worked Example: Exposure Limit
An exposure table may list a limit with a value, unit, averaging period and authority. Translate the authority name according to policy, preserve the numeric value and keep the averaging period attached. Do not collapse a short-term limit and a time-weighted average into one generic “limit.” Structured tables reduce ambiguity when translated carefully.
Worked Example: Revision Update
A manufacturer updates the source SDS because a hazard classification changes. The target process should identify the affected sections, update the controlled hazard wording, review label alignment and issue a new target revision with the correct date. Do not silently edit the old PDF without version history. Users need to know which version is current.
SDS Translation QA Matrix
Review product identity, supplier contacts, classifications, signal words, hazard and precautionary statements, pictograms, ingredients, registry numbers, concentrations, emergency information, exposure limits, properties, transport data, regulatory references and revision dates separately. Then review final layout and label alignment. A high-risk translation workflow should combine linguistic review, numerical review and qualified technical or regulatory review according to organisational policy.
A Six-Pass SDS Review
Use a structure pass for the 16 sections; a terminology pass for controlled hazard language; a numerical pass for values and identifiers; a cross-document pass for SDS-label consistency; a regulatory-context pass for authorised local adaptations; and a rendered pass for tables, symbols and artwork. Each pass catches a different failure mode. One fluent read-through is not enough for structured safety data.
Common Failure Modes
Common errors include translating trade names inconsistently, weakening a signal word, paraphrasing standard hazard language, dropping a precautionary qualifier, changing a registry number, converting a concentration range into a single value, mixing exposure-limit types, moving data into the wrong SDS section, altering transport information, confusing “not applicable” with “not available,” using an outdated source revision, and fitting label text by deleting required meaning. These failures come from treating an SDS as ordinary prose instead of regulated structured communication.
How AI Can Help
AI can help extract terminology, compare repeated sections, identify inconsistent product names and create checklists. It can draft low-risk narrative passages where organisational policy allows. It should not be trusted to classify chemicals, invent missing SDS data, select regulatory statements or override authoritative target-language phrase libraries. Safety-critical outputs need controlled human and subject-matter review. Use AI as a checking assistant, not as the regulatory owner.
Practice and Transfer
Take a fictional, non-hazardous training SDS template with all 16 section headings and populate it with safe placeholder data. Build a glossary for section headings, product identifiers, standard status terms and units. Translate the document, then run separate checks for numbers, codes, section order and final table alignment. The exercise trains structured-document discipline without requiring anyone to experiment with real hazardous materials.
Authoritative Reference Routes
For formal frameworks, use the current UNECE Globally Harmonized System of Classification and Labelling of Chemicals and the applicable national or organisational implementation. The OSHA Safety Data Sheets brief is also a useful public example of the 16-section SDS structure. Translation teams should verify which authority actually governs the target market before treating any reference wording as controlling.
Frequently Asked Questions
What is SDS translation?
SDS translation transfers structured chemical hazard and safety information into another language while preserving product identity, classification, controlled statements, technical data and document structure.
Is an SDS the same as an MSDS?
Many organisations use SDS as the current term under GHS-aligned systems, while older documents may use MSDS. Follow the terminology of the governing framework and source document.
Should hazard statements be paraphrased?
Not when a regulated or approved standard phrase applies. Use the authorised target wording and preserve associated codes.
Can a translator update a chemical classification?
No. Classification is a technical or regulatory content decision. Translators should flag discrepancies to the responsible specialist.
What should be checked after translation?
All 16 sections, product identity, hazard wording, codes, numbers, units, registry identifiers, label consistency, regulatory context and final rendered layout.
Where This Article Sits in the Translation Architecture
This article owns the chemical-hazard communication lane inside Master Art of Translation. It complements the existing Scientific Names, Chemical Formulas and Laboratory Records owner and the broader “Why Translation Matters in Chemicals” rationale page. It also depends on Terminology, Glossaries and Quality Checks for document-level control.
The Principle to Keep
A Safety Data Sheet translation is correct when the target reader sees the same product, the same hazard classification, the same controlled statements, the same technical values and the same document structure as the source, subject only to authorised target-market localisation. Translate the hazard-communication system, not merely the sentences.