Futureweb

Open Source

FFmpeg's changelog has a 9.1 section. The release index does not have a 9.1 tarball.

Phoronix says the FFmpeg 9.1 release dance is underway. The project's download index still lists 9.0.2 as the newest 9.x tarball this page could see.

The short version

No. Phoronix wrote on October 23 that the release dance for FFmpeg 9.1 is underway. The project's releases index, checked the same day, shows 9.0.2 as the newest 9.x tarball, from September, and does not list a 9.1 archive. The changelog on the development branch already has a version 9.1 heading. A heading in the changelog is not a tarball.

A heading is not a file

On October 23, 2026 Phoronix said the release dance was underway for FFmpeg 9.1. The same day's release index on ffmpeg.org lists versioned archives. The newest 9.x files there are the 9.0.2 tarballs from September. There is a development snapshot, updated October 22, and that snapshot is not labeled 9.1. The changelog in the master branch already contains a version 9.1 section. Three documents, three different objects: a news account of a release in preparation, a file list with no 9.1 archive, and a changelog that has started the section.Vulkan's October 23 update.

What the section names

Under that heading the changelog lists work a reader can check by name: ASTC image coding through libastcenc, an improved AAC encoder, an APV Vulkan encoder, an iTerm2 image muxer, an LCEVC bitstream filter, an MVR demuxer, DVD-Audio LPCM, an NVIDIA optical-flow interpolation filter, H.264 data partitioning, and several decoders, plus a note that the asf_o demuxer is removed. Phoronix singles out the APV Vulkan encoder and the optical-flow filter. This page does not turn that list into a manual. A name on a changelog is a claim that the branch contains the work, which a tarball would freeze.

The March date already slipped

In March 2026 a message on the developer list set 9.0 for June and 9.1 for September. June's 9.0 did ship. September's 9.1 did not, on the evidence of the file index. A missed month is ordinary for a volunteer release. It is also the reason a headline that says 9.1 in the present tense needs the file list beside it. Phoronix's verb is preparation. The index's verb is absence.Linux 7.4 is still a window.

Who would be early

Someone building the master branch today can compile code that the changelog files under 9.1. That person is not running a release. A distribution that packages 9.0.2 is on the release the project cut. A distribution that packages a git snapshot should say so, because a later 9.1 tarball can still add or drop entries before the heading is frozen. The removal of a demuxer, if it stays, is the kind of line a packager has to read twice. Until the tarball, the line is provisional.KeePassXC's tagged release.

What Phoronix adds

Phoronix explains the APV encoder as GPU acceleration, through shaders, for the Advanced Professional Video codec, and it explains the optical-flow filter as frame-rate conversion. Those sentences are the reporter's gloss on names that also appear in the changelog. This page keeps the gloss attached to Phoronix and the names attached to the changelog. It does not benchmark either path. An encoder that exists in a branch is not a measurement of speed.Node's October versions, a real tag.

The snapshot is a third object

The release index also offers a snapshot archive with an October 22 timestamp. A snapshot is whatever master was at that hour. It can contain the 9.1 work and also contain commits that will not be in 9.1. Treating the snapshot as 9.1 would invent a version number the filename does not use. The honest row is: changelog section yes, versioned tarball no, snapshot unlabeled. Asked directly, Does the changelog already say 9.1? Yes. The development-branch changelog has a version 9.1 heading and a list under it. That list is what the branch says will be in the release, not proof the release was cut.memory safety in the notes.

Who is in scope

Packagers, and anyone about to write that FFmpeg 9.1 shipped on October 23. People playing a video through a distribution build of 9.0.2 are not on 9.1. Developers tracking master are on master. The scope is the difference between those three. The short answer this page will stand on is this: No. Phoronix wrote on October 23 that the release dance for FFmpeg 9.1 is underway. The project's releases index, checked the same day, shows 9.0.2 as the newest 9.x tarball, from September, and does not list a 9.1 archive. The changelog on the development branch already has a version 9.1 heading. A heading in the changelog is not a tarball.the advisory names a version.

What stays on the record

October 23, 2026 Phoronix account that the 9.1 release dance is underway. Changelog version 9.1 section on the development branch, including the APV Vulkan encoder and vf_fruc_vulkan among other lines. Release index with 9.0.2 as the newest 9.x tarball this page saw, dated in September, and no 9.1 archive. A March schedule that had aimed at September. An October 22 snapshot that is not named 9.1. Asked directly, What does Phoronix say is new? Phoronix names an APV encoder on Vulkan and an NVIDIA optical-flow interpolation filter called vf_fruc_vulkan, and it describes the release dance as underway. Those names match headings a reader can find under the changelog's 9.1 section.

What would move the row

A 9.1 tarball on the release index, with a signature, would make this a release story. A changelog edit that drops a line before that tarball would change the feature list. Until one of those documents exists, the record is a section heading, a file list, and a news account of preparation. Asked directly, What is the newest 9.x file on the release index? The index this page read lists ffmpeg 9.0.2 archives dated in September 2026, and no 9.1 file. A snapshot tarball of the development tree is a different object from a versioned release.what the catalog adds.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. FFmpeg changelog
  2. FFmpeg releases
  3. Phoronix

Questions

What is the newest 9.x file on the release index?

The index this page read lists ffmpeg 9.0.2 archives dated in September 2026, and no 9.1 file. A snapshot tarball of the development tree is a different object from a versioned release.

Does the changelog already say 9.1?

Yes. The development-branch changelog has a version 9.1 heading and a list under it. That list is what the branch says will be in the release, not proof the release was cut.

What does Phoronix say is new?

Phoronix names an APV encoder on Vulkan and an NVIDIA optical-flow interpolation filter called vf_fruc_vulkan, and it describes the release dance as underway. Those names match headings a reader can find under the changelog's 9.1 section.

Was 9.1 supposed to ship in September?

A March 2026 note on the developer list set 9.1 for September 2026. That date passed without a 9.1 file on the index. A schedule is not a release.

Should a packager ship the changelog?

No. A packager ships a tarball the project cut. Until that file exists, the development branch is the development branch, and 9.0.2 remains the newest 9.x release this page can point at.