20/08/2026
Since March, Chrome has been disabling the unload event for a growing share of page loads, 80% from 25 August and all of them from 22 September. Code that saves work or notifies a server when a page closes can simply stop running, with no error and no deploy to blame, and because the rollout is percentage-based the failures look intermittent.
Our new guide explains why the failures look random, shows the header that restores the old behaviour immediately, and then walks through the proper fix for each kind of handler, from save-on-exit code to cross-window signalling, in any stack including server-rendered templates.
Read the full guide →
Chrome disables the unload event on 80% of page loads from 25 August 2026. See who's affected, how to find your handlers, and the fix for each use-case.