RenderDoc

RenderDoc
Name	RenderDoc
Developer	Baldur Karlsson
Released	2014
Programming language	C++
Operating system	Windows, Linux
Platform	x86, x86-64
Genre	Graphics debugger, frame capture tool
License	MIT License

RenderDoc RenderDoc is a frame-capture and graphics debugging tool used to inspect and analyze rendering workloads produced by applications and engines such as Unreal Engine, Unity, CryEngine, Godot, and custom renderers. It provides pixel-accurate capture of individual frames from applications using graphics APIs like Vulkan, Direct3D 11, Direct3D 12, and OpenGL. Widely adopted in industry and academia, RenderDoc complements tools from vendors including NVIDIA, AMD, Intel, and integrates into workflows alongside profilers such as NVIDIA Nsight, AMD Radeon GPU Profiler, and Windows Performance Analyzer.

Overview

RenderDoc originated as an open-source project by Baldur Karlsson to address the need for an API-neutral, inspector-style debugger suitable for modern real-time graphics. It enables developers from studios like Electronic Arts, Ubisoft, CD Projekt Red, Valve, and Rockstar Games to capture command streams, buffers, and textures for offline analysis. Academic groups at institutions such as MIT, Stanford University, and University of Cambridge have used it in research on real-time rendering, visualization, and graphics education. RenderDoc operates as a non-intrusive layer between application and GPU driver, supporting workflows found in production pipelines at companies like Microsoft, Sony Interactive Entertainment, and Nintendo.

Features

RenderDoc exposes per-draw and per-dispatch state, including shader source, pipeline state, resource bindings, and GPU memory contents. Users can inspect shader inputs and outputs using shader debugging and variable viewing akin to tools provided by Visual Studio, JetBrains products, and Eclipse Foundation IDEs. It can perform pixel history analysis to trace the sequence of fragments affecting a pixel, a capability relevant to studios such as Bungie and Square Enix during visual regression debugging. Frame capture includes call stacks and timing metadata, which can be correlated with events in profilers from Intel and NVIDIA or with telemetry systems used by Amazon Web Services game services. RenderDoc supports shader editing and live recompile workflows often employed in productions by Activision Blizzard and integrates with CI systems used by companies like Google and Facebook for automated testing.

Supported Platforms and APIs

RenderDoc supports desktop platforms including Microsoft Windows and Linux, with community ports and integrations for specialized environments. Its primary API support covers Vulkan, Direct3D 11, Direct3D 12, and OpenGL. Through layers and adapters it interfaces with drivers from vendors such as NVIDIA, AMD, and Intel. RenderDoc captures are often used alongside platform SDKs from Microsoft, console SDKs from Sony Interactive Entertainment and Nintendo, and middleware from Havok, SpeedTree, and FMOD. Third-party contributions have extended interoperability with windowing libraries like SDL, GLFW, and frameworks such as Qt.

Architecture and Design

RenderDoc is implemented primarily in C++ and designed around a modular capture-replay architecture. The capture component injects into or wraps the graphics API calls made by applications, recording resources, command buffers, and draw calls. A replay component reconstructs the recorded frame deterministically for inspection, enabling features like shader stepping and pixel history. The design separates frontend UI, influenced by patterns from GTK, Qt, and Dear ImGui, from backend platform integrations targeting Windows and Linux system APIs such as those from Microsoft Windows and X.Org. RenderDoc’s architecture supports serialization formats for captured frames, facilitating sharing among developers at studios like Blizzard Entertainment and researchers at ETH Zurich.

Usage and Workflow

Typical usage begins by launching or attaching RenderDoc to an application or engine process, capturing a single frame, and opening that capture in the UI for inspection. Users navigate a hierarchical event list similar to command viewers in tools from NVIDIA and AMD to select draw calls and examine pipeline state, resource contents, and shader variables. Shader debugging provides source-level stepping comparable to debuggers such as GDB and LLDB, while pixel history allows reverse-tracing of blending and depth tests as done in productions at Tencent and Epic Games. Captures can be shared among teams via files, enabling collaboration across organizations such as Sony Interactive Entertainment and academic labs at University of California, Berkeley.

Development and Community

RenderDoc’s development is driven by an active community of contributors from independent developers, studios, hardware vendors, and academic researchers. Contributions are coordinated through platforms familiar to developers from GitHub and discussions occur on forums and chat services used by groups like Khronos Group members and vendor-specific communities. Notable contributors include individuals associated with companies such as NVIDIA, AMD, and Intel, as well as engineers from game studios and middleware firms. Educational initiatives at institutions like University of Washington and University of Toronto incorporate RenderDoc into graphics curricula, and conference presentations have been given at events like SIGGRAPH, GDC, and Eurographics.

Licensing and Distribution

RenderDoc is distributed under the MIT License, permitting wide reuse and integration into commercial and open-source projects. Binary distributions are provided for Windows and Linux platforms, with source available for compilation and modification. Its permissive licensing has enabled adoption in proprietary engines and integration into tooling ecosystems used by companies like Epic Games, Unity Technologies, and middleware providers while fostering contributions from vendors including AMD and NVIDIA.

Category:Graphics software Category:Debugging software Category:Open-source software