Textured Maps in 3D Modeling: Types and How They Work

Textured maps are the images and grayscale masks that tell a 3D renderer or game engine what a surface looks like: its color, its bumps, how shiny it is and whether it is metal. Without them a 3D model is just gray plastic.

This guide covers every common type of texture map, how a physically based (PBR) workflow uses them, and how texture maps are made and applied to a model, whether that model is heading into a game engine or a product render.

3D Studio builds and textures 3D models for game studios and product teams that need this work done to a fixed price and schedule.

What is texture mapping

Texture mapping is the process of wrapping one or more 2D images onto the surface of a 3D object, using UV coordinates to say which part of the image lands on which part of the mesh. Once a model has a UV map, the renderer can look up color, roughness and other properties for every point on the surface.

People search for this idea under a few different names: texture mapping, 3D texture, 3D material images and 3D textures. They all point to the same thing: 2D image data applied to a 3D surface so the object reads as a real material instead of plain gray geometry.

Texture mapping also cuts down how much geometry a model needs. A brick wall can be a flat plane with a normal map instead of thousands of individual bricks modeled as geometry, so the scene renders faster and the file stays smaller.

Types of texture maps

A single texture map rarely does the whole job. Most materials use a stack of maps, each one controlling a different property. Here are the ones you will meet most often.

Base color and albedo

The base color map, also called albedo, is the plainest of the set. It stores only the object’s color with no shadow, shine or reflection baked in, so the same map keeps working under any lighting the scene uses later.

Normal maps

A normal map stores three values, red, green and blue, as directions instead of colors. Those directions tell the renderer which way each tiny patch of surface is facing, so light and shadow fall as if there really were bumps and dents there. The base mesh underneath stays exactly as low poly as before.

Tip: a normal map fakes depth with lighting only. Baked in bumps do not change the model’s silhouette, so keep large shape changes in the mesh itself and leave fine detail, like pores, stitching or scratches, to the normal map.

Roughness and specular

Roughness sets how sharp or blurry a reflection looks: a low value gives a mirror like polish, a high value scatters light into a soft matte finish. Some non-PBR workflows use a specular map instead, which stores the color and strength of reflected light directly rather than deriving it from roughness and metalness.

Metalness

The metalness map is a simple black and white mask: white marks the parts of the surface that behave like bare metal, black marks everything else. A renderer combines it with the base color and roughness maps to decide how each pixel should reflect light.

Height and displacement

Height maps go further than normal maps by actually moving the model’s surface up and down, point by point, based on how light or dark each pixel is. The result holds up from a grazing angle or in a close up render, at the cost of a denser mesh and a heavier scene to compute.

Ambient occlusion and opacity

An ambient occlusion (AO) map darkens the creases, corners and contact points where light naturally struggles to reach, which adds believable soft shadow without an extra light source. An opacity map does the opposite job for transparency: it marks which parts of a surface should let light through, used for glass, leaves and fabric mesh.

PBR texture maps

PBR (physically based rendering) is the standard texture workflow across most current game engines and 3D renderers, including Blender’s Principled shader and Adobe’s Substance 3D tools. A PBR material is built from the base color, normal, roughness, metalness, height and AO maps described above, combined so the surface reacts to light in a consistent way under any lighting setup.

Older, non-PBR workflows use a different but related set of maps: diffuse instead of base color, bump instead of normal, and specular instead of roughness and metalness together. The two systems solve the same problem in different ways, which is why a search for one term often turns up the other.

Albedo vs diffuse maps

Albedo and diffuse maps look almost identical and are often used as if they mean the same thing, but there is one real difference. An albedo map is meant to hold flat, pure color with no shadow baked in, since the PBR lighting model calculates all of the shading itself. A diffuse map can carry some baked in shadow and color variation from its source photo, which made older non-PBR renders look more finished without extra lighting work, at the cost of that shadow being wrong under a different light.

How texture maps are made and applied

Building a full set of texture maps for a model usually follows the same order:

1. UV unwrap the model so every point on the mesh has a matching 2D position, using UV mapping software.
2. Paint or photograph the base color, either by hand, from photographed reference, or generated in a texturing application.
3. Bake the normal, height and ambient occlusion maps from a high detail sculpt down onto the low poly mesh that will actually be used.
4. Set roughness and metalness, or specular, to match the real material: metal, wood, fabric, skin or glass.
5. Load the finished maps into the renderer or game engine and check them under more than one lighting setup before moving on.

Texture resolution is chosen for where the model will be seen. A background prop might only need a small texture, while a hero product shot or a close up character usually calls for 4K, and a single hero asset for print or a cinematic might go up to 8K per map.

Texturing for games and product models

Game studios are among the largest group asking studios to texture 3D assets, since a playable model needs the full PBR map set to look right in real time while staying inside a strict polygon and texture budget. 3D Studio models and textures game ready assets, including the low poly geometry the maps are baked onto, through its work with game studios.

Product and furniture models are textured for a different goal: a single well lit hero shot or a rotating turntable rather than a real time frame budget, so the maps can run at a higher resolution and the mesh can carry more detail directly. This is the same reasoning behind 3D product rendering: the surface only needs to hold up from the camera angles actually used.

Whatever the end use, a model that arrives with clean, real world proportions makes texturing straightforward. A model built from vague reference or unchecked mesh topology forces a texture artist to fix the mesh before any map can be painted.

Questions about texture maps

What is a specular map?

A specular map stores the color and strength of light an object reflects, painted directly rather than calculated from roughness and metalness. It is common in older non-PBR workflows and still shows up in some game engines as an alternative to a metalness map.

Do I need every texture map for every model?

No. A simple matte object might only need a base color and a roughness map. Complex, close up or reflective surfaces are the ones that benefit from adding normal, metalness, height and ambient occlusion maps on top.

Can I reuse one texture map on more than one model?

Yes, a tileable material such as brick, wood or fabric can be reused across many models. A unique object, like a character’s face or a branded product, usually needs its own one off set of maps.

What resolution should a texture map be?

It depends on how close the camera gets. Background objects can use a small map, while a hero product shot or a close up character usually needs 4K, and a single hero asset for print or a cinematic might go up to 8K.