PBR Texture Maps Explained: Albedo, Normal, Roughness, Metallic, AO, Height, and Emission

Settings Reference

Color and light-producing maps

These channels contain visible color or add light contribution and are normally treated as sRGB color data.

• Base color / albedo: Stores the intrinsic surface color without baked directional lighting, glossy highlights, or view-dependent reflections. Correct it when shadows, highlights, white balance, or captured perspective are painted into the source.
• Emission / emissive: Marks regions that contribute visible self-lit color independently of ordinary reflected light. Use it for screens, lamps, neon, lava, powered panels, and stylized glow—not as a substitute for scene lighting.

Surface-direction and relief maps

These channels change how the surface faces light or how the shader offsets geometry.

• Normal map: Stores an XYZ direction in RGB so small surface detail changes lighting without adding mesh geometry. Confirm tangent space, green-channel orientation, strength, and linear import whenever lighting appears inverted or swollen. Use Normal Map vs Bump Map when the representation choice is still unresolved.
• Height / displacement map: Stores scalar relief, commonly black for low and white for high, for parallax, tessellation, or displacement workflows. Use it only when the destination shader consumes height; verify midpoint and displacement scale before export.

Material-response masks

These grayscale or mask channels should normally be imported as linear data.

• Roughness / smoothness: Controls reflection spread. Higher roughness produces broader, dimmer highlights; smoothness is the inverse convention. Tune it under moving reflections. Avoid judging it from the grayscale map alone.
• Metallic / metalness: Classifies surface regions as conductors or dielectrics and changes how the shader divides reflected and diffuse light. Keep clean material regions near black or white; preserve intentional transition pixels, corrosion, dirt, and antialiasing.
• Ambient occlusion: Applies limited local attenuation in cavities and contact regions when the renderer provides an AO input. Reduce it when lighting looks double-baked or dirty; do not paint broad cast shadows into AO.
• Opacity / alpha: Controls cutout or transparency coverage according to the material blend mode. Choose cutout, blend, or opaque behavior explicitly and remove unused alpha when it changes compression or memory cost.

Choose and verify a PBR map set

A PBR material separates visible surface properties into coordinated texture maps. Base color describes surface color, normal and height describe relief, roughness controls reflection spread, metallic classifies conductors, ambient occlusion adds limited local contact shading, and emission identifies self-lit regions.

Step 1: Identify the destination shader

List the inputs the renderer exposes, including whether it expects roughness or smoothness, OpenGL or DirectX normals, a separate AO input, displacement support, and any packed-channel layout.

Step 2: Approve the base-color source

Remove perspective distortion, baked shadows, highlights, and unwanted seams before deriving technical maps. Errors in the source propagate into every generated channel.

Prepare an image source

Step 3: Build only the required maps

Generate the coordinated channels from the same source and dimensions. Treat metallic, roughness, height, AO, and emission as editable interpretations that require visual review.

Generate the PBR stack

Step 4: Validate data meaning

Check that color maps remain color, scalar maps remain grayscale where expected, normal vectors are valid, and all files share the same UV layout and dimensions.

Validate a PBR set

Step 5: Test under neutral and production lighting

Rotate the material under a neutral environment first, then test it in the actual scene. Roughness, normals, emission, and AO cannot be judged reliably from flat thumbnails alone. If the surface remains unexpectedly glossy, run the roughness troubleshooting guide before retuning unrelated channels.

Common Pitfalls

• Exporting every available map even when the shader ignores several of them.
• Treating a normal map as sRGB color or treating base color as linear scalar data.
• Using a metallic map as a gray shininess control instead of a material-class mask.
• Multiplying broad shadows into AO and then lighting the same shadow a second time in the engine.
• Confusing height with normal data or expecting either map to change the mesh silhouette automatically.
• Packing channels before confirming each source map and the target packing convention.

Which PBR texture maps are essential?

Base color, normal, and roughness form a common practical starting set. Metallic is essential for mixed metal and non-metal materials. AO, height, emission, and opacity are conditional on the surface and shader.

Is albedo the same as diffuse?

They are often used interchangeably in production, but an albedo or base-color input in a metalness workflow should exclude directional lighting and follow the renderer’s physically based expectations.

Is smoothness the same as roughness?

They describe inverse conventions: normalized smoothness equals one minus roughness. Confirm which convention and channel the destination shader expects.

Can one photo contain physically accurate PBR properties?

No. A single lit image does not directly measure hidden geometry or independent roughness, metalness, height, and AO. It can support useful authoring estimates, but the maps still require material knowledge and scene review.

What is an ORM texture?

ORM commonly packs occlusion into red, roughness into green, and metallic into blue for glTF-style workflows. Other engines use different packed layouts, so verify the destination convention.