> ## Content Index > Fetch the complete content index at: https://contextualguides.com/llms.txt > Use this file to discover other available public pages before exploring further. # Materials and Textures Overview - URL: https://contextualguides.com/mat-tex-overview/ - Published: 2026-08-19T13:53:34.000Z - Updated: 2026-08-19T13:58:37.000Z - Description: A conceptual introduction to materials and textures in OctaneRender - Author: Scott Benson - Tags: materials-textures, materials, tutorial, general, #octane-guides, #beginner, #series-Octane Overview, #site-content, #pinned ## About This Guide This is part of a conceptual, DCC-agnostic series on how OctaneRender works. This guide covers the relationship between materials, channels, textures, and projections. ### PDF This guide is also available in [📄 PDF format here](https://contextualguides.com/content/files/2026/08/mat-tex-overview-2.pdf) ## Intro and Overview The material system in Octane is a full replacement for the one in the DCC if you're using a plugin. In certain plugins like C4D, Octane *can* use legacy Standard materials (not Redshift or any other 3rd party ones), but in a very limited capacity. ## Material Types|Material Types Octane has a lot of material types, but they all work off the same system and feed the same information to the engine. There are a lot of them because the system has evolved over time, so they're all kept for compatibility reasons. **Diffuse**, **Glossy**, and **Specular** were the original three surface material types in Octane. **Metallic** was added next to round out most of the surfaces people would need to create. They're kept around for legacy purposes, but they also still have a place because they can help overall performance on scenes with lots of materials. **Universal**, **Standard Surface**, and **OpenPBR** are the "uber material" types. They can all be used to produce nearly any kind of appearance you can think of, and are the go-to for most materials now. The rest of the material types are purpose-built for specific use cases. There's one just for hair, one just to catch shadows, one for toon rendering, and a handful of others that you'll come across over your Octane learning journey. ### Channels ![OG064 001 Channels](https://storage.ghost.io/c/e9/6d/e96d8ca7-ad24-4dc4-b744-c7db76c18621/content/images/2026/08/OG064-001-Channels.jpg)Materials in Octane are broken down into buckets of settings called "channels", each of which controls a specific type of material property. There's one for the overall base color, one for how shiny it is, one for how much light passes through the surface (transmission), etc. Each material type has a unique combination of channels, but in any two that have the same channel, it works the same way under the hood. Materials show up in attribute managers or inspectors in the DCCs, but the intended representation of them is big nodes that have other nodes fed into them. If you're doing anything more than just setting a few basic settings, the node editor is where you want to be when editing one. #### Naming Caveat Even though all channels are the same, some are named different things from material to material. This is done to avoid confusion if you're used to working with, say, a Standard Surface material in Arnold or Redshift, and then come over to Octane and drop in a Standard Surface Material. You're going to be used to looking for a channel called "base color" to alter the overall color of the material, not "albedo", "diffuse", or "color", so it makes sense to stick with industry-standard naming. Fortunately this is mostly contained to color / base color / albedo / diffuse, but if a material is missing a certain channel it may be called something different, or it may just not be available in that material type. ## Textures|Textures ![OG064 002 Textures](https://storage.ghost.io/c/e9/6d/e96d8ca7-ad24-4dc4-b744-c7db76c18621/content/images/2026/08/OG064-002-Textures.jpg) *texture source: [Poly Haven](https://polyhaven.com/a/metal%5Fplate?ref=contextualguides.com)* Textures are chunks of data that are fed into the channels of a material to control how they are expressed in the material. These are simple things like an RGB color or a grayscale value, or complex things like procedurally generated patterns or bitmap images in the form of TIFFs and JPEGs that you have lying around on your computer. **Important:** Every channel that is contributing anything to the appearance of a material has a texture driving it. Nearly all channels can have textures fed into them directly. These channels also come with default textures built in (usually either an RGB or grayscale color). A few of them require intermediate steps to further process the textures (notably displacement and emission). Textures can be mixed, layered, and modified by other nodes prior to hitting the channel, making for a nearly infinite number of combinations to create unique effects. ![OG064 003 Realism](https://storage.ghost.io/c/e9/6d/e96d8ca7-ad24-4dc4-b744-c7db76c18621/content/images/2026/08/OG064-003-Realism.jpg) This is a good place to reference Tenet #3 - Perfection is the enemy. Perfect textures are one of the most common barriers to realistic-looking renders. Nothing in the real world is perfect, so when the brain processes something that is, it causes dissonance. There are plenty of strategies for beating up and randomizing them, and it's definitely something to think about when making each and every one. ### Image Texture Caveat All external image textures (JPEGs, TIFFs, etc.) really should be loaded into one of Octane's image nodes (RGB image, grayscale image, alpha image, etc.). In some DCCs - mainly C4D, but probably others - it's possible to use the DCC's native shader by loading an image directly into the attribute manager/inspector. **Don't do this.** Octane really needs to process the image through its own image texture node before sending it off to the engine to work properly. ## Texture Mapping & Projection|Mapping & Projection 3D models are arbitrarily curved, and 2D textures are flat. Any good cartographer or geography teacher can tell you that mapping a flat thing to a curved thing is hard. The main issues are distortion and seams, but there are other considerations too. In many 3D apps, including Octane, the art of mapping a flat texture to a curved surface is referred to as "projection." There isn't a single be-all, end-all best projection - choosing the right one depends on the topology of the geometry, the type of texture, and a number of other factors. Octane supports several projections to cater to different needs. ![OG064 004 UV Projection](https://storage.ghost.io/c/e9/6d/e96d8ca7-ad24-4dc4-b744-c7db76c18621/content/images/2026/08/OG064-004-UV-Projection-1.jpg)Mesh UV is the most common. This involves creating a flat map (called a UV map) of all the polygons and overlaying the texture on top. An area of the texture that intersects one of the polygons in the 2D map will also do so in the 3D model. Of course this isn't as easy as it sounds, and there are entire guides on this site written on why that is and how to work with it, but here we're just going to be made aware that this is a thing. ## Wrap Up So now we've got a pretty good understanding of the whole chain: Textures feed channels which make up the properties of materials, and the whole thing gets projected on a model in some way. On to the camera!