FFmpeg End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all FFmpeg versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.5 | 0.5.15 | Mar 2, 2009 | Nov 29, 2014 | 4224 days past EOL | EOL |
| 0.6 | 0.6.7 | May 4, 2010 | Sep 23, 2013 | 4656 days past EOL | EOL |
| 0.7 | 0.7.17 | Jun 21, 2011 | Mar 12, 2015 | 4121 days past EOL | EOL |
| 0.8 | 0.8.15 | Jun 21, 2011 | Oct 6, 2013 | 4643 days past EOL | EOL |
| 0.9 | 0.9.4 | Dec 11, 2011 | Mar 21, 2014 | 4477 days past EOL | EOL |
| 0.10 | 0.10.16 | Jan 26, 2012 | Mar 12, 2015 | 4121 days past EOL | EOL |
| 0.11 | 0.11.5 | May 25, 2012 | Mar 10, 2014 | 4488 days past EOL | EOL |
| 1.0 | 1.0.10 | Sep 28, 2012 | Jul 20, 2014 | 4356 days past EOL | EOL |
| 1.1 | 1.1.16 | Jan 6, 2013 | Mar 13, 2015 | 4120 days past EOL | EOL |
| 1.2 | 1.2.12 | Mar 15, 2013 | Feb 12, 2015 | 4149 days past EOL | EOL |
| 2.0 | 2.0.7 | Jul 10, 2013 | Jun 10, 2015 | 4031 days past EOL | EOL |
| 2.1 | 2.1.8 | Oct 28, 2013 | Apr 30, 2015 | 4072 days past EOL | EOL |
| 2.2 | 2.2.16 | Mar 23, 2014 | Jun 18, 2015 | 4023 days past EOL | EOL |
| 2.3 | 2.3.6 | Jul 16, 2014 | Jan 6, 2015 | 4186 days past EOL | EOL |
| 2.4 | 2.4.14 | Sep 14, 2014 | Dec 31, 2017 | 3096 days past EOL | EOL |
| 2.5 | 2.5.11 | Dec 4, 2014 | Feb 2, 2016 | 3794 days past EOL | EOL |
| 2.6 | 2.6.9 | Mar 7, 2015 | May 3, 2016 | 3703 days past EOL | EOL |
| 2.7 | 2.7.7 | Jun 10, 2015 | Apr 30, 2016 | 3706 days past EOL | EOL |
| 2.8 | 2.8.22 | Sep 9, 2015 | TBD | Supported | Active |
| 3.0 | 3.0.12 | Feb 15, 2016 | Oct 28, 2018 | 2795 days past EOL | EOL |
| 3.1 | 3.1.11 | Jun 27, 2016 | Sep 25, 2017 | 3193 days past EOL | EOL |
| 3.2 | 3.2.19 | Oct 27, 2016 | Oct 28, 2022 | 1334 days past EOL | EOL |
| 3.3 | 3.3.9 | Apr 13, 2017 | Nov 18, 2018 | 2774 days past EOL | EOL |
| 3.4 | 3.4.14 | Oct 15, 2017 | TBD | Supported | Active |
| 4.0 | 4.0.6 | Apr 20, 2018 | Jul 3, 2020 | 2181 days past EOL | EOL |
| 4.1 | 4.1.11 | Nov 6, 2018 | Jul 21, 2024 | 702 days past EOL | EOL |
| 4.2 | 4.2.11 | Aug 5, 2019 | TBD | Supported | Active |
| 4.3 | 4.3.9 | Jun 15, 2020 | TBD | Supported | Active |
| 4.4 | 4.4.8 | Apr 8, 2021 | TBD | Supported | Active |
| 5.0 | 5.0.3 | Jan 14, 2022 | Apr 2, 2023 | 1178 days past EOL | EOL |
| 5.1 LTS | 5.1.10 | Jul 22, 2022 | TBD | Supported | Active |
| 6.0 | 6.0.1 | Feb 27, 2023 | Jul 11, 2024 | 712 days past EOL | EOL |
| 6.1 | 6.1.6 | Nov 11, 2023 | TBD | Supported | Active |
| 7.0 | 7.0.3 | Apr 5, 2024 | TBD | Supported | Active |
| 7.1 LTS | 7.1.5 | Sep 30, 2024 | TBD | Supported | Active |
| 8.0 | 8.0.3 | Aug 22, 2025 | TBD | Supported | Active |
| 8.1 | 8.1.2 | Mar 16, 2026 | TBD | Supported | Active |
What does FFmpeg end of life mean for your organization?
When a version of FFmpeg 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 FFmpeg 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL FFmpeg versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →