


TL;DR: The FDA expects accurate English-language pharmaceutical submissions. Foreign-language materials may need complete translations and signed statements, depending on the application. Missing information or incorrect terminology can complicate review.
FDA pharmaceutical translation involves more than replacing foreign words with English ones. An overseas laboratory may have produced years of research, but the FDA needs to understand the evidence as submitted. A misplaced decimal or a misunderstood test result can create questions that never existed in the original.
FDA submission translation requirements depend on the application and the documents involved. A clinical report isn’t handled exactly like a patient leaflet, and a manufacturing record may have different obligations from an NDA attachment.

English is the working language for FDA drug applications, although precise rules vary by submission pathway. In particular, 21 CFR 314.50(g)(2) addresses foreign-language materials in NDAs.
Foreign-language material included in an NDA needs an accurate, complete English translation. This does not mean translating every foreign record a company owns. It means translating material that forms part of the application under the applicable rule.
The NDA regulation calls for the original foreign-language material and an English translation. Keeping the documents together also makes it easier to resolve questions about scientific terminology.
A translator cannot quietly simplify a difficult result or omit a qualification. The NDA rule also requires a brief statement of the translator’s qualifications and a signed statement that the translation is accurate and complete.

A submission may combine records from laboratories and manufacturing facilities around the world. Which records need translation depends on their role in the application.
NDA translation services can cover foreign clinical reports and research supporting a new drug application. ANDA translation may involve overseas analytical or manufacturing documents for a proposed generic product. The two pathways serve different purposes, so their supporting files are not interchangeable.
IND translation requirements become relevant when a sponsor relies on foreign-language research. Earlier toxicology results, for example, may need English presentation. Later amendments can introduce new material that needs the same attention.
A protocol tells researchers how to run a study. A consent form speaks to participants who may know nothing about medical research. Clinical trial translation FDA planning should distinguish regulatory documents from patient-facing material, which must be understandable to participants.
Foreign GLP study reports included in an application may require translation. GMP records can also require language assistance for submissions or inspections. A translator needs to understand the procedure before choosing the English technical term.
Drug labeling translation must account for U.S. labeling rules. Translating a leaflet approved overseas does not automatically produce a label that is acceptable for the U.S. market.
These records contain exact values and specialized instructions. If translation is needed, the English version must preserve the original procedure and measurements, including details tucked into tables.
A safety report may originate with a clinician abroad. Pharmaceutical regulatory translation must preserve the reaction described without adding a diagnosis or changing the seriousness of the event.
The FDA does not impose one identical certification procedure on every drug document. For NDA foreign-language materials, 21 CFR 314.50(g)(2) is the key provision. A certified translation for FDA submission must follow the requirements of the specific application, since the FDA doesn’t use the same certification rules for every pharmaceutical document.
The NDA provision requires a signed accuracy-and-completeness statement. Including a date is sensible for document control, although that provision does not expressly demand one.
The regulation requires a brief description of qualifications. Recording the translator’s name and contact details helps trace the work, but a mailing address is not expressly required by that particular provision.
The translator certifies fidelity to the source, not the validity of the underlying research. A signed statement should identify the document it covers and confirm the translation is accurate and complete.
Putting the statement directly before the translation is a useful organizational choice, not a prescribed placement under 21 CFR 314.50(g)(2). Follow the submission’s electronic filing instructions.
That NDA provision requires a signed statement, not notarization. Where the rule applies, the statement must be provided with the submission, rather than left solely in the translator’s internal files.

