← ← Back to all products
Backdrop
Active
CMS & Content Latest Version: 1.33.1 Latest Release: Jan 27, 2026
Backdrop CMS is a free, open-source CMS for building websites, forked from Drupal 7.
Versions
7
Latest Version
1.33.1
Active Support
2
EOL
5
Lifecycle Timeline
Today ↓
1.33
1.33
1.32
1.32
1.31
1.31
1.30
1.30
1.29
1.29
1.28
1.28
1.27
1.27
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 1.33 | Jan 16, 2026 | - | No | 1.33.1 | No | Active |
| 1.32 | Sep 16, 2025 | - | No | 1.32.2 | No | Active |
| 1.31 | May 15, 2025 | - | Jan 16, 2026 | 1.31.2 | No | EOL |
| 1.30 | Jan 15, 2025 | - | Sep 16, 2025 | 1.30.3 | No | EOL |
| 1.29 | Sep 15, 2024 | - | May 15, 2025 | 1.29.5 | No | EOL |
| 1.28 | May 15, 2024 | - | Jan 15, 2025 | 1.28.5 | No | EOL |
| 1.27 | Jan 15, 2024 | - | Sep 15, 2024 | 1.27.3 | No | EOL |
Frequently Asked Questions
Which versions of Backdrop have reached end of life?
The following Backdrop versions have reached end of life and no longer receive security updates: 1.31, 1.30, 1.29, 1.28, 1.27. It is recommended to upgrade to a supported version.
Is it safe to continue using Backdrop 1.31?
Backdrop 1.31 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 Backdrop?
The latest version of Backdrop is 1.33.1, released in the 1.33 release cycle.
How many versions of Backdrop are currently supported?
Backdrop currently has 2 actively supported version(s): 1.33, 1.32.
When does Backdrop 1.33 reach end of life?
Backdrop 1.33 does not have a specific end-of-life date announced yet.
What should I do when Backdrop reaches end of life?
When a Backdrop 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.