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: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
6000.6 Aug 31, 2026—No—6000.6.7f1—Active
6000.5 Jun 15, 2026—Aug 31, 202653d ago6000.5.11f1—EOL
6000.4 Mar 18, 2026—Jun 17, 2026128d ago6000.4.12f1—EOL
6000.3 LTSDec 4, 2025—Dec 4, 2027in 407d6000.3.27f1—Active
6000.2 Aug 12, 2025—Dec 4, 2025323d ago6000.2.15f1—EOL
6000.1 Apr 23, 2025—Aug 12, 2025437d ago6000.1.17f1—EOL
6000.0 LTSApr 29, 2024—Oct 16, 20267d ago6000.0.85f1—EOL
2023.2 Nov 14, 2023—Apr 29, 2024907d ago2023.2.22f1—EOL
2023.1 Jun 12, 2023—Nov 13, 20231075d ago2023.1.22f1—EOL
2022.3 LTSMay 30, 2023—May 7, 2025534d ago2022.3.62f3—EOL
2022.2 Dec 7, 2022—Jun 12, 20231229d ago2022.2.23f1—EOL
2022.1 May 9, 2022—Dec 6, 20221417d ago2022.1.25f1—EOL
2021.3 Apr 11, 2022—Feb 18, 2025612d ago2021.3.45f2—EOL
2021 LTSApr 11, 2022—Feb 18, 2025612d ago2021.3.45f2—EOL
2021.2 Oct 25, 2021—Apr 5, 20221662d ago2021.2.20f1—EOL
2021.1 Mar 22, 2021—Nov 4, 20221449d ago2021.1.29f1—EOL
2020 LTSJul 20, 2020—May 5, 20231267d ago2020.3.49f1—EOL
2019 LTSApr 8, 2019—Jun 16, 20221590d ago2019.4.41f2—EOL
2018 LTSApr 26, 2018—Jun 17, 20211954d ago2018.4.36f1—EOL
2017 LTSJun 26, 2017—May 18, 20202349d ago2017.4.40f1—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions