Adds early warning when the storage device backing the user's data is running low on free space. This warning is provided to currently running applications, which can pause or abandon in-progress operations that would otherwise fill up the user's storage device.


A recent issue, which allowed bad actors to precisely measure free disk space, was patched because it could be exploited to measure the size of cross-origin resources or be used for fingerprinting. To patch this, Chrome no removed free disk space as a factor in calculating quota. This caused a regression, where applications start avoiding downloading a large corpus of data when the free disk space is low. For example, some applications would not enable offline sync for users with low free disk space. This was an attempt to avoid a bad user experience -- enabling offline sync would lead to a large amount of data being downloaded and stored locally, which would lead to running out of disk space, which could cause system instability such as OS crashes. This proposal aims to address this class of regressions.



Specification link

Unknown standards status - check spec link for status

Status in Chromium


Proposed (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signals


Last updated on 2021-12-11