Renderdoc

Open source alternative to NVIDIA Nsight Graphics

11.3K stars
MIT
Active this week
Last commit today

Last verified Nov 13, 2026

Analyze GPU frames and inspect shaders with a free MIT-licensed graphics debugger for Vulkan, D3D11, D3D12, OpenGL, and OpenGL ES.

Visit website GitHub11.3K

Read the full breakdownWho it is for, how it works, trade-offs, the quick start and the FAQ

who it's for

Who Renderdoc is for#

Game developers debugging rendering artifacts

RenderDoc captures the exact frame where an artifact appears and lets you trace the draw call that produced it, inspect the textures and buffers at that point, and step through the responsible shader. Engine integration in Unity and Unreal makes triggering a capture as simple as pressing a button in the editor.

Skip if:

If you need sustained performance profiling, frame pacing analysis, or GPU utilization data over multiple frames, RenderDoc's single-frame model does not cover it. Use a dedicated GPU profiler alongside RenderDoc for that work.

Mobile GPU engineers targeting Android

RenderDoc captures OpenGL ES (2.0 to 3.2) and Vulkan frames on Android devices over adb. The capture file is portable, so you can record on device and replay the same frame on a desktop with the full shader debugger and resource inspector for detailed analysis.

Skip if:

RenderDoc has no Metal support, so iOS and macOS Metal applications are out of scope. Teams using non-Vulkan or non-GLES APIs on Android will need a different debugging approach.

Graphics programming students and hobbyists

The MIT license and free distribution mean there is no cost barrier to using a production-grade frame debugger for learning OpenGL, Vulkan, or DirectX. YouTube tutorials and HTML documentation cover the core workflows, and the Discord server and issue tracker provide access to the maintainer.

Skip if:

Students learning on Apple platforms using Metal will not find RenderDoc useful, as Metal support is not available.

the problem

The problem it solves#

GPU rendering bugs are some of the hardest to track down in software development. A wrong pixel, a flicker, or an artifact on a specific hardware configuration tells you almost nothing about which of hundreds of draw calls, thousands of shader invocations, or dozens of render state changes caused it. Without a dedicated frame debugger, the standard approach is guesswork. Teams comment out draw calls, add debug print statements that require shader recompilation, or stare at a texture atlas until the culprit surfaces.

The commercial tools that address this, like NVIDIA Nsight Graphics, tie you to specific hardware vendors or require proprietary driver access. Teams working across Vulkan, OpenGL, and DirectX on mixed hardware, or those building under NDA for platforms that cannot share code with profiling vendors, have historically had no free, vendor-neutral option that covers every major graphics API.

how Renderdoc solves it

How it solves it#

Single-frame capture and replay

Injects into any Vulkan, D3D11, D3D12, OpenGL, or OpenGL ES application at startup and records the entire frame, including every draw call, resource state, texture, buffer, and render target. The capture file replays independently of the original application, so you can share it with teammates or examine it on a different machine.

Per-pixel history

Shows every draw call that wrote to or discarded a specific pixel in the frame, in draw order. You see the blended result at each stage and the exact shader output at each contributing pass, which turns multi-pass rendering bugs from a guessing game into a targeted trace.

HLSL and GLSL shader debugger

Steps through vertex, pixel, and compute shaders line by line in the editor, showing input and output at each line. All major shader languages on all supported APIs are covered, so you can verify exactly what a shader computed for a specific draw call without adding instrumentation or recompiling.

Cross-platform capture portability

Captures recorded on Android, Windows, or Linux replay on any supported desktop platform. For mobile GPU debugging, record a frame on device, then replay the same capture on a desktop with the full shader debugger and resource inspector for detailed analysis.

Embedded Python scripting

Embeds the Python runtime for programmatic access to frame captures. You can write scripts to automate analysis, batch-inspect resources across a capture, or integrate RenderDoc frame inspection into a larger test or reporting pipeline.

strengths · trade-offs

Strengths and trade-offs#

Strengths

Vendor-neutral API and hardware coverageCovers Vulkan, D3D11, D3D12, OpenGL (3.2 to 4.6 Core), and OpenGL ES (2.0 to 3.2) in one tool. NVIDIA Nsight Graphics ties GPU trace and shader debugging to NVIDIA hardware; RenderDoc works across AMD, Intel, and mobile GPUs using any of these APIs, with no driver or vendor lock-in.
MIT license with no feature gatingThe entire tool is MIT-licensed with no paid tier, no hardware vendor requirement, and no restricted features. You can use it on commercial games, NDA projects, and educational work without a license agreement or any data sharing with a third party.
Built-in Unity and Unreal Engine integrationBoth Unity and Unreal Engine ship built-in RenderDoc capture buttons, making single-frame debugging a one-click workflow without manual injection. This is documented and officially supported in both engines.
Direct maintainer accessThe project is actively maintained by its original developer, who answers questions directly by email and in the Discord. The website states: 'I'll respond to you directly and personally, and I'm used to helping people with private or NDA'd projects.'

Trade-offs

-Desktop-only, no headless or CI capture modeRenderDoc is designed for interactive desktop use. There is no headless capture mode, no REST API, and no built-in way to trigger a capture from a CI pipeline. Automated rendering regression testing requires a separate approach or scripting on top of the Python API.
-D3D9, D3D10, and Metal not supportedDirectX 9 and DirectX 10 are explicitly unsupported. Metal is listed as not available on any platform. Teams targeting older DirectX APIs or Apple Silicon native graphics paths cannot use RenderDoc for those APIs and will need a separate debugging approach.
-No GPU performance profilingRenderDoc is a frame-capture correctness debugger, not a performance profiler. It has no GPU performance counters, frame pacing view, or sustained throughput analysis. For stutter diagnosis or GPU utilization work, a dedicated profiler is needed alongside it.

