Pixel End of Life Dates
other
Digital imaging relies heavily on the concept of a picture element, which is the smallest addressable physical element of a raster image or the smallest controllable element of a display device or dot matrix printer, commonly referred to as a pixel. This fundamental component has been a cornerstone of digital imaging since its inception, with the first pixelated images emerging in the 1960s. The maintenance of pixel-related technology is overseen by various organizations and communities, who work together to ensure that developers have access to the most up-to-date and secure tools. Developers utilize pixel technology to create a wide range of applications, from graphics editors to video games, due to its versatility and widespread adoption.
The end-of-life landscape for pixel technology is complex, with a total of 34 versions having been released over the years. Of these, 14 versions have reached their end-of-life, while 20 remain active and supported. The next version to expire is 6pro, which is scheduled to reach its end-of-life on 2026-10-01, marking an important milestone in the evolution of pixel technology. This change will likely have significant implications for developers who rely on this version, as they will need to migrate to a newer, supported version to ensure continued security and compatibility. The most recent end-of-life date was 2024-08-01, when version 5a was retired, highlighting the ongoing process of version retirement and replacement.
The security picture for pixel technology is remarkably clear, with a total of 0 CVEs tracked and 0 critical CVEs reported. This indicates that pixel technology is not currently a significant target for malicious actors, and developers can utilize it with a high degree of confidence. As a result, there is no most affected version, and no Known Exploited Vulnerability status has been assigned. Given this favorable security landscape, developers can focus on leveraging pixel technology to create innovative applications, without the burden of mitigating significant security risks, and can instead concentrate on optimizing performance and functionality.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 10a | Mar 5, 2026 | Mar 1, 2033 | Mar 1, 2033 | in 2412d | — | — | Active | |
| 10profold | Oct 4, 2025 | Oct 1, 2032 | Oct 1, 2032 | in 2261d | — | — | Active | |
| 10pro | Aug 28, 2025 | Aug 1, 2032 | Aug 1, 2032 | in 2200d | — | — | Active | |
| 10 | Aug 28, 2025 | Aug 1, 2032 | Aug 1, 2032 | in 2200d | — | — | Active | |
| 10proxl | Aug 28, 2025 | Aug 1, 2032 | Aug 1, 2032 | in 2200d | — | — | Active | |
| 9a | Apr 10, 2025 | Apr 1, 2032 | Apr 1, 2032 | in 2078d | — | — | Active | |
| 9profold | Sep 4, 2024 | Sep 1, 2031 | Sep 1, 2031 | in 1865d | — | — | Active | |
| 9pro | Sep 4, 2024 | Sep 1, 2031 | Sep 1, 2031 | in 1865d | — | — | Active | |
| 9 | Aug 22, 2024 | Aug 1, 2031 | Aug 1, 2031 | in 1834d | — | — | Active | |
| 9proxl | Aug 22, 2024 | Aug 1, 2031 | Aug 1, 2031 | in 1834d | — | — | Active | |
| 8a | May 14, 2024 | May 1, 2031 | May 1, 2031 | in 1742d | — | — | Active | |
| 8 | Oct 4, 2023 | Oct 1, 2030 | Oct 1, 2030 | in 1530d | — | — | Active | |
| 8pro | Oct 4, 2023 | Oct 1, 2030 | Oct 1, 2030 | in 1530d | — | — | Active | |
| fold | Jun 28, 2023 | Jun 1, 2028 | Jun 1, 2028 | in 678d | — | — | Active | |
| tablet | Jun 20, 2023 | Jun 1, 2028 | Jun 1, 2028 | in 678d | — | — | Active | |
| 7a | May 10, 2023 | May 1, 2028 | May 1, 2028 | in 647d | — | — | Active | |
| 7pro | Oct 13, 2022 | Oct 1, 2027 | Oct 1, 2027 | in 434d | — | — | Active | |
| 7 | Oct 13, 2022 | Oct 1, 2027 | Oct 1, 2027 | in 434d | — | — | Active | |
| 6a | Jul 28, 2022 | Jul 1, 2027 | Jul 1, 2027 | in 342d | — | — | Active | |
| 6 | Oct 28, 2021 | Oct 1, 2026 | Oct 1, 2026 | in 69d | — | — | EOL soon | |
| 6pro | Oct 28, 2021 | Oct 1, 2026 | Oct 1, 2026 | in 69d | — | — | EOL soon | |
| 5a | Aug 26, 2021 | Aug 1, 2024 | Aug 1, 2024 | 722d ago | — | — | EOL | |
| 4a-5g | Nov 5, 2020 | Nov 5, 2023 | Nov 5, 2023 | 992d ago | — | — | EOL | |
| 5 | Oct 15, 2020 | Nov 5, 2023 | Nov 5, 2023 | 992d ago | — | — | EOL | |
| 4a | Aug 20, 2020 | Aug 5, 2023 | Aug 5, 2023 | 1084d ago | — | — | EOL | |
| 4 | Oct 24, 2019 | Oct 5, 2022 | Oct 5, 2022 | 1388d ago | — | — | EOL | |
| 4xl | Oct 24, 2019 | Oct 5, 2022 | Oct 5, 2022 | 1388d ago | — | — | EOL | |
| 3axl | May 15, 2019 | May 5, 2022 | May 5, 2022 | 1541d ago | — | — | EOL | |
| 3a | May 15, 2019 | May 5, 2022 | May 5, 2022 | 1541d ago | — | — | EOL | |
| 3 | Oct 18, 2018 | Oct 5, 2021 | Oct 5, 2021 | 1753d ago | — | — | EOL | |
| 3xl | Oct 18, 2018 | Oct 5, 2021 | Oct 5, 2021 | 1753d ago | — | — | EOL | |
| 2 | Oct 17, 2017 | Oct 5, 2020 | Oct 5, 2020 | 2118d ago | — | — | EOL | |
| 2xl | Oct 17, 2017 | Oct 5, 2020 | Oct 5, 2020 | 2118d ago | — | — | EOL | |
| 1 | Oct 20, 2016 | Oct 6, 2019 | Oct 6, 2019 | 2483d ago | — | — | EOL | |
| 1xl | Oct 20, 2016 | Oct 6, 2019 | Oct 6, 2019 | 2483d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
