01 / 21

Texture
Baking

Learn how to bake and transfer textures in Blender: flatten complex shading into simple image maps for faster rendering and portable assets.

Blender

What Is Texture Baking?

Texture baking is the process of pre-computing complex surface information (lighting, shadows, colors, normals) and storing the result as a flat 2D image (a texture map). Instead of calculating these effects in real time, the renderer reads them directly from the baked image.

Why Bake Textures?

Performance
Game engines and real-time viewers can display baked maps with minimal GPU cost, avoiding expensive per-frame calculations.
Portability
Baked textures are simple image files (PNG, EXR) that work across any software, engine, or platform without special shaders.
Simplification
Complex procedural node trees with dozens of nodes can be "flattened" into a single image, keeping the look but removing complexity.

The UV Map Connection

3D Mesh unwrap UV Layout UV Island Bake onto this map

The Core Principle

Shader Nodes Noise Texture Color Ramp Bump Map Mix Shader (complex node tree) BAKE Cycles Renderer evaluates each UV pixel OUTPUT Image Texture (flat .png / .exr) Complex Nodes → Single Image → Fast Display

Common Bake Types

Diffuse
Captures the base color of the surface without specular highlights. The most common bake type.
Normal
Stores surface angle information as RGB values, allowing a low-poly mesh to display high-poly detail.
AO
Ambient Occlusion: records how much ambient light reaches each point, darkening crevices and cavities.

Procedural vs. Baked

Procedural Texture Baked Texture
Storage Math formula (nodes) Image file (pixels)
Resolution Infinite (scale-independent) Fixed (e.g., \(1024 \times 1024\))
Render Cost Recalculated every frame Single texture lookup
Editability Fully parametric Edit in image editor only
Portability Blender-only (node tree) Universal (any engine)
Best For Blender renders, iteration Game engines, export

High-Poly to Low-Poly Transfer

High-Poly Source 50,000 faces bake normals Normal Map apply Low-Poly Target 500 faces Looks detailed, runs fast Blender casts rays from low-poly to high-poly to capture detail

How to Bake in Blender

1
UV Unwrap your target mesh. Ensure no overlapping UV islands and reasonable texel density.
2
Create an Image Texture node in the Shader Editor. Set the desired resolution (e.g., \(1024 \times 1024\)). Select it so it is the active node.
3
Set the render engine to Cycles. Baking is a Cycles-only feature in Blender.
4
Choose the bake type under Render Properties → Bake. Select Diffuse, Normal, AO, or Combined.
5
Click "Bake" and wait for Cycles to finish. The result writes into your selected Image Texture node.
6
Save the image (Image → Save As). Blender does not auto-save baked textures.

Resolution and Texel Density

The baked image has a fixed resolution. Choosing the right size depends on how close the camera (or player) will get to the surface. More pixels per UV face means sharper detail, but larger file sizes.

\(512 \times 512\)
Small props, distant objects, mobile games. Fast to bake.
\(1024 \times 1024\)
Standard for most game assets. Good quality-to-size balance.
\(2048 \times 2048\)
Hero assets, characters. High detail, larger memory footprint.
\(4096 \times 4096\)
Film/archviz closeups. Very high memory: use sparingly.

Example: Baking a Procedural Material

Noise Texture Color Ramp Principled BSDF Material Output Bake Diffuse Image Texture (active, selected) ✓ Bake writes Noise + Ramp result into this image

Example: Normal Map Transfer

1
Sculpt your high-poly version with all the fine details (wrinkles, scratches, pores).
2
Create a low-poly version with clean topology suitable for animation or games.
3
UV unwrap the low-poly. Add an Image Texture node and select it.
4
Select both objects: high-poly first, then low-poly (so low-poly is the active object).
5
In Bake settings, choose "Normal" and check "Selected to Active". Adjust Ray Distance (cage extrusion).
6
Click Bake. Blender casts rays from the low-poly surface outward to find the high-poly and records the normal difference.

Example: Baking Ambient Occlusion

Scene Geometry Object dark dark blocked bake AO Map White = lit, Dark = occluded

Ray Distance and Cage

When baking from a selected object to the active object (high-to-low transfer), Blender needs to know how far to cast rays from the low-poly surface to find the high-poly. This is controlled by two settings:

Extrusion
Pushes the ray origin outward along each face normal by this distance. Increase it if parts of the high-poly are missed.
Max Ray Distance
Limits how far rays travel. Set to 0 for unlimited, or a small value to avoid picking up unrelated geometry.

Common Mistakes

✕ No Active Image Node
Forgetting to select the target Image Texture node. Blender has nowhere to write the result and throws an error.
✕ Using Eevee
Baking only works in Cycles. Switching to Eevee disables the bake button entirely.
✕ Overlapping UVs
UV islands that overlap cause bake data to overwrite itself, producing garbled results. Always check for overlaps.
✕ Not Saving the Image
Blender does not auto-save baked images. If you close the file without saving the image manually, your bake is lost.
✕ Wrong Color Space
Normal maps must use "Non-Color" color space. Using "sRGB" distorts the normal data and produces incorrect lighting.

Bake Type Summary

Bake Type What It Captures Color Space Common Use
Diffuse Base color only sRGB Game textures
Normal Surface angles (RGB) Non-Color Hi-to-low detail
AO Ambient occlusion Non-Color Depth/realism
Roughness Glossiness variation Non-Color PBR workflows
Combined Full lighting + color sRGB Archviz, film
Emission Emissive surfaces sRGB Glow effects

Question 1 of 5

What is the primary purpose of texture baking?

Question 2 of 5

Which render engine is required for baking textures in Blender?

Question 3 of 5

When baking a normal map, what color space should the resulting Image Texture node use?

Question 4 of 5

You see pink/magenta patches on your baked normal map when transferring from a high-poly to a low-poly mesh. What is the most likely cause?

Question 5 of 5

Before clicking "Bake", which element must be selected in the Shader Editor for Blender to know where to write the baked result?