versus alternatives

Renderdoc vs alternatives#

RenderDoc vs NVIDIA Nsight Graphics

Both tools capture and replay GPU frames for shader debugging, but they serve different hardware assumptions. RenderDoc is MIT-licensed and runs on any GPU vendor; NVIDIA Nsight Graphics is proprietary and requires an NVIDIA GPU with a compatible driver.

Feature	RenderDoc	NVIDIA Nsight Graphics
License	MIT, free	Proprietary
Hardware	Any vendor (AMD, Intel, NVIDIA, mobile)	NVIDIA GPU required
APIs	Vulkan, D3D11, D3D12, OpenGL, OpenGL ES	D3D, Vulkan, OpenGL, OpenXR
Shader debugging	HLSL and GLSL, vertex/pixel/compute	HLSL, GLSL with NVIDIA extensions
GPU performance profiling	No	Yes
Ray tracing inspection	No	Yes, RTX hardware
Platforms	Windows, Linux, Android	Windows only
Price	Free	Free download

RenderDoc is the better choice for cross-vendor development or any project that requires Linux or Android capture. Its frame captures are portable between platforms, so a capture recorded on an Android device replays on a Windows desktop with the full shader debugger. The MIT license and direct maintainer support make it practical for NDA and commercial work without data sharing with a third party.

NVIDIA Nsight Graphics fits when you specifically need GPU performance counters, sustained throughput analysis, or ray tracing pipeline inspection on RTX hardware. Those profiling capabilities fall outside what RenderDoc does. RenderDoc is a frame-capture debugger built for correctness investigation, not a performance profiler.

install · quick start

Quick start#

bash

Download the Windows installer or Linux binary tarball from GitHub Releases: https://github.com/baldurk/renderdoc/releases/latest

tech stack · detected from GitHub

What it's built on#

Languages: CC++Python

frequently asked

FAQ#

Which graphics APIs does RenderDoc support?

RenderDoc supports Vulkan, D3D11, D3D12, OpenGL (3.2 to 4.6 Core), and OpenGL ES (2.0 to 3.2). D3D9, D3D10, and Metal are explicitly unsupported. Nintendo Switch support is available separately through the NintendoSDK for authorized developers.

What platforms can I run RenderDoc on?

Windows (32-bit and 64-bit), Linux (x64 only), and Android are supported for capture and replay. Nintendo Switch capture is distributed separately via NintendoSDK. macOS is not supported.

Can I use RenderDoc on a commercial or NDA project?

Yes. RenderDoc is MIT-licensed, so you can use it on any project, including commercial games and NDA work, without a license agreement or any data sharing with the developer. The maintainer notes experience helping with private and NDA'd projects directly.

Does RenderDoc work with Unity and Unreal Engine?

Yes. Both engines ship built-in RenderDoc integration with a dedicated capture button in their editors. This triggers a RenderDoc frame capture directly without manual injection, so you get the full debugger without any additional setup beyond installing RenderDoc.

How do I install RenderDoc on Windows and Linux?

On Windows, download the 64-bit or 32-bit MSI installer from renderdoc.org/builds and run it. On Linux, download the precompiled x64 binary tarball from the same page and extract it. Source builds are documented in CONTRIBUTING/Compiling.md if you need a custom configuration.

also worth a look

Similar open-source tools#

Slint

Alternative toQt

Cross-platform native UI toolkit for Rust, C++, JS, and Python.

24,574 GitHub stars
Licence Triple-licensed: Royalty-free 2.0 / GPL-3.0-only / Commercial (Slint)

Brag

InDesign & Creative

Agent skill that turns any project into a launch video in one command

20,980 GitHub stars
Licence MIT

Astryx

Alternative toMUI X

Agent-ready React design system with 150+ accessible components.

23,107 GitHub stars
Licence MIT

Rataflow

InDeveloper Tools

Node-based flow graph library for the terminal, in Rust.

197 GitHub stars
Licence MIT

BUI

InDeveloper Tools

Blender's widget system for Python, Rust, JavaScript and C apps

2,383 GitHub stars
Licence GPL-3.0

Pyxel

Alternative toPICO-8

Python retro game engine with built-in editors and browser export.

18,604 GitHub stars
Licence MIT

by category

Open source tools in these categories#

633

12,987 GitHub stars
Licence AGPL-3.0
#Email

rakazo

Alternative toGrok Bot

AI teammates you own: your keys, your model, your machine.

7,869 GitHub stars
Licence Apache-2.0
#AI Agents

SnitchFeed

Live monitoring on LinkedIn, X, Reddit & more. Agentic social listening for startups.

Marketing & Growth

Advertise your product

The projects we add and every new guide. Free, unsubscribe any time.

Find open source alternatives to paid software

RenderDoc vs NVIDIA Nsight Graphics

Feature	RenderDoc	NVIDIA Nsight Graphics
License	MIT, free	Proprietary
Hardware	Any vendor (AMD, Intel, NVIDIA, mobile)	NVIDIA GPU required
APIs	Vulkan, D3D11, D3D12, OpenGL, OpenGL ES	D3D, Vulkan, OpenGL, OpenXR
Shader debugging	HLSL and GLSL, vertex/pixel/compute	HLSL, GLSL with NVIDIA extensions
GPU performance profiling	No	Yes
Ray tracing inspection	No	Yes, RTX hardware
Platforms	Windows, Linux, Android	Windows only
Price	Free	Free download