XO3D Studio · 3D Rendering
Understanding Materials and Textures in 3D Rendering
Where a render becomes a photograph.
Materials and textures decide whether a 3D render feels real or looks like CGI. This guide covers what modern PBR materials are, how texture maps combine to define a surface, and where a strong material pass sits inside a production pipeline.
Overview
The layer that separates good CGI from great CGI.
The model gives you shape. Lighting gives you form. Materials and textures give you surface, everything from anisotropy on brushed metal to subsurface scatter on skin. Get materials right and the render reads as a photograph.
A material is the full surface definition: how a surface takes colour, reflects light, lets light through or glows. A texture map is one image feeding part of that definition, such as colour or roughness. Some materials use no image maps at all, only values or procedural patterns.
PBR materials describe how a surface responds to light using a defined shading model. Their appearance still depends on the lighting, exposure, colour management, geometry and the renderer's implementation. Moving a material between applications may require map conversion, rebaking or changes to unsupported layers. Test the destination material under representative lighting before approval.
This page covers digital materials for rendering. It does not cover render textures in game engines or physical materials for 3D printing.
For the role behind this work, see the 3D artist guide on XO3D Labs. For the broader pipeline, see product modelling and product rendering.
Material, map or texture?
A material is the full surface definition: how a surface takes colour, reflects light, lets light through or glows. A texture map is one image that feeds part of that definition.
A procedural texture produces a pattern from rules rather than from an image. So “materials and textures” are not two names for the same thing: a material may use several maps, one map, or none at all.
Blender’s Principled BSDF documentation shows how many inputs a single material can have beyond its image maps.
What each material map controls (texture maps for 3D models)
Texture maps for 3D models, often called 3D textures or CG textures, each carry one kind of information, and the same holds for textures for rendering a still or a film. Base colour is colour information; the others are data, and a renderer has to read them as data rather than as colour.
The table describes common roles. It is not a universal import recipe: the exact settings depend on the application and its version.
| Map | What it controls | Is it optional? | Common mistake | What the destination needs to know |
|---|---|---|---|---|
| Base colour | The surface colour, without lighting or shadow | Usually used, though a single colour value can replace it | Shadows or highlights painted into the colour | Read as colour, usually in sRGB |
| Roughness | How sharp or blurred reflections are | A single value can do for an even finish | Using a glossiness map without inverting it | Read as non-colour data |
| Metalness | Which areas behave as bare metal | Often a single value for an all-metal or non-metal part | Mid-grey values across surfaces that are either metal or not | Read as non-colour data |
| Normal | Fine surface direction for shading, without changing the shape | Optional | Expecting it to change the silhouette, or the wrong green-channel convention | Non-colour data, and whether it uses the OpenGL or DirectX convention |
| Height or displacement | Surface height, used for bump shading or real displacement | Optional | Expecting bump to change the outline; real displacement needs enough geometry | Non-colour data, plus the height scale and midpoint |
| Ambient occlusion | Shadowing in creases and contact areas | Only where the destination uses it | Multiplying it into base colour for a renderer that calculates its own shadowing | Some real-time formats read it, such as glTF; many shaders, including Blender’s Principled BSDF, have no input for it |
Two notes on the table. First, packed maps put several data maps into the channels of one image. glTF, for example, reads roughness from the green channel and metalness from the blue channel of one texture.
Pack to the destination’s rule, not a general habit. Second, the specular and glossiness workflow and the metal and roughness workflow are different shader models.
Glossiness can often be inverted into roughness within a defined convention, but that does not make every input in the two models interchangeable, so a conversion needs an explicit rule.
Check the destination, not just the map names
A correctly named folder of maps is not a working material. Before a material is approved, check it where it will actually be used:
- UV set and scale. Which UV set each map uses, and whether texture detail matches the product’s real size.
- Map role. Every map is connected to the input it was made for.
- Channel packing. Packed maps match the destination’s channel rule.
- Normal orientation. The green channel follows the destination’s convention. Flipping it is a convention change, not a seam repair.
- Colour interpretation. Base colour and emission are read as colour; roughness, metalness, normal and height as data.
- Unsupported features. Procedural patterns or layers such as coat, sheen and transmission that the destination cannot read.
- Baking. What has to be baked into image maps for the destination to use it.
- Target engine and version. The application and version the material is being prepared for.
- Resolution. Texture size suited to how large the surface appears on screen. The texture resolution calculator and the guide to texture resolution and memory on XO3D Labs help set it.
- Reference lighting and exposure. The lighting setup the material will be approved under.
For a worked explanation of typed maps, channel meanings and normal conventions, see handing material maps between tools on XO3D Labs. Roblox’s documentation on surface appearance is a good example of one destination setting out its own requirements.
A material decision from the Nanuskate ramp
The Nanuskate modular ramp film and stills show why reference and iteration matter. Jack Robertson, the project’s lead 3D artist, built the plastic composite material from scratch using client-supplied images and photographs of comparable finishes.
There was no physical sample. The first pass looked too uniform, so he gave each panel a slight colour shift.
The references also showed fine speckling and small pellet-like detail.
Read as a lesson, the account has three parts:
- Available reference. Images supplied by Nanuskate and photographs of comparable finishes. No physical sample.
- Visible issue in the first material. The assembled ramp read as one uniform surface.
- Revision made. A slight colour shift on each panel, so the ramp reads as individual panels, alongside the fine speckle and pellet-like detail the references showed.
The boundary matters. Appearance inferred from photographs is a judgement about how a surface looks; properties measured from a sample are data. The Nanuskate material is a reference-led judgement, not a measured match, and it does not show that the render is physically accurate.
Layered finishes
One set of metalness and roughness maps does not express every finish. A coated paint has a base layer and a clear coat; fabric can have a soft sheen at grazing angles; glass and gemstones transmit light.
Blender’s Principled BSDF documents coat, sheen and transmission as separate inputs, and support for each varies between renderers and real-time formats. When a layered finish has to travel to a destination that does not support a layer, decide how it will be approximated, and approve that approximation under the shot’s lighting.
A material hand-off manifest
Use a record like this for each material that leaves the studio or moves between tools. The fields below are blank examples, not a populated client record.
| Field | What to record |
|---|---|
| Material ID | A unique name, for example “Panel_Composite_A” |
| Asset and version | The model and revision the material belongs to |
| Reference source and permission | Sample, specification or photographs, and whether you may use them |
| Intended physical scale | The real-world size the texture detail represents |
| Texture roles and channel conventions | Each map’s role, colour or data, packing and normal convention |
| Target application | The renderer, engine or viewer, with its version |
| Approval lighting | The lighting setup and exposure it was approved under |
| Approver | The named person who signed it off |
| Unresolved limitations | Anything approximated, unsupported or still open |
Making your own maps
If you need to build maps rather than brief them, XO3D Labs has free browser tools. The image to PBR generator turns one image into albedo, normal, roughness, displacement and ambient occlusion maps, and the texture and PBR tools cover creating, converting, tiling and checking maps.
Generated maps estimate surface properties from an image; they still need the destination checks above.
Advantages
Why brands commission it.
A shared vocabulary across tools.
Most current renderers and real-time engines understand base colour, roughness, metalness and normal inputs. That makes hand-over easier, but a material moving between applications may still need map conversion, rebaking or changes to layers the destination does not support.
Predictable under changing light.
A PBR material responds to light in a consistent way, so it holds up better than a hand-tuned shader when the lighting changes. It still needs testing under the lighting, exposure and colour management of the actual shot.
A starting point for the next project.
A tuned material can be a starting point for a similar finish on a later project. It still has to be checked against the new product's references; a distinctive finish may need building from scratch.
Easier to adapt for web and AR.
Clear material slots and naming make it easier to prepare a model for a web viewer, configurator or AR. Each destination still has its own limits on map types, texture size and layered effects, so readiness is checked in the destination itself.
Trade-offs
What to plan for.
Texture authoring takes real skill.
Substance Painter, Designer and Mari all take real time to master. Shortcut workflows rarely produce strong surfaces.
The reference has to fit the finish.
A physical sample helps when available, but client photographs and comparable finish references can also guide material work. Record which source was used for each decision.
UV unwrap is unglamorous but critical.
Bad UVs limit texture quality no matter how good the material. Well-unwrapped models render better in every pipeline.
Layered materials add render time.
Multi-layer materials (clearcoat, subsurface) can slow render significantly. Balance quality against budget.
Applications
Where the finished asset ships.
Metal and hard surfaces.
Brushed aluminium, high-polish steel, anodised finishes. Anisotropy, roughness and reflection all handled at the material layer.
Painted and coated finishes.
Automotive clearcoat, powder coat, satin plastic. Multi-layer materials that combine base colour with a top clearcoat for realism.
Fabrics and textiles.
Boucle, velvet, linen, leather. Weave detail, sheen and subsurface all handled inside the material.
Glass and refractive.
Clear glass, coloured glass, gemstones. Refractive index, dispersion and absorption tuned per material.
Organic surfaces.
Wood, stone, skin. Subsurface scatter, grain and layered detail combine for organic realism.
Emissive and technical.
Screens, LEDs, self-lit displays. Emission maps and physically weighted output for accurate exposure.
Process
How the work is produced.
- STAGE 1
Reference gathering.
Collect the available client photographs, finish specifications or physical samples, and record which references informed the material.
- STAGE 2
Base material choice.
Use a close library material when one exists. Build a distinctive finish from reference when a preset does not match, as Jack Robertson, the lead 3D artist on the project, did for the Nanuskate ramp's plastic composite.
- STAGE 3
Texture map creation.
Build separate colour, roughness and surface details. Jack Robertson uses masks to control distinct colours and finishes instead of forcing them into one diffuse map.
- STAGE 4
UV unwrap.
Model UVs unwrapped for texture accuracy. Critical for macro and hero work.
- STAGE 5
Lighting test.
Material tested under multiple lighting rigs to ensure it reads correctly across scenarios.
- STAGE 6
Library archive.
Tuned material saved back to the studio library with a note of its references, so a later project can start from it and check it against its own product.
Who this is for
Built for teams making it happen.
3D artists working in product, film or interactive contexts. Studio TDs setting up material libraries.
Product design teams whose CAD feeds CGI, needing to understand what makes materials work at render time.
Case studies
Recent work.
Petalite EV charger. Full launch content set from one CGI build, applying the disciplines in this guide.
View case study
Sony WF-C710 for ImageNova: two short animated segments for the launch commercial, plus rendered colourways composited into product photography.
View case study
G-Lab gaming keyboard launch. One 3D build driving film, stills, and interactive content.
View case studyTestimonial
The team at XO3D were a pleasure to work with on one of our big projects. They rendered, batched, and saved out literally thousands of images for us. Every single one of these images came out perfect.
FAQ
Common questions, answered.
What is the difference between a material and a texture map?
A material is the full surface definition: how a surface takes colour, reflects light, lets light through or glows. A texture map is one image feeding part of that definition, such as base colour, roughness or a normal map. A material can use several maps, or none.
What is PBR?
Physically based rendering. A way of describing materials with physically meaningful inputs such as base colour, roughness, metalness and normal, so they respond to light in a consistent way. The result still depends on the lighting, exposure, colour management, geometry and renderer, so it is tested under the intended lighting.
What texture maps do modern materials use?
Common maps are base colour, roughness, metalness, normal and height, with opacity, emission and ambient occlusion where the material and destination need them. Not every material needs every map, and each destination reads them in its own way.
How does material work differ for AR?
AR and web viewers usually need optimised geometry and baked PBR maps within a size limit. A normal map can carry fine surface shading from a high-poly source, but it does not change the silhouette, thickness or real displacement, so shape detail that matters has to stay in the geometry.
Do materials need to change per render engine?
Often, at least a little. Base colour, roughness, metalness and normal inputs usually carry across, but layered effects, procedural textures and renderer-specific features may need converting or baking. Check the material in the destination under representative lighting before approval.
Your next project
Give materials a reference.
Separate base colour, texture, surface relief and reflective behaviour when preparing references. Review the material under representative lighting before applying it across every shot.
A route to consider
CGI stills and campaign visuals
Directed product stills with an agreed shot list, material references, environments and delivery formats.
Bring these three things.
- What physical samples are available?
- Which surface details must be visible?
- Under what lighting will they be reviewed?
Start with an outline. We review the product, intended outputs and timing before agreeing the production scope.