← ← Back to all products
Strapi
Active
CMS & ContentLatest Version: 5.48.0Latest Release: Jun 10, 2026
Strapi is an open-source headless CMS built with Node.js for building APIs and managing content.
Support summary
Strapi currently has supported cycles. Track the next EOL date and validate upgrades before your change window.
What do EOL and support statuses mean?Next EOL
No announced EOL date is currently listed.
Supported cycles
1
0 lts
Versions
3
Latest Version
5.48.0
Active Support
1
EOL
2
Lifecycle Timeline
Today ↓
5
5
4
4
3
3
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 5 | Sep 18, 2024 | Yes | No | 5.48.0 | No | Active |
| 4 | Nov 30, 2021 | Oct 31, 2025 | Apr 30, 2026 | 4.26.2 | No | EOL |
| 3 | May 26, 2020 | May 31, 2022 | Dec 31, 2022 | 3.6.11 | No | EOL |
Data sources
Sources
Last verified
Jun 24, 2026
Community-maintained lifecycle data. Verify against official release notes before production migration.
Frequently Asked Questions
Which versions of Strapi have reached end of life?
The following Strapi versions have reached end of life and no longer receive security updates: 4, 3. It is recommended to upgrade to a supported version.
Is it safe to continue using Strapi 4?
Strapi 4 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Strapi?
The latest version of Strapi is 5.48.0, released in the 5 release cycle.
How many versions of Strapi are currently supported?
Strapi currently has 1 actively supported version(s): 5.
When does Strapi 5 reach end of life?
Strapi 5 does not have a specific end-of-life date announced yet.
What should I do when Strapi reaches end of life?
When a Strapi version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.