# RenderDoc

Application: Baldur Karlsson

Also called qrenderdoc, render doc

Baldur Karlsson, Productivity

Graphics debugger. The process is qrenderdoc.exe. It is not a game. It is not PIX.

## What you need to know

RenderDoc is a graphics debugger. It is not PIX and not a game.

qrenderdoc.exe captures frames. PIX is Microsoft's tool. Unreal and Unity are engines, not this debugger.

- **What is it?**: Graphics debugger

  **Still current?**: Yes, see Current status

  **Official download?**: Use the vendor link in this article

Feex says

If qrenderdoc.exe is running, I treat it as a capture tool. I do not look for a Steam play button, and I do not open PIX unless the job is PIX.

## What is RenderDoc?

qrenderdoc.exe injects and captures frames. You inspect draw calls and textures. It is not UnrealEditor.exe and not PIX's timing UI.

## If you have never used it

If you need to capture a frame from a D3D or Vulkan app, RenderDoc is Baldur Karlsson's debugger. Download it from renderdoc.org. It is not a game. PIX is Microsoft's Xbox/DirectX profiler, a different tool.

## What is it used for?

**Frame capture**

Launch the target from RenderDoc. This is a debugger, not a game you play.

**Mesh, texture, and pipeline inspect**

Why graphics engineers keep it. PIX overlaps on D3D but is a different Microsoft product.

**Vulkan and D3D targets RenderDoc lists**

API support is on renderdoc.org. Some consoles and APIs stay on PIX or vendor tools.

## Who is it for?

- Graphics programmers
- Technical artists chasing a bad draw
- People who saw qrenderdoc.exe and thought it was a game

## Current status

RenderDoc (2014) is a current graphics debugger from Baldur Karlsson. The vendor still points Windows users at https://renderdoc.org/.

## How old is it?

RenderDoc launched in 2014 and became the common capture tool for PC graphics. PIX is Microsoft's sibling for DirectX on Windows and Xbox. Neither is a Steam game.

## Versions

Major channels first. Exact build numbers are not all verified here.

RenderDoc

## System requirements

Values follow the publisher's public guidance. Workload still changes the real need.

### Minimum

| Operating system | A current supported Windows 10 or Windows 11 release, per the vendor |
| ---------------- | -------------------------------------------------------------------- |
| RAM              | Enough for Windows plus this app. Heavy projects want more.          |

## Resource profile

- **CPU demand**: Follows what you open inside the app

  **RAM demand**: Follows documents, tabs, or libraries

## Installed processes

These executables belong to this product when it is installed.

| qrenderdoc.exe | Main Windows executable |
| -------------- | ----------------------- |

## Startup components

RenderDoc starts when you capture. It does not need Startup Apps.

## File locations

| Typical install | C:\Program Files\RenderDoc\\ |
| --------------- | ---------------------------- |

## File formats

RDC

## Common problems

### Tried to "play" RenderDoc

There is no campaign. You launch another exe under capture. It is not a game.

### Needed PIX timing and opened RenderDoc instead

PIX is the Microsoft sibling for some D3D/Xbox jobs. Different installer.

## Getting unstuck

### Install from renderdoc.org

Docs and GitHub releases are official. Skip "RenderDoc game" stores that are the wrong product.

### Launch the target from RenderDoc, or inject as the docs say

Attaching late can miss the frame. PIX has its own attach flow.

### If capture fails, check the API RenderDoc supports for that build

Some debug layers and overlays (RTSS, NVIDIA) interfere. Turn them off for a capture.

## Alternatives

PIX is Microsoft's graphics debugger/profiler. NVIDIA Nsight and AMD tools are vendor suites. Those are not games either.

## Official help and downloads

Start with the vendor. Random exe sites are not a support channel.

| Download      | [renderdoc.org/ ](https://renderdoc.org/)Official installer or vendor page |
| ------------- | -------------------------------------------------------------------------- |
| Help          | [renderdoc.org/docs ](https://renderdoc.org/docs)Vendor support            |
| Official site | [renderdoc.org/ ](https://renderdoc.org/)Start here, not a random exe host |

## Related hardware

Needs a GPU and driver the target app already uses. Capture adds overhead. This is not a benchmark Feex invented.

## Technical details

Technical details

Vendor version numbers change. This article does not pin a build.

## Related

These entities connect to this article. Type is shown on every link.

[Unreal Engine: Application](https://feex.it/wiki/software/unreal-engine)[How to read Task Manager: Guide](https://feex.it/wiki/software/system/how-to-read-task-manager)

## Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. [How we research](https://feex.it/wiki/research).

- [RenderDoc official site ](https://renderdoc.org/)· Vendor product page
- [RenderDoc help ](https://renderdoc.org/docs)· Vendor support
- [RenderDoc GitHub ](https://github.com/baldurk/renderdoc)· Source and releases
- [Foxhole process map ](https://foxhole.feex.it/)· First-party samples on Windows PCs. Not a lab benchmark.

## Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.

Quick facts

The short identity of this page. Specs, sources, and the full story stay in the article.

- **Developer**: Baldur Karlsson

  **Category**: Graphics debugger

  **Process**: qrenderdoc.exe

  **License**: MIT

  **First released**: 2014

  **Official site**: [renderdoc.org](https://renderdoc.org/)

  **Mapped by Feex**: Seen on Windows PCs in Foxhole

Feex Reviewed: Last verified August 2026

---

Source: [Canonical Feex Wiki page](https://feex.it/wiki/software/renderdoc/)

[Developer guide](https://feex.it/wiki/developers/) | [API policy](https://feex.it/developers/api-policy/) | [Agent guidance](https://feex.it/wiki/llms.txt)