Godot · Lifecycle Status

Godot End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Godot versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Godot 1.0 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
1.0
1.0 series
Next EOL
None upcoming
Active Versions
7
of 17 total
EOL Versions
10
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 2015201620172018201920202021202220232024202520261.02.02.13.03.13.23.33.43.54.04.14.24.33.64.44.54.6TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1.0 1.0 Dec 15, 2014 Supported indefinitely Supported Active
2.0 2.0.4.1 Feb 22, 2016 Supported indefinitely Supported Active
2.1 LTS 2.1.6 Aug 9, 2016 Supported indefinitely Supported Active
3.0 3.0.6 Jan 29, 2018 Supported indefinitely Supported Active
3.1 3.1.2 Mar 13, 2019 Jan 29, 2020 2292 days past EOL EOL
3.2 3.2.3 Jan 29, 2020 Apr 21, 2021 1844 days past EOL EOL
3.3 3.3.4 Apr 21, 2021 Nov 5, 2021 1646 days past EOL EOL
3.4 3.4.5 Nov 5, 2021 Aug 5, 2022 1373 days past EOL EOL
3.5 LTS 3.5.3 Aug 5, 2022 Oct 23, 2025 198 days past EOL EOL
4.0 4.0.4 Mar 1, 2023 Nov 29, 2023 892 days past EOL EOL
4.1 4.1.4 Jul 5, 2023 Mar 3, 2025 432 days past EOL EOL
4.2 4.2.2 Nov 29, 2023 Oct 9, 2025 212 days past EOL EOL
4.3 4.3 Aug 15, 2024 Oct 23, 2025 198 days past EOL EOL
3.6 LTS 3.6.2 Sep 8, 2024 Already EOL Supported Active
4.4 4.4.1 Mar 3, 2025 Mar 26, 2026 44 days past EOL EOL
4.5 4.5.2 Sep 15, 2025 Already EOL Supported Active
4.6 4.6.2 Jan 26, 2026 Already EOL Supported Active

What does Godot end of life mean for your organization?

When a Godot version 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 Godot 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Godot?
See the full table above for all Godot version EOL dates.
What is the latest supported version of Godot?
The latest active version of Godot is 1.0. Always verify against the table above as support windows can change.
What happens when Godot reaches end of life?
When Godot reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Godot?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Godot versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →