Shader Reference

Shaders in Unity can be written in one of three different ways:

• as surface shaders,
• as vertex and fragment shaders and
• as fixed function shaders.

The shader tutorial can guide you on choosing the right type for your needs.

Regardless of which type you choose, the actual meat of the shader code will always be wrapped in a language called ShaderLab, which is used to organize the shader structure. It looks like this:

Shader "MyShader" {
    Properties {
        _MyTexture ("My Texture", 2D) = "white" { }
        // other properties like colors or vectors go here as well
    }
    SubShader {
        // here goes the 'meat' of your
        //  - surface shader or
        //  - vertex and program shader or
        //  - fixed function shader
    }
    SubShader {
        // here goes a simpler version of the SubShader above than can run on older graphics cards
    }
} 

We recommend that you start by reading about some basic concepts of the ShaderLab syntax in the sections listed below and then to move on to read about surface shaders or vertex and fragment shaders in other sections. Since fixed function shaders are written using ShaderLab only, you will find more information about them in the ShaderLab reference itself.

The reference below includes plenty of examples for the different types of shaders. For even more examples of surface shaders in particular, you can get the source of Unity's built-in shaders from the Resources section. Unity's Image Effects package contains a lot of interesting vertex and fragment shaders.

Read on for shader reference, and check out the shader tutorial as well!

• Writing Surface Shaders
  • Surface Shader Examples
  • Custom Lighting models in Surface Shaders
  • Surface Shader Lighting Examples
  • Surface Shaders with DX11 Tessellation
• Writing vertex and fragment shaders
  • Vertex and Fragment Shader Examples
  • Accessing shader properties in Cg
  • Providing vertex data to vertex programs
  • Built-in shader include files
  • Predefined shader preprocessor macros
  • Built-in state variables in shader programs
  • Making multiple shader program variants
  • GLSL Shader Programs
• ShaderLab syntax: Shader
  • ShaderLab syntax: Properties
  • ShaderLab syntax: SubShader
    • ShaderLab syntax: Pass
      • ShaderLab syntax: Color, Material, Lighting
      • ShaderLab syntax: Culling & Depth Testing
      • ShaderLab syntax: Texture Combiners
      • ShaderLab syntax: Fog
      • ShaderLab syntax: Alpha testing
      • ShaderLab syntax: Blending
      • ShaderLab syntax: Pass Tags
      • ShaderLab syntax: Name
      • ShaderLab syntax: BindChannels
      • ShaderLab syntax: Stencil
    • ShaderLab syntax: UsePass
    • ShaderLab syntax: GrabPass
    • ShaderLab syntax: SubShader Tags
  • ShaderLab syntax: Fallback
  • ShaderLab syntax: CustomEditor
  • ShaderLab syntax: other commands
• Advanced ShaderLab topics
  • Unity's Rendering Pipeline
  • Performance Tips when Writing Shaders
  • Rendering with Replaced Shaders
  • Custom Material Editors
  • Using Depth Textures
  • Camera's Depth Texture
  • Platform Specific Rendering Differences
  • Shader Level of Detail
• ShaderLab built-in values

Page last updated: 2011-01-14