Early Fragment Test

From OpenGL Wiki
(Redirected from Early Depth Test)
Jump to: navigation, search

Early Fragment Test (sometimes called Early Depth Test) is a feature supported by many GPUs that allow the certain Per-Sample Processing tests that discard fragments to proceed before fragment processing in the rendering pipeline. This feature can be active in two ways: as an optimization and by explicit user control (with OpenGL 4.2 or ARB_shader_image_load_store.

Affected operations

The following Per-Sample Processing steps can be performed before the fragment shader:

Note that with OpenGL 4.2 or ARB_shader_image_load_store, the pixel ownership and scissor tests will always be performed early.


Early fragment tests, as an optimization, exist to prevent unnecessary executions of the Fragment Shader. If a fragment will be discarded based on the Depth Test (due perhaps to being behind other geometry), it saves performance to avoid executing the fragment shader. There is specialized hardware that makes this particularly efficient in many GPUs.

The most effective way to use early depth test hardware is to run a depth-only pre-processing pass. This means to render all available geometry, using minimal shaders and a rendering pipeline that only writes to the depth buffer. The Vertex Shader should do nothing more than transform positions, and the Fragment Shader does not even need to exist.

This provides the best performance gain if the fragment shader is expensive, or if you intend to use multiple passes across the geometry.


The OpenGL Specification states that these operations happens after fragment processing. However, a specification only defines apparent behavior, so the implementation is only required to behave "as if" it happened afterwards.

Therefore, an implementation is free to apply early fragment tests if the Fragment Shader being used does not do anything that would impact the results of those tests. So if a fragment shader writes to gl_FragDepth​, thus changing the fragment's depth value, then early testing cannot take place, since the test must use the new computed value.

Note: Do recall that if a fragment shader writes to gl_FragDepth​, even conditionally, it must write to it at least once on all codepaths.

There can be other hardware-based limitations as well. For example, some hardware will not execute an early depth test if the (deprecated) alpha test is active, as these use the same hardware on that platform. Because this is a hardware-based optimization, OpenGL has no direct controls that will tell you if early depth testing will happen.

Similarly, if the fragment shader discards the fragment with the discard​ keyword, this will almost always turn off early depth tests on some hardware. Note that even conditional use of discard​ will mean that the FS will turn off early depth tests.

Note: All of the above limitations apply only to early testing as an optimization. They do not apply to anything below.

Explicit specification

Early Fragment Tests
Core in version 4.5
Core since version 4.2
Core ARB extension ARB_shader_image_load_store

More recent hardware can force early depth tests, using a special fragment shader layout qualifier:

layout(early_fragment_tests) in;

This will also perform early stencil tests.

There is a caveat with this. This feature cannot be used to violate the sanctity of the depth test. When this is activated, any writes to gl_FragDepth​ will be ignored. The value written to the depth buffer will be exactly what was tested against the depth buffer: the fragment's depth computed through rasterization.

This feature exists to ensure proper behavior when using Image Load Store or other incoherent memory writing. Without turning this on, fragments that fail the depth test would still perform their Image Load/Store operations, since the fragment shader that performed those operations successfully executed. However, with early fragment tests, those tests were run before the fragment shader. So this ensures that image load/store operations will only happen on fragments that pass the depth test.

Note that enabling this feature has consequences for the results of a discarded fragment.