khronosgroup/vulkan-docs

The Vulkan API Specification and related tools

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 20th, 2026
Created on February 11th, 2016
Open Issues & Pull Requests: 389 (+0)
GitHub issues: Enabled
Number of forks: 549
Total Stargazers: 3,338 (+0)
Total Subscribers: 215 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 347
New in 7 days: 2
Closed in 7 days: 3
Avg open age: 1,349 days
Stale 30+ days: 326
Stale 90+ days: 304

Recent activity

Opened in 7 days: 2
Closed in 7 days: 3
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Resolving Inside Khronos (82)
  • System Integration (72)
  • Feature Request (60)
  • Ray Tracing (23)
  • Specification (17)
  • Video (15)
  • Memory Model TSG (9)
  • Extension (7)

Detailed Description

Vulkan-docs is the official API specification and documentation repository for the Vulkan graphics and compute API maintained by the Khronos Group.

The repository serves as the authoritative source for the Vulkan API specification and reference documentation. It addresses the need for comprehensive, standardized documentation of the Vulkan API by maintaining specification documents in Asciidoctor format and generating API headers and related files from a centralized XML registry. The approach separates specification markup from generated artifacts, allowing the XML registry to serve as the single source of truth from which C headers and documentation components are automatically produced.

Developers working on Vulkan implementations, bindings, or applications that need to reference the official specification should use this repository. It is essential for anyone implementing Vulkan drivers, creating language bindings, or contributing to the Vulkan ecosystem. The repository includes separate documentation tracks for both the standard Vulkan API and Vulkan SC, a safety-critical variant designed for use in safety-critical systems.

The project maintains active development with regular updates to the specification and toolchain. The build system uses Asciidoctor and related tools to generate output documents from source markup, with a Makefile-based workflow for managing dependencies and regenerating headers from the XML registry. Changes to the XML registry automatically trigger regeneration of C headers and related specification components through the build system's dependency tracking.