Vulkan 1.4.366 adds one HDR extension. The extension is not ratified.
Vulkan 1.4.366, dated October 23, adds one unratified extension for SMPTE ST 2094-50 swapchain metadata. Phoronix says the rest is fixes and clarifications.
The short version
The Vulkan documentation and the Khronos specification tree updated October 23 add VK_GOOGLE_hdr_smpte_st_209450_metadata, revision 1, extension number 719. The page says the extension is not ratified. It lets an application attach SMPTE ST 2094-50 dynamic metadata to a swapchain. Phoronix describes the release as two weeks of fixes plus that one extension.
One extension, dated two ways
On October 23, 2026 the Khronos Vulkan specification directory showed a fresh tree, and Phoronix reported Vulkan 1.4.366. The new API surface in that update is VK_GOOGLE_hdr_smpte_st_209450_metadata. The reference page gives it extension number 719, revision 1, and a last-modified date of October 8, 2026. Those are different clocks. October 8 is when the extension text was last edited. October 23 is when the specification update and the news account landed. A reader who treats the news date as the day the text was written will miss the earlier modification date printed on the page.a stable release with a tag.
What the structure carries
The reference page says an application can attach SMPTE ST 2094-50 dynamic metadata to a swapchain by chaining VkHdrSmpteSt209450GOOGLE onto the existing HDR metadata structure. The buffer is a bitstream defined in the SMPTE document. The call copies those bytes. A separate field lets the application suggest a tradeoff between color accuracy and lower power. The page says the implementation does not validate the buffer. A bad bitstream is still a bad bitstream after Vulkan accepts the pointer. This page will not pretend the specification checks the picture.
Not ratified, and not a product launch
The same page says the extension is not ratified. An unratified extension can be in the published headers and still be a vendor proposal. Phoronix says the standard itself, SMPTE ST 2094-50, was finalized in August and is meant to improve the mix of SDR and HDR, including brightness spikes. That purpose is Phoronix's summary of the standard, not a measurement this page ran. Shipping the structure in the specification does not mean a particular phone or television has turned it on.FFmpeg 9.1 is not a tarball yet.
What a swapchain note is not
HDR metadata on a swapchain is a hint to the presentation engine. It is not a codec, and it is not a new GPU. The proposal text says some engines can apply the metadata in a low-power hardware block or in a higher-precision shader, which is why the power preference exists. A game that never sets the structure is unchanged. A video player that does set it still depends on the compositor honoring the bytes. The specification says use of the data follows the SMPTE document and is outside Vulkan's scope.the short slice in the scheduler.
Two weeks, one headline
Phoronix frames 1.4.366 as the past two weeks of specification fixes, clarifications, and one new extension. That framing matters because a version number that ticks every two weeks is a document, not a product release a user installs from an app store. Developers who vendor the headers pick up the structure. Users do not see 1.4.366 as a version on a box. The GitHub history Phoronix points at is the change list. This page uses the reference page for the extension's own fields and Phoronix for the scope of the rest of the update.Open Responses, one announcement.
What this page will not collapse
It will not call the extension ratified because the headers exist. It will not attribute the August standard's authorship beyond what Phoronix names. It will not claim Chrome has shipped the path, because Phoronix says Google has been working to bring the standard to Chrome, which is a program of work and not a release note this page opened. The record is the reference page, the dated specification directory, and Phoronix's account of the update.what a training cutoff does not mean.
Who is in scope
Graphics programmers who set HDR metadata on a Vulkan swapchain, and the driver writers who would honor the new structure. People watching a video are in scope only if an application and a compositor both implement the path. A phone that never exposes the feature is outside the extension even if it plays HDR by some other means. Asked directly, Is the new extension ratified? No. The Vulkan reference page lists ratification status as not ratified, revision 1, last modified October 8, 2026. A specification update is not a ratification vote.on-device inference, a different limit.
What stays on the record
Vulkan 1.4.366 as Phoronix's October 23, 2026 report. Extension VK_GOOGLE_hdr_smpte_st_209450_metadata, number 719, revision 1, not ratified, last modified October 8, 2026. SMPTE ST 2094-50 dynamic metadata on a swapchain. No validation of the bitstream. A power-preference hint. Dependencies on Vulkan 1.1, the swapchain extensions, and VK_EXT_hdr_metadata. Contributors listed as Google engineers. The specification directory's October 23 tree is the publication clock, not a claim that every GPU implemented the hint that day. Asked directly, Does the driver check the metadata bytes? The reference page says no validation is performed on the buffer. The bytes are copied and passed on. Validity is outside Vulkan, in the SMPTE document.
What would move the row
A ratification notice, or a driver release that says the feature is enabled on named hardware, would be a later document. Until then the row is a specification update with one unratified extension and a news account that separates that extension from a pile of clarifications. The short answer this page will stand on is this: The Vulkan documentation and the Khronos specification tree updated October 23 add VK_GOOGLE_hdr_smpte_st_209450_metadata, revision 1, extension number 719. The page says the extension is not ratified. It lets an application attach SMPTE ST 2094-50 dynamic metadata to a swapchain. Phoronix describes the release as two weeks of fixes plus that one extension.the advisory is the story.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
Is the new extension ratified?
No. The Vulkan reference page lists ratification status as not ratified, revision 1, last modified October 8, 2026. A specification update is not a ratification vote.
Does the driver check the metadata bytes?
The reference page says no validation is performed on the buffer. The bytes are copied and passed on. Validity is outside Vulkan, in the SMPTE document.
What must a device already support?
The reference page lists Vulkan 1.1 or the properties2 extension, plus swapchain, surface-capabilities2, and VK_EXT_hdr_metadata. The new structure hangs off the existing HDR metadata structure.
Who wrote it?
The contributors on the reference page are Google engineers. Phoronix says Google has been bringing the August SMPTE standard into Chrome and other software. That is Phoronix's account of the standard's authors, which it names as Google, Apple, and NBCUniversal.
Is 1.4.366 a new major version?
No. It is a specification update inside 1.4. Phoronix says the notable addition is the one extension, with the rest described as minor fixes and clarifications.