NVIDIA GPU End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all NVIDIA GPU versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| Consumer Fahrenheit (NVx) | — | Jun 15, 1998 | Mar 11, 2005 | 7821 days past EOL | EOL |
| Consumer Celsius (NV1x) | — | Oct 11, 1999 | Apr 14, 2005 | 7787 days past EOL | EOL |
| Consumer Kelvin (NV1x, NV2x) | — | Feb 27, 2001 | Nov 2, 2006 | 7220 days past EOL | EOL |
| Consumer Rankine (NV3x) | — | Jan 27, 2003 | Jun 23, 2008 | 6621 days past EOL | EOL |
| Consumer Curie (NV4x, G7x) | — | Apr 14, 2004 | Feb 24, 2015 | 4184 days past EOL | EOL |
| Consumer Tesla (Cxx, G8x, G9x, GT2xx, ION) | — | Nov 8, 2006 | Dec 14, 2016 | 3525 days past EOL | EOL |
| Consumer Fermi (GF1xx)* | — | Mar 26, 2010 | Mar 10, 2018 | 3074 days past EOL | EOL |
| Professional Fermi (GF1xx)** | — | Jul 23, 2010 | Dec 31, 2022 | 1317 days past EOL | EOL |
| Mobile Consumer Kepler (GKxxx) | — | Mar 22, 2012 | Apr 11, 2019 | 2677 days past EOL | EOL |
| Mobile Professional Kepler (GKxxx) | — | Mar 22, 2012 | Mar 1, 2022 | 1622 days past EOL | EOL |
| Consumer Kepler (GKxxx) | — | Mar 22, 2012 | Sep 1, 2024 | 707 days past EOL | EOL |
| Professional Kepler (GKxxx) | — | Mar 1, 2013 | Sep 1, 2024 | 707 days past EOL | EOL |
| Consumer Maxwell (GMxxx) | — | Sep 19, 2014 | Oct 31, 2028 | 814 days remaining | Active |
| Mobile Consumer Maxwell (GMxxx) | — | Oct 7, 2014 | Oct 31, 2028 | 814 days remaining | Active |
| Professional Maxwell (GMxxx) | — | Jun 29, 2015 | Oct 31, 2028 | 814 days remaining | Active |
| Mobile Professional Maxwell (GMxxx) | — | Aug 18, 2015 | Oct 31, 2028 | 814 days remaining | Active |
| Professional Pascal (GP10x) | — | Apr 5, 2016 | Oct 31, 2028 | 814 days remaining | Active |
| Consumer Pascal (GP10x) | — | May 27, 2016 | Oct 31, 2028 | 814 days remaining | Active |
| Mobile Consumer Pascal (GP10x) | — | Aug 15, 2016 | Oct 31, 2028 | 814 days remaining | Active |
| Mobile Professional Pascal (GP10x) | — | Feb 6, 2017 | Oct 31, 2028 | 814 days remaining | Active |
| Professional Volta (GV100) | — | Dec 7, 2017 | Oct 31, 2028 | 814 days remaining | Active |
| Professional Turing (TU1xX) | — | Aug 13, 2018 | TBD | Supported | Active |
| Consumer Turing (TU1xX) | — | Sep 20, 2018 | TBD | Supported | Active |
| Mobile Consumer Turing (TU1xX) | — | Jan 29, 2019 | TBD | Supported | Active |
| Mobile Professional Turing (TU1xX) | — | May 27, 2019 | TBD | Supported | Active |
| Consumer Ampere (GA10x) | — | Sep 1, 2020 | TBD | Supported | Active |
| Professional Ampere (GA10x) | — | Oct 5, 2020 | TBD | Supported | Active |
| Mobile Consumer Ampere (GA10x) | — | Jan 12, 2021 | TBD | Supported | Active |
| Mobile Professional Ampere (GA10x) | — | Apr 12, 2021 | TBD | Supported | Active |
| Consumer Ada Lovelace (AD1xx) | — | Sep 20, 2022 | TBD | Supported | Active |
| Professional Ada Lovelace (AD1xx) | — | Oct 13, 2022 | TBD | Supported | Active |
| Mobile Consumer Ada Lovelace (AD10x) | — | Feb 8, 2023 | TBD | Supported | Active |
| Consumer Blackwell (GB20x) | — | Jan 30, 2025 | TBD | Supported | Active |
| Mobile Consumer Blackwell (GB20x) | — | Jan 30, 2025 | TBD | Supported | Active |
| Professional Blackwell (GB20x) | — | Jan 30, 2025 | TBD | Supported | Active |
| Mobile Professional Blackwell (GB20x) | — | Jan 30, 2025 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/nvidia-gpu)
What does NVIDIA GPU end of life mean for your organization?
When a version of NVIDIA GPU 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 NVIDIA GPU 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 NVIDIA GPU 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 NVIDIA GPU 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 →