Google has provided clarification regarding the large amount of space Chrome was consuming due to its artificial intelligence features. The browser's official documentation now specifies that to use these tools locally, a minimum of 20 GB of available hard drive space is required.
This information was released months after a controversy involving Chrome. In May, users noticed that the program had silently downloaded a version of Gemini Nano, which occupied 4 GB on the user's disk. This download occurred without any notification or permission request, even when the AI features were not being used.
Despite this incident, the company also assures that if the device cannot deliver adequate performance, the browser will not initiate the download of the necessary models to activate such functionalities. As reported by WindowsReport, between July 29 and August 1, Google updated the Chrome support pages related to on-device AI features, adding four new sections detailing the minimum requirements and download conditions.
Regarding AI eligibility, Chrome states that it will not even attempt to download the models if it detects that the hardware lacks sufficient power to run the tools, thus ignoring incompatible computers. However, Google does not detail exactly what computer specifications are needed to run the AI, and the help page warns that these requirements are subject to change over time.
When the device meets the prerequisites, the browser checks for an unlimited internet connection and 20 GB of free disk space, in addition to verifying the necessary processing capacity to perform the download.
Concerning the May incident, Google advises users not to look for the model in the computer files and delete it manually, as this action does not prevent the browser from performing a new download. Instead, the browser offers a specific control to disable local AI, located in the settings under the section named 'System'. By disabling this option, Chrome proceeds to delete the AI model files.
Google has implemented significant improvements in Chrome for Android, resulting in a 48% reduction in what is known as 'scroll jank,' making the scrolling experience smoother for users.
This type of instability is a common behavior, but one that is now less frequent, where the scrolling flow appears to momentarily stop. In certain situations, the browser may exhibit a 'jump,' abruptly advancing to a more distant point on the page, making it difficult to locate specific information.
Google clarifies that this jump occurs due to a time limit Chrome has to display each frame before screen refresh. If this limit is exceeded, the previous frame remains visible for an additional refresh cycle. When the new frame is finally ready, the page jumps directly to the most updated scroll position.
Although users perceive this dynamic as a visual 'stutter,' the problem is considered more subtle than a complete freeze. Therefore, Google focused its efforts on reducing this 'scroll jank.'
The solution was not limited to just speeding up Chrome, but rather ensuring that the frame delivery flow was as consistent as possible, given that various factors can cause this instability. Developers modified how Chrome manages touch inputs related to scrolling.
Instead of overloading the browser's main task—which might be busy executing scripts—the scrolling processing was transferred to a more specialized and consequently less prone to delays component. Additionally, Chrome began optimizing the frame display time.
If a small delay of a few milliseconds occurs in a touch, the browser chooses to wait a bit before rendering the next image. If the remaining time is insufficient, the system estimates the position the finger should reach at the subsequent moment, preventing the screen from repeatedly displaying an old frame and generating the 'stutter' effect.
As a result of these optimizations, Google reports that 'scroll jank' has been reduced by 48% in Chrome for Android between 2023 and 2026. Although the article's author expected a higher percentage, they consider this advancement relevant, considering the vast diversity of devices and configurations on which Chrome for Android operates. Google indicated that optimization work on Chrome for Android will continue.