A medicine sold in the United States needs labeling that follows American regulations. Translating the packaging from another country doesn’t automatically make it acceptable for the U.S. market.
Under 21 CFR Part 201, the FDA regulates the information that appears on drug labels. The rules cover much more than the words printed on the front of a box.
English is generally required for U.S. drug labeling, although FDA regulations allow certain exceptions and additional foreign-language labeling under specified conditions.
For a manufacturer entering the American market, this means checking the entire package rather than translating only the product name and directions.
A medicine imported from Italy, for example, cannot simply keep its Italian instructions and assume the packaging is suitable for U.S. distribution.
A warning that tells patients not to take a medicine under certain conditions cannot become a gentle suggestion in English.
The same applies to instructions about dosage. If the original document limits how frequently a medicine may be taken, the translation must preserve that restriction.
A translator should also flag any source wording that appears unclear instead of quietly rewriting the medical instructions.
Under the Federal Food, Drug, and Cosmetic Act, drug labeling can be considered misbranded if it is false or misleading.
Imagine a foreign package describing a medicine as suitable for relieving a particular symptom. During translation, the wording becomes a broader claim about treating the underlying disease.
That change could create a regulatory problem because the English labeling now makes a claim the original did not.
The Physician Labeling Rule, or PLR, establishes content and formatting requirements for prescribing information covered by the rule.
This includes organized sections for information such as warnings, dosage, and adverse reactions.
A translator working on prescribing information must therefore consider the required U.S. format, not simply reproduce the layout used by a foreign regulator. Other applicable labeling rules, including the Pregnancy and Lactation Labeling Rule, may also need attention.
A generic drug’s labeling generally needs to be the same as that of its reference listed drug, apart from differences permitted by regulation.
This matters when translating labeling originally prepared for another market.
The foreign wording may describe the same active ingredient but use different instructions or indications. A manufacturer cannot assume those differences will be acceptable in the United States.
The U.S. reference labeling and applicable exceptions need to be checked before finalizing the generic product’s text.

