Unity End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Unity versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2017 LTS | 2017.4.40f1 | Jun 26, 2017 | May 18, 2020 | 2227 days past EOL | EOL |
| 2018 LTS | 2018.4.36f1 | Apr 26, 2018 | Jun 17, 2021 | 1832 days past EOL | EOL |
| 2019 LTS | 2019.4.41f2 | Apr 8, 2019 | Jun 16, 2022 | 1468 days past EOL | EOL |
| 2020 LTS | 2020.3.49f1 | Jul 20, 2020 | May 5, 2023 | 1145 days past EOL | EOL |
| 2021.1 | 2021.1.29f1 | Mar 22, 2021 | Nov 4, 2022 | 1327 days past EOL | EOL |
| 2021.2 | 2021.2.20f1 | Oct 25, 2021 | Apr 5, 2022 | 1540 days past EOL | EOL |
| 2021.3 | 2021.3.45f2 | Apr 11, 2022 | Feb 18, 2025 | 490 days past EOL | EOL |
| 2021 LTS | 2021.3.45f2 | Apr 11, 2022 | Feb 18, 2025 | 490 days past EOL | EOL |
| 2022.1 | 2022.1.25f1 | May 9, 2022 | Dec 6, 2022 | 1295 days past EOL | EOL |
| 2022.2 | 2022.2.23f1 | Dec 7, 2022 | Jun 12, 2023 | 1107 days past EOL | EOL |
| 2022.3 LTS | 2022.3.62f3 | May 30, 2023 | May 7, 2025 | 412 days past EOL | EOL |
| 2023.1 | 2023.1.22f1 | Jun 12, 2023 | Nov 13, 2023 | 953 days past EOL | EOL |
| 2023.2 | 2023.2.22f1 | Nov 14, 2023 | Apr 29, 2024 | 785 days past EOL | EOL |
| 6000.0 LTS | 6000.0.77f1 | Apr 29, 2024 | Oct 16, 2026 | 115 days remaining | Warning |
| 6000.1 | 6000.1.17f1 | Apr 23, 2025 | Aug 12, 2025 | 315 days past EOL | EOL |
| 6000.2 | 6000.2.15f1 | Aug 12, 2025 | Dec 4, 2025 | 201 days past EOL | EOL |
| 6000.3 LTS | 6000.3.18f1 | Dec 4, 2025 | Dec 4, 2027 | 529 days remaining | Active |
| 6000.4 | 6000.4.12f1 | Mar 18, 2026 | Jun 17, 2026 | 6 days past EOL | EOL |
| 6000.5 | 6000.5.0f1 | Jun 15, 2026 | TBD | Supported | Active |
What does Unity end of life mean for your organization?
When a version of Unity 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 Unity 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Unity versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →