← ← Back to all products
FFmpeg
Active
Tools & MonitoringLatest Version: 8.1.2Latest Release: Jun 17, 2026
FFmpeg is a complete, cross-platform solution for recording, converting, and streaming audio and video.
Support summary
FFmpeg 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
7
2 lts
Versions
37
Latest Version
8.1.2
Active Support
7
EOL
30
Lifecycle Timeline
Today ↓
8.1
8.1
8.0
8.0
7.1
7.1
7.0
7.0
6.1
6.1
6.0
6.0
5.1
5.1
5.0
5.0
4.4
4.4
4.3
4.3
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 8.1 | Mar 16, 2026 | Yes | No | 8.1.2 | No | Active |
| 8.0 | Aug 22, 2025 | Yes | No | 8.0.3 | No | Active |
| 7.1 | Sep 30, 2024 | Yes | No | 7.1.5 | Yes | Active |
| 7.0 | Apr 5, 2024 | Yes | No | 7.0.3 | No | Active |
| 6.1 | Nov 11, 2023 | Yes | No | 6.1.6 | No | Active |
| 6.0 | Feb 27, 2023 | No | Jul 11, 2024 | 6.0.1 | No | EOL |
| 5.1 | Jul 22, 2022 | Yes | No | 5.1.10 | Yes | Active |
| 5.0 | Jan 14, 2022 | No | Apr 2, 2023 | 5.0.3 | No | EOL |
| 4.4 | Apr 8, 2021 | Yes | No | 4.4.8 | No | Active |
| 4.3 | Jun 15, 2020 | No | Jun 21, 2026 | 4.3.9 | No | EOL |
| 4.2 | Aug 5, 2019 | No | Jun 21, 2026 | 4.2.11 | No | EOL |
| 4.1 | Nov 6, 2018 | No | Jul 21, 2024 | 4.1.11 | No | EOL |
| 4.0 | Apr 20, 2018 | No | Jul 3, 2020 | 4.0.6 | No | EOL |
| 3.4 | Oct 15, 2017 | No | Jun 21, 2026 | 3.4.14 | No | EOL |
| 3.3 | Apr 13, 2017 | No | Nov 18, 2018 | 3.3.9 | No | EOL |
| 3.2 | Oct 27, 2016 | No | Oct 28, 2022 | 3.2.19 | No | EOL |
| 3.1 | Jun 27, 2016 | No | Sep 25, 2017 | 3.1.11 | No | EOL |
| 3.0 | Feb 15, 2016 | No | Oct 28, 2018 | 3.0.12 | No | EOL |
| 2.8 | Sep 9, 2015 | No | Jun 21, 2026 | 2.8.22 | No | EOL |
| 2.7 | Jun 10, 2015 | No | Apr 30, 2016 | 2.7.7 | No | EOL |
| 2.6 | Mar 7, 2015 | No | May 3, 2016 | 2.6.9 | No | EOL |
| 2.5 | Dec 4, 2014 | No | Feb 2, 2016 | 2.5.11 | No | EOL |
| 2.4 | Sep 14, 2014 | No | Dec 31, 2017 | 2.4.14 | No | EOL |
| 2.3 | Jul 16, 2014 | No | Jan 6, 2015 | 2.3.6 | No | EOL |
| 2.2 | Mar 23, 2014 | No | Jun 18, 2015 | 2.2.16 | No | EOL |
| 2.1 | Oct 28, 2013 | No | Apr 30, 2015 | 2.1.8 | No | EOL |
| 2.0 | Jul 10, 2013 | No | Jun 10, 2015 | 2.0.7 | No | EOL |
| 1.2 | Mar 15, 2013 | No | Feb 12, 2015 | 1.2.12 | No | EOL |
| 1.1 | Jan 6, 2013 | No | Mar 13, 2015 | 1.1.16 | No | EOL |
| 1.0 | Sep 28, 2012 | No | Jul 20, 2014 | 1.0.10 | No | EOL |
| 0.11 | May 25, 2012 | No | Mar 10, 2014 | 0.11.5 | No | EOL |
| 0.10 | Jan 26, 2012 | No | Mar 12, 2015 | 0.10.16 | No | EOL |
| 0.9 | Dec 11, 2011 | No | Mar 21, 2014 | 0.9.4 | No | EOL |
| 0.8 | Jun 21, 2011 | No | Oct 6, 2013 | 0.8.15 | No | EOL |
| 0.7 | Jun 21, 2011 | No | Mar 12, 2015 | 0.7.17 | No | EOL |
| 0.6 | May 4, 2010 | No | Sep 23, 2013 | 0.6.7 | No | EOL |
| 0.5 | Mar 2, 2009 | No | Nov 29, 2014 | 0.5.15 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of FFmpeg have reached end of life?
The following FFmpeg versions have reached end of life and no longer receive security updates: 6.0, 5.0, 4.3, 4.2, 4.1, 4.0, 3.4, 3.3 (and 22 more). It is recommended to upgrade to a supported version.
Is it safe to continue using FFmpeg 6.0?
FFmpeg 6.0 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 FFmpeg?
The latest version of FFmpeg is 8.1.2, released in the 8.1 release cycle.
How many versions of FFmpeg are currently supported?
FFmpeg currently has 7 actively supported version(s): 8.1, 8.0, 7.1, 7.0, 6.1, 5.1, 4.4.
When does FFmpeg 8.1 reach end of life?
FFmpeg 8.1 does not have a specific end-of-life date announced yet.
What should I do when FFmpeg reaches end of life?
When a FFmpeg 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.