Clinical trials can involve researchers and patients who speak completely different languages. The FDA may need English documentation, while participants need information they can actually understand.
Those two needs have to be handled separately. Giving the FDA an English document doesn’t mean a Spanish-speaking participant has received understandable consent information.
Under 21 CFR 50.20, informed consent information must be presented in language understandable to the participant or their legally authorized representative.
For a Spanish-speaking participant who doesn’t understand English, handing over an English consent form won’t satisfy that principle.
FDA guidance discusses using accurately translated consent documents and an approved short-form process in appropriate circumstances. The important part is that the participant understands the study before agreeing to take part.
A clinical site may use an approved Portuguese consent form with participants in Brazil while maintaining English study documentation for the sponsor and FDA.
Keeping the relevant versions organized allows reviewers to see what information participants received.
It also helps when consent language changes during the trial. The sponsor needs to know which version was approved and used at each stage.
Recruitment advertisements are often the first information potential participants see about a clinical trial.
A poorly translated advertisement could make a study sound easier or more beneficial than it really is.
When recruitment materials are prepared for non-English speakers, they should accurately reflect the approved information and undergo the appropriate institutional review board review.
Foreign clinical studies may provide evidence supporting a U.S. drug application. Their reports can contain valuable information, but the FDA needs to be able to review that information in English.
For an IND, the applicable regulation expressly requires signed certification of the English translation. Other submission types have their own requirements.
Clinical trial translation FDA work should therefore begin by identifying the application type rather than assuming that every foreign study report needs an identical certificate.
An investigator brochure may contain information about a drug’s known effects and potential risks. A protocol describes the study procedures.
If those documents are submitted to the FDA in a language other than English, applicable translation requirements must be followed.
A mistranslated eligibility condition can be particularly troublesome. It could change which patients appear qualified to enter the study, even though the original protocol says something different.
The Common Technical Document, or CTD, organizes pharmaceutical submission information into five modules.
For companies preparing U.S. submissions from foreign regulatory files, the CTD structure helps determine where translated material belongs. It doesn’t eliminate the need to check FDA-specific requirements.
Module 1 contains region-specific information, including administrative documents and labeling.
For an FDA submission, the relevant material needs to satisfy U.S. requirements. A company submitting the same drug in Japan or Europe may need different local-language versions for those markets.
A translation prepared for one regulator shouldn’t be reused automatically for another without checking the content and format.
Modules 2 through 5 contain summaries and detailed quality, nonclinical, and clinical information.
For FDA submissions, these materials are generally prepared in English. Foreign-language supporting documents included in the application may need translation under the applicable rules.
A company with an existing foreign dossier can save time by identifying the documents that need translation before assigning the entire package.
A foreign clinical study report submitted as part of an NDA cannot be reduced to an English summary when the applicable requirement calls for a complete translation.
That includes relevant supporting information, not just the pages describing the main results.
If a report contains tables showing adverse reactions, those tables matter just as much as the discussion that follows them.
A drug substance may appear in several CTD modules. Its name, strength, and technical descriptions need to remain consistent.
If one translated report uses a different term from the quality documentation, reviewers may have to determine whether the documents refer to the same material.
A shared terminology glossary can prevent these disagreements from reaching the submission stage.
Some translation problems are difficult to spot because the English sounds perfectly reasonable. Others are ordinary document-handling mistakes.
Neither type is welcome when a company has spent months preparing an application.
A translator receives a 70-page report but only translates the main body. The annexes remain in German because nobody noticed they were attached to a separate file.
The English document looks finished until someone checks the source.
Before translation begins, the project team should identify every page that belongs to the material being submitted.
For an IND, a missing signed translator certification can leave the submission without documentation expressly required by 21 CFR 312.23(c).
The translation itself may be accurate, but that doesn’t replace the required statement.
A final document check should confirm whether certification applies and whether it has been included.
A pharmaceutical ingredient might have several names, including a chemical name and an established nonproprietary name.
If translators use different terms without checking whether they refer to the same substance, the English documents can become confusing.
A terminology glossary helps everyone working on the application follow the same naming conventions.
A decimal point is easy to overlook. So is a date written in a different national format.
In pharmaceutical documents, these small details can change the meaning of a study result or manufacturing instruction.
Numerical information should be checked against the original, especially when tables have been recreated or reformatted.
For NDA materials covered by 21 CFR 314.50(g)(2), the original foreign-language information must accompany the English translation.
Submitting only the English version can leave the application incomplete.
The safest approach is to check the document requirements for the particular submission before assembling the final package.
Machine translation can help someone understand the general subject of a foreign document. That doesn’t make its output suitable for an FDA application.
A machine might misread a technical abbreviation or produce an English sentence that changes the meaning of a safety finding.
When certification is required, the appropriate signed statement must also accompany the translation. Human review is important even when the regulation doesn’t prescribe a particular certification format.
Good quality control begins before anyone translates the first sentence. The team needs to know what kind of document they’re handling and how it will be used.
FDA-compliant translation services should be organized around the applicable submission requirements rather than a promise that one certificate makes every document acceptable.
A general translator might understand the ordinary meaning of a word but miss its specialized pharmaceutical use.
Take the word assay. In a laboratory report, it has a technical meaning that depends on the testing context.
A translator with pharmaceutical experience is better equipped to recognize that distinction and use the terminology appropriate to the document.
After translation, a second qualified linguist can compare the English with the original.
This review is particularly valuable for long reports where repeated terminology and numerical data make mistakes easy to overlook.
The reviewer shouldn’t simply polish the English. The job is to determine whether it accurately represents the source.
Every dosage value deserves attention, even when it appears several times in the same document.
The same goes for specifications and analytical results.
If the original describes a concentration of 0.25%, the translated document must not accidentally change it to 2.5%. A dedicated numerical check can catch errors that ordinary proofreading misses.
A translated report may be accurate but difficult to use if the tables are broken or footnotes have disappeared.
Formatting becomes particularly important with scanned records and documents containing complex diagrams.
Reviewers should be able to locate the same information in the English version without searching through pages of misplaced text.
Before submission, the regulatory team should confirm that the translated material belongs in the correct application section and meets the applicable documentation requirements.
The linguistic reviewer checks the translation itself.
These are different responsibilities. A well-translated document can still be filed incorrectly, while a properly organized submission can contain translation mistakes.
A medicine approved for sale in another country doesn’t automatically meet FDA requirements.
Before bringing a foreign-manufactured drug into the United States, the importer needs to establish the product’s regulatory status and whether its labeling and supporting documentation meet U.S. requirements.
A manufacturer cannot simply translate a foreign package into English and start selling the medicine in the United States.
The product must meet applicable FDA requirements, including those governing labeling and marketing authorization.
Even if the drug has the same active ingredient as a product sold in the United States, the foreign package may contain claims or instructions that aren’t appropriate for the American market.
A manufacturer in Germany may maintain its batch production records in German. That doesn’t automatically mean every record must be translated before the drug can enter the United States.
However, when those records are required for an FDA submission or requested during an inspection, the manufacturer needs to make the information accessible for review.
The translation should preserve the original manufacturing information, including handwritten corrections and recorded test results.
A company seeking FDA approval through an NDA, ANDA, or Biologics License Application (BLA) generally needs to prepare its submission in English.
Foreign-language supporting material must be handled according to the requirements applicable to that application.
For companies already selling products internationally, this often means reviewing existing regulatory documents before deciding which ones can be adapted for the FDA submission.
Some over-the-counter medicines can be marketed without an individual approved NDA when they comply with an applicable OTC monograph and other legal requirements.
That doesn’t give manufacturers permission to reuse foreign packaging without checking it.
The Drug Facts label must follow the relevant U.S. requirements, including the appropriate presentation of directions and warnings.
The Language Doctors helps pharmaceutical companies prepare English translations of foreign-language documents used in U.S. regulatory work.
A Japanese laboratory report and a French manufacturing procedure present different translation challenges. TLD can help companies address those differences while keeping the documents organized for regulatory review.

