In late June 2025, Google confirmed that Chrome 138 will be the final version of its popular browser to support devices running Android 8 (Oreo) and Android 9 (Pie). From Chrome 139 onward—expected to roll out on August 5, 2025—users must be on Android 10 or newer to receive updates. Devices on Android 8 or 9 can still run Chrome but will no longer get security patches, feature improvements, or bug fixes via new Chrome releases.

Android 8.0 “Oreo” and Android 9.0 “Pie” debuted in 2017 and 2018, respectively. Oreo introduced Project Treble (modular architecture aimed at speeding up OEM updates), notification channels, picture-in-picture video, and more. Pie refined UI gestures, adaptive brightness, digital wellbeing tools, and tightened privacy controls; its final security update was delivered in January 2022, after which Google Play Services support continued but OS-level patches ceased. At launch, both versions represented significant steps forward; now, roughly seven to eight years later, they’ve effectively reached their end of life in terms of OS-level support.

Android fragmentation is a perennial topic. As of early 2025, combined usage of Android Oreo (8.x) and Pie (9.x) is modest but not negligible. Wikipedia notes that as of January 2025, about 3.09% of devices ran Android Oreo and approximately 3.59% ran Android Pie, for a combined share of around 6.68%. StatCounter data for May 2025 shows Android 10 at roughly 5.26% and newer versions dominating, but older versions still persist globally, especially in regions where users hold onto devices longer or OEMs deliver fewer updates. In absolute numbers, given Android’s roughly 3.3 billion active devices worldwide, even a 6–7% share translates to tens or hundreds of millions of users who will soon run an unsupported Chrome.

Running an outdated browser on an OS that no longer receives security updates compounds risk. Chrome’s security team regularly patches vulnerabilities in the browser itself, but when Chrome 139+ drops support for Android 8/9, those OS-level vulnerabilities cannot be mitigated by updating Chrome. In effect, users remain on Chrome 138, which over time accumulates unpatched security flaws in the browser as well. Cybersecurity experts warn that outdated browsers on unpatched OSes create fertile ground for exploits, privacy leaks, and malware. Since Android 8 and 9 no longer receive platform security fixes (Android 8.0 unsupported as of January 2021; Android 8.1 unsupported as of October 2021; Android 9 unsupported as of January 2022), the combination of old OS plus static browser heightens exposure.

From Google’s perspective, focusing development and testing on Android 10+ simplifies engineering: newer Android releases provide updated WebView, security frameworks, and platform APIs. Supporting antiquated OS versions often requires workarounds or maintaining legacy code paths, increasing complexity and hindering the rollout of cutting-edge features. Moreover, Android 10 introduced scoped storage changes, privacy enhancements (e.g., one-time permissions), and improved performance that Chrome leverages. By moving the baseline to Android 10+, Google aligns Chrome with a more modern, secure foundation and can adopt newer platform capabilities without backward-compatibility baggage.

For many users, upgrading the OS isn’t straightforward. OEM update policies vary widely: flagship devices might get two to three major Android upgrades, while budget or older models often stop receiving updates after one or two years. In some regions, inexpensive devices running Android 8/9 remain in active use because upgrades aren’t offered or users can’t afford newer hardware. Even if an OEM release exists, carriers might delay distribution or drop support altogether. Users tied to such devices face limited options: continue using an outdated Chrome (with growing security risks), switch to an alternative browser that still supports older Android versions (bearing its own security implications), or seek deeper technical routes like installing custom ROMs.

Web developers and enterprises need to note this change for several reasons. First, analytics: as Chrome usage on Android 8/9 stagnates on version 138, metrics around browser versions will shift; seeing a plateau in update adoption among older segments is expected. Second, testing: QA teams can de-prioritize testing on Android 8/9 for features targeting Chrome 139+ enhancements. Third, enterprise device fleets: organizations managing devices in verticals (e.g., retail kiosks, field equipment) running Android 8/9 must plan OS upgrades or device replacements to maintain a secure browsing environment. Some enterprises might lock down browser features or use managed browser solutions, but the lack of Chrome updates past version 138 poses a long-term support concern.

Global Android distribution varies: in developed markets, users often upgrade devices more frequently, so the Android 8/9 user base is relatively small; in emerging markets, older devices linger longer, so a higher proportion may be affected. According to StatCounter, Android 10 holds around 5.26% market share as of May 2025, with Android 8/9 combined near 6–7% globally but unevenly distributed by region. Users in regions with limited upgrade options or slower replacement cycles will feel the cutoff more acutely. Local connectivity constraints and data costs can further complicate large OS updates or switching devices.