What is the albedo/base color map?

Definition of Albedo / Base Color Map

The albedo or base color map describes the pure object colors of a surface— without baked-in lighting, shadows, reflections, or gloss. In Metal/Roughness PBR, it serves as the color base; metalness, roughness, and the normal map separately control how light interacts with the surface. See the basics in our glossary on PBR—Physically Based Rendering. Additionally, NVIDIA Omniverse confirms in its template documentation that “Albedo defines the base color without light or reflections.”

Albedo/Base Color Map – Key Information at a Glance

• Purpose: Description of the material based solely on color; no shading or gloss.
• Color Space (Import): sRGB/Color for Albedo; Non-Color for technical maps (Normal, Roughness, AO). See the Blender Color Management Manual for details.  
• Standard reference: In glTF 2.0, the texture is called `baseColorTexture `—part of the core material in the specification's Metal/Roughness model.  
• Practical Tip: For Web/AR rendering via glTF, albedo textures can be efficiently compressed using KTX2/Basis Universal.  

What Is the Albedo/Base Color Map? Practical Example: Natural Stone Floor with PBR Maps

This photo gallery shows, step by step, how an albedo/base color map and supplementary PBR maps are created from a reference photo. It explains color (without lighting), shape, and the appearance of cavities separately—to ensure consistent results in renderings, web viewers, and AR.

1. Untextured Mesh / UV Grid

2. Albedo / Base Color

3. Normal Map (Tangent Space)

4. Height / Displacement (Grayscale)

5. Final Rendering (Beauty Pass)

Why is the albedo/base color map crucial for consistent 3D renderings in the PBR workflow?

The strict separation of material roles (Albedo vs. Metalness/Roughness/Normal/AO) prevents duplicate effects and ensures that assets look consistent across engines —from offline rendering to the 3D viewer on the web or Virtual Showroom. The Khronos overview of PBR in glTF provides a concise introduction; an unlit mode (e.g., the glTF extension KHR_materials_unlit) displays the albedo “in its purest form.”

Practical examples (furniture & home living)

Oak, oiled vs. lacquered: The albedo contains wood tone & grain - not lacquer highlights. Gloss comes from roughness/clearcoat (see roughness map).

Velvet/Velour: The perceived “wipe direction” is determined by the microstructure → Normal/Roughness, not by the albedo (see normal map).

CI color fidelity: Exact color counts for fronts/upholstery - sRGB import for albedo, correct linearization in the engine; technical maps as non-color.  

Mini workflow: Create albedo/base color map correctly (steps & best practices)

Step 1: Set the reference: Examine the material sample under neutral light (D50/D65); lock in the white balance.

Step 2: Capture & de-lighting: rectify scans/photos; do not transfer any shadows/gloss to the albedo (spot retouching if necessary).

Step 3: Set the color space correctly: Import Albedo as sRGB/Color; import Normal/Roughness/AO as Non-Color (see the Blender Manual: Color Management). ‍

Step 4: PBR Validation: Use Adobe Substance to check whether base color values are “PBR-safe”— PBR Albedo Safe Color and BaseColor/Metallic Validate are designed for this purpose:

– PBR Guide (Adobe Substance)

– PBR Albedo Safe Color

– PBR BaseColor/Metallic Validate

It's also a good idea to run a test using the tilable texture checker to ensure that solid color areas remain consistent when repeated.

Step 5: Delivery & Web: Master lossless (PNG/TIFF). For glTF target KTX2/BasisU (small, fast upload) - check visually.  

"Albedo vs. Diffuse vs. AO" – Comparison Table for the PBR Workflow (Definition, Color Space, Role)

For metals, the base color encodes the F0 reflection (colored specular reflection); for dielectrics, it encodes the diffuse albedo.

For Web/AR delivery, KTX2/BasisU textures are GPU-friendly and offer significant file size advantages (KTX – GPU Texture Container).

Common errors & quick fixes

“X vs. Y” – Clear Distinctions

• Albedo vs. Diffuse: “Diffuse” is part of the Specular/Glossiness workflow; it often includes baked-in light components. Albedo/Base Color in the Metal/Roughness workflow contains only color. Recommended reading for context: Albedo vs. Diffuse – Community Discussion (Blender StackExchange) as well as the glTF extension KHR_materials_pbrSpecularGlossiness for the older workflow model.  
• Albedo vs. AO: AO is ambient occlusion → separate map, not "baked in" (Ambient Occlusion); glTF handles AO separately.  

FAQ - Albedo / Base Color Map

What distinguishes the albedo/base color from the “material color” in the PBR workflow?

The albedo/base color is the pure color texture without any light components; gloss, reflections, and micro-relief are provided by other maps. In the glTF 2.0 standard, this is defined as `baseColorTexture` (see glTF 2.0 – Materials). For a basic understanding of this approach, see PBR – Physically Based Rendering. NVIDIA Omniverse also describes albedo as a pure base color.

Albedo vs. Diffuse vs. AO: What Shouldn't Be Included in the Base Color?

Diffuse originates from specular/gloss pipelines and may contain residual shading—see the discussion on Albedo vs. Diffuse (Blender StackExchange). AO should be handled separately (see Ambient Occlusion). Specular and relief are controlled via the roughness map and normal map —they are not “baked into” the albedo.

Which color space is correct for albedo—and how do I set it?

The albedo is typically imported as sRGB/Color for the input texture; technical maps (Normal, Roughness, AO) are imported as Non-Color. This is documented in the Blender Manual on color management. In the glTF material system, the Base Color is part of the Metal/Roughness standard—this ensures consistent interpretation across viewers and engines.

How do I check the "true" albedo—and why is that important for Web/AR?

Enable an unlit mode to view the base color without lighting; for glTF, use the KHR_materials_unlit extension. For fast loading times in a 3D viewer on the web or in AR, use texture compression such as KTX2/Basis Universal —this significantly reduces the data size.

What bit depths and formats are recommended—and how do I keep PBR values "clean"?

For albedo, 8-bit PNG/TIFF files are usually sufficient; 16-bit is worth using for extensive grading or compositing. Blender Color Management continues to apply for color spaces. Check values using Adobe validators (PBR Albedo Safe Color), and follow the guidelines in OmniPBR – Albedo regarding parameters and color spaces.

How do I handle scans and photos so that no shadows or glare end up in the albedo?

Aim for "smooth" references right from the capture stage; retouch any imperfections if necessary. You can check this using the unlit view (see KHR_materials_unlit). AO remains separate (Ambient Occlusion); for an explanation of why "Diffuse" can be problematic, see Albedo vs. Diffuse (Blender StackExchange).

How do I optimize the albedo for glTF in e-commerce/viewers?

Save the master texture in a lossless format (PNG/TIFF), then generate a KTX2/BasisU variant from it for web/AR (see KTX – GPU Texture Container). Test the result directly in the 3D viewer on the web to check sharpness, color tones, and compression artifacts under real-world conditions.

How does albedo fit into the overall PBR workflow with roughness and normals?

Albedo provides the color information, the roughness map controls specular brightness and reflections, and the normal map defines the micro-relief. This interplay is at the heart of PBR (Physically Based Rendering) and is standardized in glTF 2.0 materials— ideal for reproducible results across different engines.