Vulkan SDK 1.4.341.1 Release Notes
Version 1.4.321.1 for Linux
February 4, 2026
Overview of new features in SDK 1.4.341.1
This SDK supports Vulkan API revision 1.4.341.
Please refer to the Getting Started Guide for a list of supported Linux distributions.
SDK Version Lifetime Vulkan SDK's older than 2 years are removed from the Vulkan SDK download site and won't be available once removed. All SDK's are backwards compatible and using the latest or newer SDK is recommended due to ongoing bug fixes and enhancements in the SDK content.
Drivers: It is recommended that you update Vulkan-capable hardware drivers to the latest recommended version from the hardware vendor. A list of Known Issues appears at the end of this document with more information.
Looking for the Android build of the Validation Layers?
With each SDK release, the Android Validation Layer binaries are released in the Validation Layers repository
Deprecation Notices
The May 2025 SDK release was the last release of Ubuntu Packages. As Ubuntu Packages become older than two years, they will be removed from public availability.
GLIBC requirements
The precompiled binaries provided now require GLIBC version 2.35 or higher
Version 1.4.341.1 for Linux
February 4, 2026
Version 1.4.341.1 addresses a crash in the API dump layer when VK_EXT_descriptor_heap was used.
Overview of new features in SDK 1.4.341.0
The Vulkan headers now include the following new extensions. Note that extensions are optional and may not be implemented by the underlying driver/ICD. Applications can now query for the presence of these new features.
- VK_KHR_internally_synchronized_queues
- VK_EXT_descriptor_heap
- VK_EXT_shader_subgroup_partitioned
- VK_NV_push_constant_bank_support
- VK_EXT_texture_compression_astc_3d
- VK_EXT_shader_long_vector
- VK_NV_compute_occupancy_priority
Inclusion of the Roadmap 2026 Profile that mandates high-end features that were previously optional to ensure consistency across modern desktop, mobile, and console hardware.
Improved validation coverage. VUID validation coverage documentation (validation_error_database.csv and validation_error_database.html) has been updated to represent the validation layer VUID coverage status.
- Note: This SDK includes validation layer support for all of the EXT
and KHR extensions listed above.
- CPU based validation for VK_EXT_descriptor_heap is included in this SDK. The GPU based validation will be included in the next SDK release.
- Note: This SDK includes validation layer support for all of the EXT
and KHR extensions listed above.
Platform Support Matrix
| Feature | Windows-x64/x86 | Windows-ARM | Linux tarball | macOS SDK |
|---|---|---|---|---|
| Tools | ||||
| Vulkan Configurator | X | X | X | X |
| Vulkaninfo | X | X | X | X |
| Vulkan Profiles API Library | X | X | X | X |
| VOLK (a meta-loader for Vulkan) | X | X | X | X |
| AMD Memory Allocator | X | X | X | X |
| Validation Layers | ||||
| Validation | X | X | X | X |
| Best Practices | X | X | X | X |
| GPU Assisted Validation | X | X | X | |
| Debug Printf | X | X | X | |
| Synchronization Validation | X | X | X | X |
| Utility Layers | ||||
| Crash Diagnostic Layer | X | X | X | |
| Profiles Layer | X | X | X | X |
| API Dump | X | X | X | X |
| Monitor | X | X | X | X |
| Screenshot | X | X | X | X |
| GFXReconstruct | X | X | X | X |
| Extension Layers | ||||
| Synchronization 2 | X | X | X | X |
| Shader Object | X | X | X | X |
| Shader Tools | ||||
| glslangValidator | X | X | X | X |
| SPIR-V Optimizer | X | X | X | X |
| SPIR-V Disassembler, Assembler, Validator | X | X | X | X |
| SPIR-V Remapper (spirv-opt canonicalize-ids) | X | X | X | X |
| SPIR-V Control Flow Visualization | X | X | X | X |
| SPIR-V Cross-Compilation and Reflection | X | X | X | X |
| shaderc | X | X | X | X |
| DXC (DirectX Shader Compiler) | X | X | X | X |
| SPIRV-reflect | X | X | X | X |
| slang | X | X | X | X |
SDK Components
This version of the SDK is based on the following specifications, source code repositories, and commits:
- Vulkan Specification
- SPIR-V Specification (Version 1.6, Revision 5)
- GLSL Specification (Version 4.6)
- GitHub Repo: KhronosGroup/glslang, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: KhronosGroup/SPIRV-Cross Version Tag: vulkan-sdk-1.4.341.0
- Github Repo: SPIRV-Reflect Version Tag: vulkan-sdk-1.4.341.0
- Github Repo: shader-slang Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: KhronosGroup/SPIRV-Tools, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: KhronosGroup/Vulkan-Headers, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: KhronosGroup/Vulkan-Loader, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: KhronosGroup/Vulkan-Tools, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: KhronosGroup/Vulkan-ValidationLayers, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: KhronosGroup/Vulkan-Profiles, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: KhronosGroup/Vulkan-ExtensionLayer, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: KhronosGroup/Vulkan-Utility-Libraries, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: LunarG/gfxreconstruct, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: LunarG/VulkanTools, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: LunarG/CrashDiagnosticLayer, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: volk, Version Tag: vulkan-sdk-1.4.341.0
- GitHub Repo: AMD Memory Allocator tag: v3.3.0
- GitHub Repo: microsoft/DirectXShaderCompiler commit: e35541826046479d9787ea0368b274ed2447f913
- GitHub Repo: google/shaderc commit: 3108af8ce49ae67066bb9289ed889a85b0c3e393
- GitHub Repo: SaschaWillems/VulkanCapsViewer tag: 4.11
Submitting Issues
If while using the tools and layers included in the SDK you find a defect in that tool or layer, the most expedient way to get a resolution is to submit to its corresponding repository. For example, if you believe you have found a defect in the Validation Layers, submit an issue at the repository for Validation Layers. The only exception to this is for the shader tool chain (glslang, SPIRV-Cross, SPIRV-Tools, shaderc). For these repositories you can submit issues against the SDK at vulkan.lunarg.com.
Known Issues
- When using Vulkan Profiles requiring Profiles with the Vulkan Profiles layer, no warning is emitted when trying to override a device capability to a value that is not supported by the device.
- Vulkan Configurator known issues are documented in the Vulkan Configurator Change Log

