← ← Back to all products
BigBlueButton
Active
CMS & ContentLatest Version: 3.0.35Latest Release: Aug 13, 2026
BigBlueButton is an open-source web conferencing system designed for online learning.
Support summary
BigBlueButton 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
4
Latest Version
3.0.35
Active Support
1
EOL
3
Lifecycle Timeline
Today ↓
3.0
3.0
2.7
2.7
2.6
2.6
2.5
2.5
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 3.0 | Feb 28, 2025 | Yes | No | 3.0.35 | No | Active |
| 2.7 | Sep 6, 2023 | No | May 31, 2025 | 2.7.16 | No | EOL |
| 2.6 | Mar 20, 2023 | No | Feb 28, 2025 | 2.6.18 | No | EOL |
| 2.5 | Jun 9, 2022 | No | Sep 6, 2023 | 2.5.20 | No | EOL |
Data sources
Frequently Asked Questions
Which versions of BigBlueButton have reached end of life?
The following BigBlueButton versions have reached end of life and no longer receive security updates: 2.7, 2.6, 2.5. It is recommended to upgrade to a supported version.
Is it safe to continue using BigBlueButton 2.7?
BigBlueButton 2.7 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 BigBlueButton?
The latest version of BigBlueButton is 3.0.35, released in the 3.0 release cycle.
How many versions of BigBlueButton are currently supported?
BigBlueButton currently has 1 actively supported version(s): 3.0.
When does BigBlueButton 3.0 reach end of life?
BigBlueButton 3.0 does not have a specific end-of-life date announced yet.
What should I do when BigBlueButton reaches end of life?
When a BigBlueButton 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.