Welcome to RenderDoc - a graphics debugger, currently available for D3D11 and OpenGL development on windows.

This document serves primarily as reference guide, introductory document and explanation of which features are available in RenderDoc and how to best use them.

The latest information and discussion is always available on the GitHub wiki wiki on GitHub https://github.com/baldurk/renderdoc/wiki .

# License

RenderDoc is released under the MIT license, so there are no restrictions on your use of it either commercial or non-commercial. This includes the source release available on the GitHub repository Source on GitHub https://github.com/baldurk/renderdoc/issues .

Details of the licenses of third party software used in RenderDoc are included in the LICENSE file in the RenderDoc directory as well as in the .

# How to browse this documentation

If you just want to dive straight in and learn how to get started using RenderDoc consider looking at the section which gives a simple introduction on how to get started. Afterwards there are reference pages on each of the windows available in RenderDoc which can be referred to as you use the program, or skimmed to get a feel for the functionality available.

Those of you familiar with other graphics debuggers will likely find much of RenderDoc recognisable, you might want to check out the , , or browse the How Do I... ? sections which detail how some common tasks are accomplished.

Regardless of your experience or patience for documentation it's recommended that you read the as this details known bugs and current limitations of the program.

# Important notes

- RenderDoc is not yet bug free! It is pretty stable but you will still likely encounter bugs depending on your use case. I am always happy to spend time to fix them and I can work with you even if you cannot share any details about your project. Get in touch (see below) and I will actively fix your bug!

- On the other side of the coin, please do give feedback when RenderDoc works for you and request features that would make your life easier or improve your workflow.

- There are a few common issues you might run into, so if you have any problems check the , or the issues page on github Issues on github https://github.com/baldurk/renderdoc/issues to see if it's been reported.

# Contact info, Feedback, Bug reports

If you want to get in touch with any feature requests, suggestions, comments etc then feel free to contact me: Baldur Contact.

Bug reports can be submitted directly via email, or also on the github repository Issues on github https://github.com/baldurk/renderdoc/issues where you can also find the full source code.

The builds page Build and release downloads https://renderdoc.org/builds always has the latest stable and beta build downloads, as well as builds made from the source code each night for the bleeding edge. Stable releases update relatively infrequently and are tested the most to ensure they're as reliable as possible. Beta releases update more often to expose the latest fixes and features from the source, but risk more bugs sneaking in.

RenderDoc Homepage
Go to the RenderDoc Homepage
http://renderdoc.org/
Builds page
Build and release downloads
https://renderdoc.org/builds