Microsoft Edge: Retirement of default unload event support

Microsoft Edge will stop running unload event handlers by default starting September 2026, requiring sites to explicitly permit them via Permissions Policy. Organizations should migrate to modern lifecycle events like visibilitychange and pagehide, update applications, and use provided policies temporarily during transition.

If your websites or applications do not use unload event handlers (unload), the impact described below does not apply and no action is required.

[What and why]

Microsoft Edge is changing the default behavior of the web platform unload event as part of the ongoing retirement of unload event handlers.

Today, unload event handlers are allowed by default. As this change rolls out, pages will no longer run unload event handlers unless the site explicitly permits them through Permissions Policy. Organizations should work with application owners to migrate their applications to modern lifecycle events and APIs designed for these scenarios.

The unload event is not a reliable way to save data, perform cleanup operations, or indicate that a user session has ended because browsers and operating systems can suspend or terminate pages without firing it. It can also prevent pages from using the back/forward cache, which may affect navigation performance.

[Rollout schedule]

• Worldwide, GCC, GCC High, DoD: Beginning in early September 2026 and expected to complete in October 2026

[Impact on your organization]

Who is affected

Organizations may be affected if internal websites, public websites, or third-party web applications that users depend on use unload event handlers to provide required functionality.

Users are affected only when a website or application depends on unload event handlers and does not provide an alternative implementation.

Platforms and services

• Microsoft Edge
• Websites and web applications opened in Microsoft Edge
• WebView2-based applications
• Managed Microsoft Edge environments

What will happen

Websites and applications that rely on unload event handlers may experience functional changes when the handlers no longer run by default.

Common scenarios include applications that use unload handlers to:

• Save user data
• Release resources
• Send analytics or telemetry
• Notify services that a session has ended

Organizations can temporarily preserve the current behavior while applications are updated by enabling the ForcePermissionPolicyUnloadDefaultEnabled Microsoft Edge policy. This policy is intended only as a migration aid while application owners update affected applications. A website can still apply a more restrictive Permissions Policy configuration.

[Action required and recommendations]

Complete the following actions by September 6,2026:

• Identify internal and business-critical web applications that register unload event handlers, including handlers introduced through third-party libraries.
• Validate application behavior without relying on unload event handlers.
• Use Microsoft Edge DevTools to identify pages that are blocked from using the back/forward cache because of unload listeners.
• Migrate data-saving scenarios to the visibilitychange event and use transitions to the hidden state as the final reliable opportunity to preserve application state.
• Use the pagehide event when code must respond to navigation away from a page while remaining compatible with the back/forward cache.
• Update internal development standards, support documentation, and testing guidance.
• Notify application owners, support teams, and affected users of any application-specific changes.

If an application cannot be updated before rollout completion, site owners can temporarily enable unload support through Permissions Policy. Administrators can also use the ForcePermissionPolicyUnloadDefaultEnabled Microsoft Edge policy to retain the previous default behavior while migration work is completed. These controls are intended to provide migration time and should not be considered permanent solutions. A website can still apply a more restrictive Permissions Policy configuration.

Learn more

• ForcePermissionPolicyUnloadDefaultEnabled | Microsoft Edge | Microsoft Learn
• Document: visibilitychange event | Mozilla
• Window: pagehide event | Mozilla

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.