Google Pixel End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Google Pixel versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| Pixel | — | Oct 20, 2016 | Oct 6, 2019 | 2499 days past EOL | EOL |
| Pixel XL | — | Oct 20, 2016 | Oct 6, 2019 | 2499 days past EOL | EOL |
| Pixel 2 | — | Oct 17, 2017 | Oct 5, 2020 | 2134 days past EOL | EOL |
| Pixel 2 XL | — | Oct 17, 2017 | Oct 5, 2020 | 2134 days past EOL | EOL |
| Pixel 3 | — | Oct 18, 2018 | Oct 5, 2021 | 1769 days past EOL | EOL |
| Pixel 3 XL | — | Oct 18, 2018 | Oct 5, 2021 | 1769 days past EOL | EOL |
| Pixel 3a | — | May 15, 2019 | May 5, 2022 | 1557 days past EOL | EOL |
| Pixel 3a XL | — | May 15, 2019 | May 5, 2022 | 1557 days past EOL | EOL |
| Pixel 4 | — | Oct 24, 2019 | Oct 5, 2022 | 1404 days past EOL | EOL |
| Pixel 4 XL | — | Oct 24, 2019 | Oct 5, 2022 | 1404 days past EOL | EOL |
| Pixel 4a | — | Aug 20, 2020 | Aug 5, 2023 | 1100 days past EOL | EOL |
| Pixel 5 | — | Oct 15, 2020 | Nov 5, 2023 | 1008 days past EOL | EOL |
| Pixel 4a (5G) | — | Nov 5, 2020 | Nov 5, 2023 | 1008 days past EOL | EOL |
| Pixel 5a | — | Aug 26, 2021 | Aug 1, 2024 | 738 days past EOL | EOL |
| Pixel 6 | — | Oct 28, 2021 | Oct 1, 2026 | 53 days remaining | Warning |
| Pixel 6 Pro | — | Oct 28, 2021 | Oct 1, 2026 | 53 days remaining | Warning |
| Pixel 6a | — | Jul 28, 2022 | Jul 1, 2027 | 326 days remaining | Active |
| Pixel 7 | — | Oct 13, 2022 | Oct 1, 2027 | 418 days remaining | Active |
| Pixel 7 Pro | — | Oct 13, 2022 | Oct 1, 2027 | 418 days remaining | Active |
| Pixel 7a | — | May 10, 2023 | May 1, 2028 | 631 days remaining | Active |
| Pixel Tablet | — | Jun 20, 2023 | Jun 1, 2028 | 662 days remaining | Active |
| Pixel Fold | — | Jun 28, 2023 | Jun 1, 2028 | 662 days remaining | Active |
| Pixel 8 | — | Oct 4, 2023 | Oct 1, 2030 | 1514 days remaining | Active |
| Pixel 8 Pro | — | Oct 4, 2023 | Oct 1, 2030 | 1514 days remaining | Active |
| Pixel 8a | — | May 14, 2024 | May 1, 2031 | 1726 days remaining | Active |
| Pixel 9 | — | Aug 22, 2024 | Aug 1, 2031 | 1818 days remaining | Active |
| Pixel 9 Pro XL | — | Aug 22, 2024 | Aug 1, 2031 | 1818 days remaining | Active |
| Pixel 9 Pro | — | Sep 4, 2024 | Sep 1, 2031 | 1849 days remaining | Active |
| Pixel 9 Pro Fold | — | Sep 4, 2024 | Sep 1, 2031 | 1849 days remaining | Active |
| Pixel 9a | — | Apr 10, 2025 | Apr 1, 2032 | 2062 days remaining | Active |
| Pixel 10 | — | Aug 28, 2025 | Aug 1, 2032 | 2184 days remaining | Active |
| Pixel 10 Pro XL | — | Aug 28, 2025 | Aug 1, 2032 | 2184 days remaining | Active |
| Pixel 10 Pro | — | Aug 28, 2025 | Aug 1, 2032 | 2184 days remaining | Active |
| Pixel 10 Pro Fold | — | Oct 4, 2025 | Oct 1, 2032 | 2245 days remaining | Active |
| Pixel 10a | — | Mar 5, 2026 | Mar 1, 2033 | 2396 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/pixel)
What does Google Pixel end of life mean for your organization?
When a version of Google Pixel reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Google Pixel should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Google Pixel reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Commercial extended support | Not available for Google Pixel from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →