You open Chrome on an older phone and everything still works, so why does a headline keep telling you that support is ending? Chrome ending support older Android versions is not a one time event. It is an ongoing pattern that Google repeats every couple of years as it quietly raises the minimum Android version Chrome will run on. If your phone is a few years old, this affects you more than you might think, and the confusion around what actually happens is exactly why this guide exists. Below you will find the current cutoff, a short history of how we got here, how to check your own device, and what to actually do about it.
Quick answer: as of now, Chrome requires Android 10 or newer. Support for Android 8 Oreo and Android 9 Pie ended with Chrome 139 in August 2025. Chrome still opens on those older versions, but it no longer receives new features, performance work, or security patches.
What Ending Support Actually Means
When Google says Chrome is ending support for an Android version, the browser does not vanish or refuse to open. What actually happens is quieter and, in a way, more dangerous. The Play Store simply stops offering new Chrome updates to devices below the new minimum version. The last compatible build keeps running exactly as it did the day support ended, while every device above the cutoff keeps getting new features, performance improvements, and critical security patches.
That gap grows every month. A browser that stops receiving patches becomes a fixed target, since any vulnerability discovered later is never fixed on that version, no matter how serious it turns out to be.
Why Google Keeps Doing This
It can look like Google is punishing people for owning older phones, but the underlying reason is more practical. Maintaining full support for a browser engine across a decade of Android releases means testing every new feature and every security fix against operating system APIs that no longer receive updates themselves. Each additional Android version supported multiplies the testing and compatibility burden, and older Android releases eventually stop receiving security patches from Google directly, which limits how safely Chrome can even operate on them regardless of what Google does on its end. Dropping support for the oldest, smallest slice of the install base lets Google focus engineering effort on the platforms most people actually use, while still giving the affected group a browser that keeps functioning, just without further updates.
This is also not unique to Google. Firefox, WhatsApp, and most major apps have gone through the same kind of cutoff at different points, usually following Android’s own support lifecycle rather than getting ahead of it.
The Current Cutoff: Chrome and Android 10
Google Chrome for Android currently requires Android 10 or later to install new versions. The change took effect with Chrome 139 in early August 2025, when Google dropped support for Android 8.0 Oreo and Android 9.0 Pie. Chrome 138 was the final version that ran on those two releases. Google’s own support notes were blunt about it: devices on Oreo or Pie would keep functioning on Chrome 138 indefinitely, but would never see a newer build again.
At the time, that decision affected somewhere around 10 percent of all active Android devices worldwide, a number in the hundreds of millions once you account for the full size of the Android install base. It was one of Google’s larger cutoffs in recent years, which is part of why it generated so much coverage.
A Short History of Chrome’s Android Cutoffs
This is not new behavior from Google. Chrome for Android has dropped older versions on a fairly predictable cycle for years, usually once a version has been out in the world for seven to nine years.
| Android version | Released | Chrome support ended |
| Jelly Bean (4.1 to 4.3) | 2012 | 2019 |
| KitKat (4.4) | 2013 | 2020 |
| Lollipop (5.0 to 5.1) | 2014 | 2021 |
| Marshmallow (6.0) | 2015 | 2022 |
| Nougat (7.0 to 7.1) | 2016 | November 2023 |
| Oreo (8.0 to 8.1) | 2017 | August 2025 |
| Pie (9.0) | 2018 | August 2025 |
Seeing the pattern laid out like this makes the next question fairly predictable. Android 10 launched in 2019, which puts it on roughly the same clock as Nougat and Oreo before it. Google has not announced anything official, but several outlets have already started speculating that Android 10 could be the next version to lose Chrome support, likely sometime after 2026 if the historical pattern holds.
How to Check If Your Device Is Affected
Checking your own status takes less than a minute.
- Open Settings on your phone and go to About Phone or About Tablet
- Look for the line labeled Android Version
- If it reads Android 10 or higher, you are on a currently supported version
- If it reads Android 9, 8, or lower, Chrome on your device is no longer receiving updates
You can also open Chrome itself, tap the three dot menu, go to Settings, then About Chrome, to see which version you currently have installed. If it shows Chrome 138 or lower and will not update further, that confirms your device has already hit the ceiling.
What Actually Breaks When Chrome Stops Updating
An unsupported browser does not fail all at once. It degrades gradually, and the practical effects show up in a few specific ways.
- Security patches stop. Any vulnerability found in Chrome after your cutoff version is never fixed on your device.
- New web standards eventually break pages. As sites adopt newer JavaScript, CSS, or encryption standards, an old browser engine renders them incorrectly or not at all.
- TLS and certificate handling ages out. Some banking, shopping, and login pages quietly require newer transport security than an old Chrome build supports, which shows up as a page that simply will not load.
- Extensions and web apps drift out of compatibility. Progressive web apps built against current browser APIs may misbehave or fail to install.
None of this happens on day one. It happens gradually over months, which is exactly why it catches people off guard. The browser looks fine right up until the specific thing you needed stops working.
What To Do If Your Device Is Affected
| Option | What it involves | Best for |
| Update to Android 10 or newer | Check Settings, System, System Update for an available upgrade | Devices whose manufacturer still offers newer Android builds |
| Switch to a browser that still supports your version | Install Firefox, which currently supports Android 5.0 and up | Anyone who wants to keep using their current device a while longer |
| Install a custom ROM | Flash LineageOS or GrapheneOS, which extend security support beyond what the manufacturer offers | Technically confident users comfortable with manual setup |
| Replace the device | Move to a phone or tablet currently shipping with Android 10 or later | Devices too old to receive any further manufacturer updates at all |
If your manufacturer no longer offers an Android update for your specific model, a custom ROM is worth exploring before assuming you need new hardware. LineageOS and GrapheneOS both maintain security patches for a wide range of older devices long after the original manufacturer has stopped, though the installation process is more involved than a standard software update.
Alternative Browsers for Older Android Versions
If updating your Android version is not an option right now, switching browsers buys real time without buying new hardware.
| Browser | Minimum Android version | Notes |
| Firefox | Android 5.0 | Actively maintained, receives regular security updates |
| Chrome | Android 10.0 | Current requirement as of this cutoff |
| Opera | Android 5.0 | Similar reach to Firefox, includes a built in VPN option |
| Kiwi Browser | Android 5.0 | Chromium based, supports desktop style extensions |
Switching browsers is not a permanent fix. It buys time on hardware you already own while you plan an upgrade, and it is far safer than continuing on an unpatched version of Chrome indefinitely.
Frequently Asked Questions
Does Chrome still work on Android 8?
It still opens and functions, but it stopped receiving updates in August 2025 with the release of Chrome 139. The last version available on Android 8 is Chrome 138, and it will not be updated further.
Will my phone stop working if Chrome loses support?
No. Your phone and every other app on it will continue working normally. Only Chrome itself becomes frozen at its final supported version, gradually growing less secure and less compatible with modern websites over time.
Can I still download Chrome on an unsupported Android version?
The Play Store will only offer the last compatible version for your Android release. You will not see newer Chrome updates listed as available until you upgrade your operating system.
Is Android 10 going to lose Chrome support soon?
Google has not announced a date. Based on the historical pattern of Chrome supporting an Android version for roughly seven to nine years after release, Android 10 is a reasonable candidate for a future cutoff, though nothing is confirmed.
Conclusion
Chrome ending support for older Android versions is not a one time headline, it is a recurring maintenance cycle that has already worked its way through Jelly Bean, KitKat, Lollipop, Marshmallow, Nougat, and most recently Oreo and Pie. The current requirement is Android 10 or newer, and if your device runs anything older, Chrome on it is already frozen at its final update. Check your Android version today, weigh whether an operating system update is available, and consider a supported alternative browser or a custom ROM if new hardware is not in your immediate plans. Staying on top of this one setting is a small habit that keeps your browsing meaningfully safer over time.