Back to Toolkit
RenderFree
RenderDoc
Free open-source GPU frame debugger for analyzing real-time rendering in Unreal Engine, Unity, and custom engines. Capture any frame and inspect draw calls, shader inputs, textures, and render targets step by step. Invaluable for technical artists debugging materials, optimizing shaders, and understanding how the GPU processes your game art.
Best For
Capturing a single GPU frame from any game or engine build and inspecting every draw call, shader, and texture state to diagnose visual bugs and validate art asset behavior in the actual render pipeline.
Primary Use Cases
- - Diagnosing why a Substance Painter-textured asset renders darker than expected in Unreal Engine 5 by inspecting its actual shader inputs at draw time
- - Validating that a character's normal map is being sampled with the correct tangent-space settings inside the engine's GBuffer pass
- - Confirming that LOD transitions are firing at the correct screen-size thresholds by capturing frames at varying camera distances
- - Identifying overdraw hotspots in a VFX particle effect by stepping through individual draw calls to find transparency sorting issues
- - Verifying that a material's roughness and metalness channels are correctly split from a packed ORM texture in the shader's texture fetch
Pros & Cons for Game Art
Pros
- + Free and open-source — no license cost for access to the same frame debugging capability used by AAA graphics programmers
- + Works with Unreal Engine 5, Unity, Godot, and custom D3D/Vulkan/OpenGL applications from a single tool
- + Pixel History feature resolves texture debugging questions in seconds that would otherwise require hours of shader printf debugging
- + Mesh Viewer confirms exported geometry — vertex normals, UVs, tangent frames — exactly as the GPU receives them, bypassing importer guesswork
- + Portable capture files (.rdc) can be shared with a technical artist or graphics programmer for remote debugging without them needing the original application
Cons
- − Steep conceptual learning curve — understanding what you are looking at requires baseline knowledge of the GPU rendering pipeline that most art students lack initially
- − No Mac Metal support on recent macOS versions; Apple's own Xcode GPU Frame Debugger must be used for Metal targets
- − Cannot modify shader code or material parameters and re-render in-tool — it is a read-only capture inspector, not an interactive editor
- − Capturing frames from shipping game builds with stripped debug information produces limited draw call labels, making navigation difficult
Suggested Learning Path
- 1.Launch RenderDoc, attach it to a running Unreal Engine 5 PIE session, capture a frame, and navigate the Event Browser to understand draw call structure
- 2.Select a prop's draw call and open the Pipeline State viewer to confirm which shader variant is active and what texture slots are bound
- 3.Use the Texture Viewer to inspect the GBuffer channels (BaseColor, Normal, Roughness/Metalness) for a specific asset and compare them to your Substance Painter export
- 4.Step through a transparent VFX draw call sequence and use the Mesh Viewer to inspect vertex data — confirm UVs and normals match what Blender exported
- 5.Practice diagnosing a self-introduced bug: misconfigure a texture channel in Substance, export, and use RenderDoc to trace the incorrect value back to its source
Quick Tip
In the Texture Viewer, use the "Pixel History" feature on a suspiciously dark pixel — it shows every draw call that touched that pixel and what value each wrote, pointing you directly to which pass or shader is corrupting the final color.
Setup Notes
- - On Unreal Engine 5, launch via RenderDoc's "Launch Application" rather than attaching to a running process — this ensures the D3D12 hooks initialize correctly before the renderer starts
- - Disable Temporal Anti-Aliasing (TAA) in UE5 before capturing for art debugging — TAA accumulates frames and makes single-frame texture inspection unreliable
- - Enable "Allow full replay" in capture settings to allow scrubbing backward through draw call history, which is essential for debugging complex render graphs
- - Increase RenderDoc's capture memory limit in Settings if capturing large open-world scenes — the default limit causes incomplete captures that drop late draw calls
How N-hance Uses It
N-hance's VFX Artist course introduces RenderDoc as an advanced diagnostic tool for verifying that particle shaders and post-process materials behave as intended in Unreal Engine 5, teaching students to read GPU pipeline state rather than guess at engine-side material issues.