eCTD File Naming Conventions: The Complete Guide to Compliant Document Names
eCTD file naming conventions are technical rules within the eCTD specification that limit file names to controlled character sets, lowercase formatting, and defined length limits. Spaces, uppercase letters, and many special characters can trigger validation problems, so teams should apply the current regional specifications consistently before publishing and transmission.
Key Takeaways
Key Takeaways
- File naming violations are a common and preventable cause of eCTD validation failure
- ICH M8 limits file names to lowercase alphanumeric characters, hyphens, and underscores, with total path length not exceeding 180 characters
- Spaces, special characters, and uppercase letters in file or folder names will trigger immediate gateway rejection
- FDA, EMA, and Health Canada enforce the same ICH M8 naming rules but have minor regional differences in Module 1 folder structures
- eCTD file naming conventions are the standardized rules defined by ICH M8 that govern how documents, folders, and paths must be named within Electronic Common Technical Document (eCTD) submissions. These naming conventions specify character limits, allowed characters, case requirements, and structural rules that regulatory gateways enforce during validation.
- > Key Point: File naming errors are usually preventable and can stop a submission before content review begins, which is why naming controls should be built into authoring and publishing workflows.
- Getting file names wrong is one of the fastest ways to trigger a gateway rejection.
- The frustrating reality is that most file naming errors are entirely preventable. A document named
Clinical Study Report (Final).PDFcontains four separate naming violations that will fail validation, yet these errors often go unnoticed until the critical moment of submission. - In this guide, you'll learn:
- Complete eCTD file naming rules with character limits and allowed characters
- Folder naming conventions and path length requirements
- Regional differences between FDA, EMA, and Health Canada naming requirements
- The 12 most common file naming errors and how to prevent them
- Step-by-step process for fixing non-compliant file names
- ---
What Are eCTD File Naming Conventions?
eCTD file naming conventions are the technical specifications within the ICH M8 standard that define the exact rules for naming documents and folders in regulatory submissions. They are enforced automatically by regulatory agency gateways (FDA ESG, EMA CESP, Health Canada CESR, PMDA) and violations trigger immediate submission rejection without human review.
eCTD file naming conventions are the technical specifications that define how every document and folder in an eCTD submission must be named. These conventions are part of the ICH M8 specification and are enforced by all regulatory agency gateways including FDA ESG, EMA CESP, and Health Canada CESR.
Key characteristics of eCTD file naming conventions:
- Maximum file name length of 64 characters including extension
- Only lowercase letters (a-z), numbers (0-9), and hyphens (-) are allowed
- Spaces, uppercase letters, and special characters are prohibited
- File extensions must be lowercase (.pdf not .PDF)
- Total path length has recommended limits varying by region
- Folder names follow the same character rules with specific structural requirements
“Key Point: File naming rules are enforced automatically during technical validation, so teams should treat compliant naming as a publishing control rather than a last-minute cleanup task.
Understanding eCTD file naming conventions is essential because these rules are enforced automatically at the gateway level. Unlike content issues that reviewers identify during assessment, file naming violations trigger immediate rejection before your submission even reaches a human reviewer.
eCTD Naming Rules: Character Requirements
The eCTD naming rules specify exactly which characters are permitted in file names and folder names. Violations of these character requirements are the primary cause of file naming validation errors.
Allowed Characters in eCTD File Names
| Character Type | Allowed | Examples | Notes |
|---|---|---|---|
| Lowercase letters | Yes | a, b, c, z | Only a-z permitted |
| Uppercase letters | No | A, B, C, Z | Must convert to lowercase |
| Numbers | Yes | 0, 1, 2, 9 | Digits 0-9 only |
| Hyphens | Yes | - | Primary word separator |
| Underscores | Varies | _ | FDA allows, EMA prohibits - avoid for safety |
| Periods | Limited | . | Only before file extension |
| Spaces | No | " " | Never allowed |
| Special characters | No | @, #, $, %, &, *, (, ) | Never allowed |
| Non-ASCII characters | No | e, u, n | Never allowed |
Character Rules by File Name Component
| Component | Rule | Valid Example | Invalid Example |
|---|---|---|---|
| File name body | Lowercase alphanumeric + hyphens | clinical-study-report | Clinical_Study_Report |
| Word separator | Hyphens only | study-001-csr | study 001 csr |
| Numbers | Digits 0-9 allowed | batch-12345 | batch-#12345 |
| Version indicators | Use hyphens | protocol-v2 | protocol (v2) |
| File extension | Lowercase required | .pdf | .PDF |
| Extension separator | Single period | report.pdf | report..pdf |
File Name Length Limits
The eCTD naming requirements specify strict length limits:
| Element | Maximum Length | Notes |
|---|---|---|
| File name (with extension) | 64 characters | ICH M8 specification |
| File name (without extension) | 60 characters | Allows for .pdf extension |
| Folder name | 64 characters | Same as file names |
| Total path length | 180-230 characters | Varies by region and system |
File Name Length Calculation:
While the ICH M8 specification allows 64 characters, keep file names under 50 characters to provide a safety buffer for folder path requirements and avoid edge-case validation failures across different regulatory systems. This conservative approach reduces the risk of total path length violations, especially for nested folder structures.
eCTD File Names: Folder Naming Conventions
eCTD file names and folder names follow similar rules, but folders have additional structural requirements based on their position in the eCTD module hierarchy.
ICH M8 Folder Naming Structure
The eCTD specification defines standard folder names for each module section:
| Module | Standard Folder Name | Purpose |
|---|---|---|
| Root | 0000/, 0001/, etc. | Sequence folders |
| Module 1 | m1/ | Administrative information |
| Module 2 | m2/ | CTD summaries |
| Module 3 | m3/ | Quality (CMC) |
| Module 4 | m4/ | Nonclinical |
| Module 5 | m5/ | Clinical |
| Utility | util/ | DTD, stylesheets |
Module-Specific Folder Naming
Module 1 Folder Naming (FDA Example):
| Section | Folder Name | Pattern |
|---|---|---|
| 1.1 | 11-forms/ | Section number + description |
| 1.2 | 12-cover-letter/ | Section number + description |
| 1.3.1 | 131-patent-info/ | Subsection number + description |
| 1.14 | 114-labeling/ | Section number + description |
| 1.14.1 | 1141-spl/ | Subsection number + abbreviation |
Module 3 Folder Naming:
| Section | Folder Name | Content |
|---|---|---|
| 3.2.S | 32s-drug-sub/ | Drug substance |
| 3.2.S.1 | 32s1-gen-info/ | General information |
| 3.2.S.2.2 | 32s22-manuf-proc/ | Manufacturing process |
| 3.2.P | 32p-drug-prod/ | Drug product |
| 3.2.P.5.1 | 32p51-spec/ | Specifications |
Folder Naming Rules Summary
| Rule | Requirement | Example |
|---|---|---|
| Case | All lowercase | m3/ not M3/ |
| Numbers | Section numbers included | 32s-drug-sub/ |
| Separators | Hyphens between elements | 32s1-gen-info/ |
| Abbreviations | Standard ICH abbreviations | gen-info for general information |
| Trailing slash | Required for directories | m1/us/ |
| Spaces | Never allowed | drug-sub/ not drug sub/ |
Complete Path Examples
Valid eCTD Paths:
Invalid eCTD Paths:
Use a consistent folder structure template across all your eCTD submissions. Store this template in a version-controlled location and distribute it to all regulatory team members. This ensures every eCTD submission follows the same naming patterns, reducing the chance of regional or module-specific errors and making quality reviews faster and more reliable.
eCTD Naming Requirements: Path Length Specifications
The eCTD naming requirements include specifications for total path length that vary by region and technical environment. Understanding path length limits prevents truncation errors and system compatibility issues.
Regional Path Length Requirements
| Region | Maximum Path Length | Notes |
|---|---|---|
| FDA (US) | 230 characters | ESG technical limit |
| EMA (EU) | 180 characters | CESP recommendation |
| Health Canada | 200 characters | CESR specification |
| PMDA (Japan) | 200 characters | Gateway limit |
| ICH M8 | 180 characters | Recommended maximum |
Path Length Calculation
Total path length includes:
- Sequence folder (e.g.,
0000/) - Module folder (e.g.,
m3/) - All subfolders (e.g.,
32-body-data/32s-drug-sub/) - File name with extension (e.g.,
drug-substance-specification.pdf)
Example Path Length Calculation:
Path Length Best Practices
| Practice | Recommendation |
|---|---|
| Target length | Keep paths under 150 characters for safety margin |
| File name length | Target 40-50 characters when possible |
| Folder depth | Minimize unnecessary subfolder nesting |
| Abbreviations | Use standard ICH abbreviations consistently |
| Testing | Validate path lengths before final assembly |
CTD File Naming: Regional Differences
CTD file naming requirements are largely harmonized across regions, but subtle differences exist that can cause validation failures when preparing multi-regional submissions.
FDA vs EMA vs Health Canada File Naming Comparison
| Requirement | FDA (US) | EMA (EU) | Health Canada |
|---|---|---|---|
| Maximum file name length | 64 characters | 64 characters | 64 characters |
| Lowercase required | Yes | Yes | Yes |
| Hyphens allowed | Yes | Yes | Yes |
| Underscores allowed | Yes (discouraged) | No | Yes (discouraged) |
| Spaces allowed | No | No | No |
| Maximum path length | 230 characters | 180 characters | 200 characters |
| Extension case | Lowercase only | Lowercase only | Lowercase only |
| Unicode characters | No | No | No |
Regional Folder Name Differences
Module 1 Regional Variations:
| Element | FDA | EMA | Health Canada |
|---|---|---|---|
| Regional subfolder | m1/us/ | m1/eu/ | m1/ca/ |
| Cover letter location | 12-cover-letter/ | 10-cover/ | 10-cover/ |
| Forms location | 11-forms/ | 12-form/ | 121-form/ |
| Labeling location | 114-labeling/ | 131-smpc/ | 131-prod-mono/ |
| Financial disclosure | 18-financial/ | N/A | N/A |
Multi-Regional Submission Considerations
When preparing eCTD submissions for multiple regions, follow the most restrictive naming rules:
| Rule | Most Restrictive | Apply To |
|---|---|---|
| Path length | EMA: 180 characters | All regions |
| Underscores | EMA: not allowed | All regions - use hyphens |
| File name length | All: 64 characters | All regions |
| Character set | All: lowercase alphanumeric + hyphens | All regions |
“Key Point: For multi-regional submissions, applying the most conservative current regional naming rules across the whole dossier helps avoid rework and region-specific validation failures.
For global submissions, always follow EMA's naming restrictions (no underscores, 180-character path limit) as these are the most conservative and most likely to change in future updates. Files compliant with EMA rules will pass FDA and Health Canada validation, giving you future-proof compliance across all major regions.
Create a regional file naming checklist for your team that specifies which names work for each region. Include visual examples of files that pass FDA but fail EMA (such as those with underscores) so authors understand why the stricter EMA rules apply to all submissions. This prevents the costly last-minute discovery that files pass one region but fail another.
Common eCTD File Naming Errors
Understanding the most frequent eCTD file naming errors helps you prevent validation failures and gateway rejections. These 12 errors account for the majority of naming-related submission problems.
The 12 Most Common File Naming Errors
| Rank | Error Type | Example | Correct Version |
|---|---|---|---|
| 1 | Spaces in file name | clinical study.pdf | clinical-study.pdf |
| 2 | Uppercase letters | ClinicalStudy.pdf | clinical-study.pdf |
| 3 | Uppercase extension | report.PDF | report.pdf |
| 4 | Special characters | study#001.pdf | study-001.pdf |
| 5 | Parentheses | report(final).pdf | report-final.pdf |
| 6 | Underscores (EMA) | clinical_study.pdf | clinical-study.pdf |
| 7 | File name too long | 70+ character names | Shorten to under 64 |
| 8 | Path too long | 200+ character paths | Restructure path |
| 9 | Multiple periods | study..report.pdf | study-report.pdf |
| 10 | Non-ASCII characters | etude-clinique.pdf | etude-clinique.pdf |
| 11 | Trailing spaces | report .pdf | report.pdf |
| 12 | Mixed case extension | report.Pdf | report.pdf |
Common Error Categories
| Error Category | Typical Root Cause |
|---|---|
| Case violations | Copying file names from authoring tools or operating systems without normalization |
| Space characters | Using document titles directly as file names |
| Special characters | Carrying formatting characters or symbols into published file names |
| Length violations | Overly descriptive naming without length checks |
| Extension errors | Default save settings or manual renaming mistakes |
Common Error Patterns by Source System
| Source System | Typical Errors | Prevention |
|---|---|---|
| Microsoft Word | Spaces, uppercase, long names | Rename at PDF conversion |
| Mac Finder | Spaces, special characters | Batch rename tool |
| Windows Explorer | Uppercase extension, spaces | Automated renaming script |
| SharePoint | Encoded characters (%20) | Clean before publishing |
| Document Management | Version numbers in parens | Establish naming convention |
How to Fix eCTD File Naming Errors
When you discover file naming errors in your eCTD submission, systematic correction prevents missing violations and ensures all documents pass validation.
Step-by-Step File Name Correction Process
Step 1: Identify All Non-Compliant Files
Run validation to generate a complete list of naming errors:
- Use eCTD publishing tool validation
- Run dedicated file naming check
- Review validation report for all naming violations
Step 2: Categorize Errors
| Error Type | Fix Required | Tools Available |
|---|---|---|
| Case errors | Convert to lowercase | Bulk rename utility |
| Space errors | Replace with hyphens | Find/replace tool |
| Special characters | Remove or replace | Regex-based cleanup |
| Length errors | Shorten file name | Manual renaming |
| Extension errors | Change to lowercase | File extension fixer |
Step 3: Apply Naming Corrections
For individual files:
- Identify the non-compliant element
- Rename following the conventions
- Update all references to the file
- Regenerate XML backbone
- Recalculate MD5 checksum
For bulk corrections:
- Export list of non-compliant files
- Create mapping of old names to new names
- Execute batch rename operation
- Update backbone.xml references
- Regenerate all checksums
- Re-validate entire submission
File Name Transformation Examples
| Original Name | Issue | Corrected Name |
|---|---|---|
Clinical Study Report.pdf | Spaces, uppercase | clinical-study-report.pdf |
Module 2.3 QOS (v2).PDF | Multiple violations | module-2-3-qos-v2.pdf |
STABILITY_DATA_12345.pdf | Uppercase, underscores | stability-data-12345.pdf |
Pharmacology Study #1.pdf | Space, special char | pharmacology-study-1.pdf |
Drug Substance Spec (Final Version).pdf | Many violations | drug-substance-spec-final.pdf |
Checksum Regeneration After Renaming
After renaming any file in an eCTD submission, you must regenerate the MD5 checksum in the backbone.xml immediately. The checksum validates file integrity at the gateway level, and a renamed file with an old checksum will fail validation even if the new name is compliant. This step is commonly forgotten and causes resubmission delays-build it into your file renaming SOP to prevent this costly oversight.
Checksum update process:
- Rename the file
- Calculate new MD5 checksum
- Update the
checksumattribute in backbone.xml - Update the
xlink:hrefpath if location changed - Validate the submission again
eCTD File Naming Best Practices
Following eCTD file naming best practices from the start of document creation prevents costly corrections and submission delays.
Document Creation Best Practices
| Practice | Implementation | Benefit |
|---|---|---|
| Establish naming conventions early | Create naming standards before authoring | Prevents end-stage renaming |
| Use templates with compliant names | Pre-configured document templates | Consistent naming from start |
| Train authors on conventions | Naming rules in authoring SOPs | Reduces manual correction |
| Validate at creation | Check names when documents finalize | Catches errors early |
| Avoid descriptive long names | Use codes and abbreviations | Stays within character limits |
Naming Convention Framework
Recommended naming pattern:
Examples using this pattern:
| Document | Naming Pattern Result |
|---|---|
| Module 3.2.S.4.1 Drug Substance Specification | m3-32s41-ds-spec.pdf |
| Module 5.3.5.1 Pivotal Efficacy Study | m5-5351-study-001-csr.pdf |
| Module 2.7.4 Clinical Safety Summary | m2-274-clin-safety-sum.pdf |
Pre-Publishing Checklist
Before final eCTD assembly, verify all file names against this checklist:
| Check | Verification Method |
|---|---|
| All lowercase | Automated scan for uppercase |
| No spaces | Automated scan for space characters |
| No special characters | Regex validation |
| Length under 64 characters | Character count check |
| Path length under 180 characters | Full path validation |
| Lowercase extensions | Extension verification |
| No consecutive hyphens | Pattern matching |
| No leading/trailing hyphens | Pattern matching |
Automated Validation Tools
| Tool Type | Function | Integration Point |
|---|---|---|
| Pre-authoring templates | Enforce naming at creation | Document management |
| Batch rename utilities | Bulk correction capability | Pre-publishing |
| Publishing tool validation | Comprehensive checking | Assembly phase |
| Gateway pre-check | Final validation | Pre-submission |
eCTD File Naming Validation Error Messages
Understanding validation error messages helps you quickly identify and correct file naming issues during eCTD preparation.
Common Validation Error Messages
| Error Message | Meaning | Resolution |
|---|---|---|
| "Invalid character in file name" | Special character, space, or uppercase detected | Remove invalid characters |
| "File name exceeds maximum length" | Name longer than 64 characters | Shorten file name |
| "Invalid file extension case" | Uppercase extension (.PDF, .Pdf) | Convert to lowercase (.pdf) |
| "Path length exceeds limit" | Total path over regional maximum | Shorten file name or restructure |
| "Invalid folder name" | Folder name violates conventions | Rename folder per ICH M8 |
| "Underscore not permitted" | Underscore used (EMA validation) | Replace with hyphen |
Validation Error Message Reference Table
| Error Code | Description | ICH M8 Reference | Severity |
|---|---|---|---|
| FN-001 | Invalid character in file name | Section 2.3.1 | Critical |
| FN-002 | File name length exceeded | Section 2.3.2 | Critical |
| FN-003 | Invalid extension case | Section 2.3.1 | Critical |
| FN-004 | Path length exceeded | Section 2.4 | Critical |
| FN-005 | Invalid folder name format | Section 2.5 | Critical |
| FN-006 | Reserved character used | Section 2.3.1 | Critical |
| FN-007 | Missing file extension | Section 2.3.3 | Critical |
| FN-008 | Multiple extensions detected | Section 2.3.3 | Warning |
Gateway-Specific Error Messages
FDA ESG Error Messages:
| ESG Error | Meaning | Action |
|---|---|---|
| "FAIL: Invalid filename" | File name validation failed | Check all naming rules |
| "FAIL: Path too long" | Path exceeds 230 characters | Shorten path components |
| "WARN: Underscore in filename" | Underscore detected | Replace with hyphen |
EMA CESP Error Messages:
| CESP Error | Meaning | Action |
|---|---|---|
| "File naming error" | General naming violation | Review against EU-M1 specs |
| "Path exceeds maximum" | Path over 180 characters | Restructure path |
| "Invalid character" | Non-compliant character found | Clean file name |
Key Takeaways
eCTD file naming conventions are the ICH M8 rules that specify how documents must be named in regulatory submissions. File names must use only lowercase letters (a-z), numbers (0-9), and hyphens (-), with a maximum length of 64 characters including the file extension. Spaces, uppercase letters, and special characters are prohibited. These conventions ensure consistent validation across FDA, EMA, and other regulatory gateways.
Key Takeaways
- File naming errors cause 18% of eCTD gateway rejections: These errors are entirely preventable with proper naming conventions established before document creation and systematic validation before submission.
- The maximum file name length is 64 characters including extension: Only lowercase letters (a-z), numbers (0-9), and hyphens (-) are allowed. Spaces, uppercase letters, special characters, and underscores (for EMA) are prohibited.
- Path length limits vary by region: EMA has the most restrictive limit at 180 characters; FDA allows 230 characters. For multi-regional submissions, always follow EMA's 180-character limit.
- Folder names follow the same character rules as file names: ICH M8 defines standard folder naming patterns for each module section that must be followed exactly.
- Prevention is more efficient than correction: Establishing naming conventions during document authoring and validating names before publishing prevents the time-consuming process of renaming files and regenerating checksums.
- ---
Next Steps
Implementing correct eCTD file naming conventions prevents validation failures and gateway rejections, but manually checking thousands of files across a submission is error-prone and time-consuming. Automated validation catches naming errors before they delay your submission.
Need help validating eCTD file names? Assyro's AI-powered platform validates all file naming conventions automatically, checking character compliance, length limits, path lengths, and regional requirements across your entire submission. Catch naming errors before they become gateway rejections.
Organizations managing regulatory submissions benefit from automated validation tools that catch errors before gateway rejection. Assyro's AI-powered platform validates eCTD submissions against FDA, EMA, and Health Canada requirements, providing detailed error reports and remediation guidance before submission.