baldurk/renderdoc

RenderDoc is a stand-alone graphics debugging tool.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 5th, 2026
Created on February 27th, 2014
Open Issues & Pull Requests: 49 (+0)
GitHub issues: Enabled
Number of forks: 1,755
Total Stargazers: 11,062 (+0)
Total Subscribers: 236 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.5 hours
Mean response time: 9.2 days
90th percentile: 2.8 days
Tracked items: 2,392

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 11% of issues opened in the past year have been closed. Three people close 87% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 17
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 1,427 days
Stale 30+ days: 13
Stale 90+ days: 12

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 5

Top labels

  • Bug (1,119)
  • Unresolved (608)
  • Need More Info (517)
  • Feature (276)
  • Profiling (3)

Detailed Description

RenderDoc is a stand-alone graphics debugging tool that captures and analyzes graphics API calls to help developers diagnose rendering issues.

The tool solves the problem of understanding what happens during graphics rendering by intercepting and recording API calls made to graphics libraries. It captures a frame or sequence of frames, then allows developers to step through draw calls, inspect shader state, examine textures and buffers, and replay operations to identify where visual artifacts or performance problems originate. The approach works by instrumenting graphics APIs including Direct3D 11 and 12, OpenGL, and Vulkan, giving developers visibility into the entire rendering pipeline.

RenderDoc suits graphics programmers, game developers, and engine maintainers who need to debug rendering behavior across different graphics APIs. It is particularly valuable when working with modern APIs like Vulkan or Direct3D 12, where the complexity of explicit resource management and synchronization makes debugging difficult. The tool is useful for both real-time graphics work and offline rendering pipelines. Developers choosing RenderDoc should expect a dedicated application focused specifically on graphics API debugging rather than a general-purpose debugger; this specialization means it provides deep insights into graphics-specific state but operates as a separate tool from CPU debuggers.

The project maintains active development with regular updates addressing new graphics API features and capabilities. The codebase shows ongoing refinement of existing functionality and expansion of supported graphics APIs. Development activity indicates sustained attention to compatibility across different platforms and graphics driver versions. The project demonstrates responsiveness to issues and maintains documentation alongside code changes.