TL;DR
FFmpeg 9.1, named “Gauss,” was released on Nov. 20, 2026, according to the project’s download page. The stable release branch was cut from the development branch on Oct. 24; the page lists new versions for seven FFmpeg libraries but does not detail individual features or fixes.
FFmpeg 9.1 “Gauss” was released on Nov. 20, 2026, the project’s download page says, making it the latest stable version from the 9.1 release branch. The release updates the version numbers of FFmpeg’s core libraries; the page supplied for the release does not describe specific new features, bug fixes or security changes.
Get everyday helpers delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
The project says the 9.1 branch was cut from master on Oct. 24, 2026, nearly four weeks before the release. The page lists these library versions: libavutil 61.19.100, libavcodec 63.24.100, libavformat 63.16.100, libavdevice 63.5.100, libavfilter 12.8.100, libswscale 10.5.100 and libswresample 7.6.100. These are version identifiers, not a description of what changed in each library.
FFmpeg says it provides source code, while links to compiled packages and executable files are provided by other sources. The project’s release page points users to its Git repository and notes that releases are cryptographically signed. Users downloading a release can verify its signature using the project’s published public key and verification instructions.
The project describes major releases as arriving approximately every six months, with point releases between them intended to include important bug fixes rather than new features. It says release branches receive selected changes from the development branch, where developers work actively. The page advises distributors and system integrators to use releases and encourages people compiling FFmpeg themselves to consider the development branch.
What the New Stable Branch Offers
FFmpeg is a multimedia framework used to process audio and video, and its libraries are incorporated into other software. A new stable release gives distributors and system integrators a defined set of source code and library versions to evaluate, package and support. That can matter to projects that need to track an established release rather than follow ongoing development.
The published page confirms the release and its library version numbers, but does not establish what practical changes users will see. Without release notes describing specific updates, readers should not infer from the version list alone that the release adds a particular codec, improves performance, fixes a named vulnerability or changes compatibility. Those details matter when developers decide whether and when to update software built on FFmpeg.
Products Worth Considering

Bose Home Speaker 500 Smart Speaker with Alexa, Black

Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation

Samsung 27-Inch Odyssey G5 QHD Gaming Monitor (G50F)
As an affiliate, we earn on qualifying purchases.
How FFmpeg Releases Are Managed
FFmpeg’s release page distinguishes between its development branch and stable release branches. The project says development snapshots receive changes more quickly, including features, bug fixes and security patches, while release branches receive selected changes. It characterizes snapshots as working well most of the time, but that statement is the project’s description, not an independent guarantee for every user or setup.
The previous listed release in the 9.x series was FFmpeg 9.0.2 “Lei,” released Sept. 18, 2026. Its branch was cut from master on June 26. The project also lists other maintained release lines, including 8.1.3, 8.0.3, 7.1.5 and 6.1.6. Multiple branches allow users and software distributors to choose among versions, although the page does not specify support deadlines for those branches.
““FFmpeg only provides source code.””
— FFmpeg project download page
Release Notes Leave Changes Unspecified
The supplied release listing confirms the release date, branch cut date and library versions, but does not include a change log for FFmpeg 9.1. It is not clear from that page which features were added, which bugs were addressed, whether there are security fixes, or whether applications need code changes to work with the new library versions. No performance benchmarks or compatibility guidance are provided there either.
The listing also does not identify specific operating systems, package maintainers or application vendors that have already shipped builds based on 9.1. FFmpeg itself says it supplies source code, so the availability and timing of compiled packages depend on third parties. Readers should consult the project’s release materials and their distribution or software vendor for details relevant to a particular build.
Verify Builds Before Updating
People who want the release can obtain the source code through FFmpeg’s Git repository or use compiled packages supplied by linked third-party providers. The project recommends verifying release authenticity: its page explains how to import the public signing key and check a downloaded tarball’s signature. A successful signature check confirms the file matches the signer’s signature; it does not explain the release’s technical changes.
For maintainers, the next practical step is to review a full change log when available, test the new library versions against their software and check package availability with their distribution or vendor. Developers who need the project’s latest working changes can consider the development branch, while weighing the project’s distinction between that branch and its stable releases. The download page does not announce a date for a subsequent 9.1 point release.
Key Questions
When was FFmpeg 9.1 ‘Gauss’ released?
FFmpeg’s download page lists the release date as Nov. 20, 2026.
What changed in FFmpeg 9.1?
The supplied release listing gives updated versions for seven FFmpeg libraries but does not provide a feature list, bug-fix summary or security advisory. The specific changes cannot be confirmed from that material alone.
Does FFmpeg provide ready-to-run installers?
The project says it provides source code only. Its download page links to other sources that offer compiled packages and executable files.
Should users choose the stable release or development branch?
FFmpeg describes its releases as intended for distributors and system integrators, and says development branch changes arrive more quickly. The appropriate choice depends on a user’s software, testing needs and tolerance for changes; the project page does not give individualized upgrade advice.
How can I check that a downloaded release is authentic?
FFmpeg publishes a public signing key and instructions for verifying release signatures. Users can follow those instructions to check a downloaded source archive before using it.
Source: ffmpeg.org
