The OpenGL Reference Pages
The reference pages for OpenGL 4 include complete descriptions of all OpenGL commands contained in the OpenGL 4 Specification and the functions contained in the OpenGL Shading Language 4.40 Specification.
The reference pages for OpenGL 3.3 include complete descriptions of all OpenGL commands contained in the Core Profile of the OpenGL 3.3 Specification.
The legacy OpenGL 2.1 reference pages include descriptions of all OpenGL commands contained in the OpenGL 2.1 Specification, including commands that have been deprecated and removed in more modern versions of OpenGL (but are still included in compatibility profiles of OpenGL). Also included are descriptions of GLU and GLX entry points.
Quick Reference Cards
Several quick reference guides are available in PDF format from the links below. The quick reference guides are fold-out annotated lists of the functions included in OpenGL, along with their parameters and other useful information.
- OpenGL 4.4 Reference Card
- OpenGL 4.3 Reference Card
- OpenGL 4.2 Reference Card
- OpenGL 4.2 (Core Profile) Reference Card
- OpenGL 4.1 Reference Card
- OpenGL 4.0 Reference Card
- OpenGL 3.2 Reference Card
The OpenGL Registry, hosted outside of the SDK, contains the formal Specifications for OpenGL and the OpenGL Shading Language, as well as for companion APIs like GLX and GLU. Specifications are the authoritative documents about how OpenGL is intended to work. They are also the most difficult to read, being written primarily for OpenGL implementers, not developers using OpenGL; so you may find the reference pages combined with tutorials to be a better choice.
The Registry also contains specifications for extensions describing optional features of OpenGL, and header files defining interfaces for extensions. Extension specifications are written as supplements to the core OpenGL Specification. Most new features are first introduced as extensions and only later become part of a core OpenGL version, so using extensions is important to staying current with the evolution of the API.
Please use the public bugtracker to let us know about any issues you find.