Texturing is where product 3D succeeds or fails
Buyers do not evaluate topology. They look at a render and decide, in about a second, whether it looks like the real thing. That judgement is almost entirely a materials judgement: how light rolls off a satin finish, whether the fabric weave holds up at zoom, whether the metal reads as steel or as grey plastic. A correct, unremarkable mesh with excellent materials beats a beautiful mesh with generic ones every time.
It is also where the file size lives. Geometry compresses to a few hundred kilobytes with Draco or Meshopt; textures are the megabytes. Every performance conversation about web 3D is, in practice, a texture conversation.
The PBR map set, one map at a time
Base colour (albedo)
Pure surface colour with no baked lighting or shadow. The most common defect we see in inherited assets is a photo-sourced albedo with highlights baked in, which double-lights the product in every scene.
Metalness
Binary in practice: metal or not. Grey values only appear at transitions such as worn paint over steel. Wrong metalness is why chrome renders as grey plastic.
Roughness
The single most important map for realism. It carries fingerprints, brush direction, polish variation and wear. A flat roughness value is the fastest way to make a product look CG.
Normal
Surface detail without geometry: stitching, grain, knurling, weave. Tangent-space, correct green channel for the target engine, baked from a high-poly source rather than generated from a photo.
Ambient occlusion
Contact shadow in crevices and seams. Subtle by design; heavy AO makes products look dirty under the HDR environments configurators ship with.
Opacity, emissive, clearcoat, anisotropy
Added per material. Glass and mesh fabric need opacity, displays need emissive, car paint and lacquered wood need clearcoat, brushed metal and satin need anisotropy.
This metallic-roughness set is what glTF, USDZ and every real-time engine consume, so it travels from a product page to AR to a marketing render without reauthoring. Older specular-glossiness workflows still turn up in supplier assets and need converting.
UVs and texel density: the part clients never see
Before a single map is painted, the model needs a UV layout: non-overlapping islands, seams hidden along edges the camera will not favour, and a consistent texel density across parts. Texel density is the reason a chair can look wrong even when every individual material is good. If the armrest is textured at twice the pixels-per-centimetre of the seat, the grain scale jumps and the eye catches it immediately.
For configurable products the layout also has to anticipate variants. Swapping a fabric should mean swapping a texture set on a defined material slot, not re-unwrapping the model. Getting this right up front is what makes a catalogue maintainable; How to build a 3D product configurator covers how that structure feeds the rules engine.
Resolution and budgets that work on real devices
- 2K per material as the default for web product models; 4K only for hero surfaces the shopper can zoom into; 1K for small parts, hardware and interiors.
- Pack metalness, roughness and AO into a single ORM texture's channels: three maps for the cost of one download.
- Ship KTX2 (Basis Universal) rather than PNG or JPG. It stays compressed on the GPU, which cuts both transfer size and video memory.
- Target a sub-3 MB initial payload for a product page and keep secondary variant textures lazy-loaded on first selection.
- Power-of-two dimensions, mipmaps enabled, and no 4K map on a part that occupies 60 pixels on screen.
Colour accuracy against the physical product
Returns caused by "the colour was different online" are a materials problem with a financial number attached. The workflow that avoids it: work from physical samples or calibrated swatch scans rather than supplier JPEGs, author in a known colour space with base colour in sRGB and data maps in linear, review under the same HDR environment the configurator ships with, and sign off against a reference photograph of the real item side by side with the render.
Where a brand has a standard finish used across many products, a signature oak, a house powder-coat, it should be authored once as a shared master material and reused, not re-created per product by whoever is on the job that week.
The QA checklist we run before delivery
- No baked lighting or shadow in base colour.
- Metalness is 0 or 1 except at deliberate transitions.
- Roughness varies across the surface; no flat grey fills.
- Normal map green channel matches the target engine; no inverted detail.
- Texel density consistent across all parts of the product.
- Tiling materials show no visible repeat at the default camera distance.
- Every variant slot resolves to a complete map set: no missing roughness on the eleventh fabric.
- Model reviewed in at least three HDR environments, not just the studio one.
- USDZ and GLB exports both render correctly; iOS Quick Look is checked on device.
- Final payload measured against the performance budget, not estimated.
What to ask a texturing partner for
Request the map set and its resolutions in writing, the UV and texel density standard, the export formats (glTF/GLB, USDZ, plus the DCC source), the performance budget they will hold, and how shared materials are versioned across the catalogue. A studio that cannot answer the texel density question is going to hand you a catalogue that looks inconsistent by the fortieth SKU. The platform layer matters too: Product configurator software: 12 features that matter covers what the software side has to support for these assets to pay off.
Frequently asked questions
If you need these materials produced for your catalogue, our 3D texturing and PBR material services cover commissioned work on your product assets, from source review to platform-ready delivery.
What are 3D texturing services?
The production of a model's material layer: UV layout plus a PBR map set authored so the product responds correctly to light in renders, configurators and AR. Usually sold alongside modelling, sometimes as a standalone service on client-supplied geometry.
What maps are in a PBR texture set?
Base colour, metalness, roughness, normal and ambient occlusion as standard, plus opacity, emissive, clearcoat, anisotropy or height where the material calls for it.
What resolution should e-commerce textures be?
2K per material by default, 4K for hero close-up surfaces, 1K for small parts. Consistent texel density across parts matters more than any single resolution number.
Can you texture models we already have?
Yes. Supplier and CAD-derived meshes usually need a UV pass and often light retopology first, which we quote after inspecting the files.
How long does texturing take per product?
A single-material product is typically a day or two. A multi-material product with a variant library runs longer, and shared master materials cut per-SKU time significantly once the first few are done.
Why do textures matter more than polygon count on the web?
Compressed geometry is small; textures are the bulk of the download and the bulk of perceived quality. A modest mesh with correct roughness and normals looks premium, a dense mesh with flat maps does not.