At runtime, you can enable or disable shader keywords. When you enable or disable a shader keyword, Unity uses the appropriate shader variant for rendering.
Changing shader variants at runtime can impact performance. If a change in keywords requires a variant to be used for the first time, it can lead to hitches while the graphics driver prepares the shader program. This can be a particular problem for large or complex shaders, or if a global keyword state change affects multiple shaders. To avoid this, ensure that you consider keyword variants in your shader loading and prewarming strategy. For more information, see Shader loading.
In Unity, there are local shader keywords and global shader keywords:
You set the scope of a shader keyword when you declare it. For more information, see Shader keywords: global and local scope.
To enable or disable a global shader keyword, use Shader.EnableKeyword or Shader.DisableKeyword.
To enable or disable a global keyword with a Command Buffer, use CommandBuffer.EnableKeyword, or CommandBuffer.DisableKeyword.
To check the state, use [Shader.IsKeywordEnabled].
To enable or disable a local shader keyword for a graphics shader, use Material.EnableKeyword or Material.DisableKeyword. To check the state, use Material.IsKeywordEnabled.
To enable or disable a local shader keyword for a compute shader, use ComputeShader.EnableKeyword or ComputeShader.DisableKeyword. To check the state, use [ComputeShader.IsKeywordEnabled].
When you author your shader, you declare keywords in sets. A set contains mutually-exclusive keywords.
At runtime, Unity has no concept of these sets. It allows you to enable or disable any keyword independently, and enabling or disabling a keyword has no effect on the state of any other keyword. This means that it is possible to enable multiple keywords from the same set, or disable all the keywords in a set.
When more than one keyword in a set is enabled, or no keywords in a set are enabled, Unity chooses a variant that it considers a “good enough” match. There is no guarantee about what exactly happens, and it can lead to unintended results. It is best to avoid this situation by managing keyword state carefully.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.