TLD provides certified translation services for pharmaceutical documents, including technical reports and regulatory supporting materials.
The certification can be prepared according to the requirements of the particular project.
For FDA submissions, the appropriate format depends on the application type, so the regulatory team should identify any specific certification requirements before the translation begins.
A translator working on a pharmaceutical study needs more than fluency in two languages.
TLD can help match projects with linguists who have relevant life sciences expertise. Where specialized credentials such as a PharmD or PhD are required, clients should confirm the qualifications available for their particular assignment.
This is especially important for documents involving complex pharmacology or laboratory methods.
A drug’s name or technical description may appear throughout hundreds of pages.
If different translators work on separate sections, terminology can drift unless everyone follows the same references.
TLD uses terminology management to help maintain consistent wording across related pharmaceutical documents.
A translation may look finished long before it’s ready for submission.
TLD can support a review process in which the translated document is compared with the original and checked for missing information.
Regulatory compliance still requires confirmation by the sponsor’s regulatory specialists, who determine whether the documents meet the requirements of the specific FDA application.
A translation request sometimes arrives when the regulatory team is already preparing the final submission.
TLD offers support for urgent pharmaceutical translation projects, with turnaround depending on document length and technical complexity.
If your company needs help preparing English regulatory documents, contact The Language Doctors to discuss the files and submission deadline.
No. Certification requirements depend on the submission type. IND regulations expressly require a signed translator certification, while other applications may have different requirements.
For an IND, the translator must sign a statement attesting that the translation is complete and accurate. Additional identifying details may be included for documentation purposes.
For NDAs, the applicable regulation requires both the foreign-language material and its English translation. Check the specific rules for other application types.
Common examples include foreign clinical study reports, manufacturing records, laboratory documentation, and supporting material prepared for regulatory submissions.
Yes. U.S. drug labeling must meet applicable FDA content and formatting rules, including requirements under 21 CFR Part 201.
Machine translation may assist with preliminary work, but its output needs qualified review. It doesn't replace required certification or the sponsor's responsibility for accurate submissions.
The FDA may request clarification or additional information. Serious mistakes can complicate the review and potentially delay a regulatory decision.
Generally, no. The relevant IND regulation requires a signed translator certification rather than notarization.
Participants must receive consent information in language they understand. Accurate translated consent documents or an appropriately approved short-form process may be used.
TLD can provide pharmaceutical translations and certification documentation tailored to the project. Final FDA compliance must be confirmed against the requirements of the specific submission.

At The Language Doctors, we work with native subject-matter experts across 200+ languages, including Norwegian, trusted for certified document translation.
With our service, you can expect translators who understand the subject as well as the language, certified translation for Norwegian contracts, healthcare and immigration documents, and wording handled for what it means in context, not just what it looks like on the page.
Everything you need for the moments where “easy to learn” is not the same as “easy to translate” and a legal or medical term carries a very specific meaning. We connect you with qualified professionals who understand the terminology and certification requirements involved.
Get your free Norwegian translation consultation today. Accurate, certified and built for official documents.
