The U.S. Food and Drug Administration (FDA) recently posted an update to the Electronic Submissions Gateway Next Generation (ESG NextGen) system — the modern platform used to receive regulatory submissions (including eCTD and other regulatory documents) from industry. This announcement was published on December 5, 2025 on the FDA’s official website.
📰 What the December 2025 Notice Covers
Here are the two key points from the recent FDA announcement:
Legacy SSL Certificate Does Not Need Renewal
An older digital certificate (used in the legacy ESG environment and set to expire on December 26, 2025) has not been in use since ESG NextGen launched earlier in 2025.
The FDA confirmed that you do not need to renew that expiring certificate to continue using ESG NextGen.
Browser Version Impact on Upload Workflow
Users accessing the ESG NextGen Unified Submission Portal (USP) with Google Chrome v142+ or Microsoft Edge v143+ may experience a slightly different upload process.
Specifically, when uploading files using the FileCatalyst TransferAgent, the browser may prompt users to open the agent in a new tab or window to begin uploads.
The FDA indicated this is a temporary change and that they are working with vendors to restore the original workflow.
📌 Why This Matters for Regulatory Publishing & Submissions Teams
1. ESG NextGen Is the Primary Transmission Pathway
The ESG NextGen system serves as the secure conduit between you and the FDA for almost all electronic regulatory submissions — including:
eCTD regulatory filings
Safety reports
Device reports
Other regulatory documents
Maintaining connectivity and submission readiness through ESG is therefore critical to regulatory operations.
2. SSL / Certificate Notices Affect Connectivity & Security
Although the notice says you don’t need to renew the legacy certificate, the technical confirmation helps reduce confusion about expiring certs that used to be required for machine-to-machine communication. Modern ESG NextGen workflows rely more on API and unified portal processes rather than legacy cert dependencies.
3. Browser Workflow Changes Can Impact Submission Execution
Because the FileCatalyst TransferAgent component handles actual file uploading:
Teams may need to adjust standard internal SOPs for upload procedures.
Help desks and submission coordinators should be ready to support users encountering the “open in new tab/window” prompt.
Confirm browser versions and test upload workflows ahead of critical filings.
🧭 Best Practices to Stay Ready
Here are a few suggested actions based on this December 2025 notice:
✔ Confirm Browser Compatibility
Make sure users are informed about the current Chrome/Edge behavior with ESG NextGen uploads and plan for alternative workflows or training if needed.
✔ Validate ESG NextGen Access Before Filing Windows
Prior to high-stakes filing days (especially year-end or agency blackout periods), verify that submission accounts and upload processes work in your environment across browsers.
✔ Monitor FDA ESG NextGen Updates
Continue watching the FDA’s ESG NextGen homepage for additional notices or workflow fix announcements.
Select Mandate HA
Select Mandate Function