Unity End of Life Dates

other

Developers working with game engines require a reliable way to stay informed about the lifecycle of their tools, and this is where Unity's end-of-life tracking comes into play. Created to simplify the process of managing upgrades and support timelines, this resource has been a vital tool for developers since its inception. The team behind Unity maintains a rigorous schedule of updates and support, ensuring that users can plan their projects with confidence. With a vast array of versions to keep track of, developers rely on this resource to navigate the complex landscape of Unity's lifecycle, from initial release to eventual end-of-life.

The Unity ecosystem is vast, with 18 versions currently tracked, of which 15 have already reached end-of-life. Only 3 versions remain actively supported, with the latest stable version being 6000.0.77f1. Looking ahead, the next version to reach end-of-life is 6000.0, which is scheduled to occur on 2026-10-16. This information is crucial for developers, as it allows them to plan their upgrades and migrations well in advance. The most recent version to reach end-of-life was 6000.2, which occurred on 2025-12-04, marking an important milestone in the Unity lifecycle.

From a security perspective, Unity's track record is impeccable, with 0 CVEs tracked to date. This means that there are no known critical vulnerabilities affecting any version of Unity, and as a result, there is no most affected version to speak of. With no critical CVEs to contend with, developers can focus on their projects without worrying about potential security risks. To maintain this level of security, developers should continue to monitor the end-of-life dates and plan their upgrades accordingly, ensuring that they stay within the supported versions and take advantage of the latest security patches and updates.

Last updated: Jul 24, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
6000.5 Jun 15, 2026No6000.5.5f1Active
6000.4 Mar 18, 2026Jun 17, 202637d ago6000.4.12f1EOL
6000.3 LTSDec 4, 2025Dec 4, 2027in 498d6000.3.20f1Active
6000.2 Aug 12, 2025Dec 4, 2025232d ago6000.2.15f1EOL
6000.1 Apr 23, 2025Aug 12, 2025346d ago6000.1.17f1EOL
6000.0 LTSApr 29, 2024Oct 16, 2026in 84d6000.0.80f1EOL soon
2023.2 Nov 14, 2023Apr 29, 2024816d ago2023.2.22f1EOL
2023.1 Jun 12, 2023Nov 13, 2023984d ago2023.1.22f1EOL
2022.3 LTSMay 30, 2023May 7, 2025443d ago2022.3.62f3EOL
2022.2 Dec 7, 2022Jun 12, 20231138d ago2022.2.23f1EOL
2022.1 May 9, 2022Dec 6, 20221326d ago2022.1.25f1EOL
2021 LTSApr 11, 2022Feb 18, 2025521d ago2021.3.45f2EOL
2021.3 Apr 11, 2022Feb 18, 2025521d ago2021.3.45f2EOL
2021.2 Oct 25, 2021Apr 5, 20221571d ago2021.2.20f1EOL
2021.1 Mar 22, 2021Nov 4, 20221358d ago2021.1.29f1EOL
2020 LTSJul 20, 2020May 5, 20231176d ago2020.3.49f1EOL
2019 LTSApr 8, 2019Jun 16, 20221499d ago2019.4.41f2EOL
2018 LTSApr 26, 2018Jun 17, 20211863d ago2018.4.36f1EOL
2017 LTSJun 26, 2017May 18, 20202258d ago2017.4.40f1EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions