Skip to content
blendshelf

Blender texture baking: a checklist for a usable image

Last reviewed 20 October 2026

To bake a texture image in Cycles, give the destination mesh UVs and an image, make that image’s node the active bake target, choose the pass you need, then bake and save the result. Test one map on a copy before processing an entire asset.

Baking writes information into an image; it does not automatically transfer every Blender shader feature to another application. Define the destination’s expected map type, normal convention and colour handling before building a large texture set.

1. Define the map you need

Write down whether you need base colour, roughness, surface normals, ambient occlusion or a lit result. These are different outputs. For example, a colour-only diffuse bake should exclude the Direct and Indirect lighting contributions; Combined is not a substitute for an unlit base-colour image. Start with a simple material you understand so you can judge whether the selected pass contains the intended information.

2. Prepare a distinct target image

Use Cycles and check the destination mesh’s UV layout. Create a new output image with the intended dimensions. Add or choose an Image Texture node containing that image in each destination material, and make it the active selected image node. Keep the source textures and output image distinct so you can identify what was read and what was written. The node selected for baking and the image displayed in an editor can be different.

3. Choose same-object or high-to-low baking

A material-to-image bake on one mesh does not require the same selection workflow as transferring detail between meshes. For Selected to Active, select the source objects and make the destination mesh active. Check ray distance or a suitable cage on a small test: too little coverage misses detail, while excessive reach can capture another surface. A manually supplied cage needs matching topology with the destination as described in the manual.

4. Bake one map and inspect its edges

Check the Bake type, contribution switches, target and Clear Image option before running the test. Clearing an image can remove earlier content, so preserve an image you need to keep. Inspect the output in the Image Editor, then connect it in a test material. Add enough UV-island spacing and bake margin for the intended resolution and filtering; inspect seams at a distance as well as close up.

5. Check normal maps in the destination

Choose a normal space that matches the intended use. Tangent-space maps are commonly used for deforming assets, while object-space maps encode a different reference. Confirm the destination’s channel convention and normal-map interpretation instead of treating the image as ordinary display colour. Test lighting across curved surfaces and UV seams before generating a full batch.

6. Save and inventory the outputs

Save the baked image explicitly and save the project separately. Reopen a copy and verify the disk files in the application that will consume them. Use the texture calculator for mixed-resolution maps and higher-precision data images; count each unique tile once. Keep a small record of mesh version, pass and image names so you can reproduce the bake when the asset changes.

Questions before choosing

Why did only part of the mesh receive a bake?

Check each destination material’s active image node and the mesh UVs. For high-to-low baking, also inspect source selection, the active destination and ray or cage coverage.

Is baking the same as painting a captured view in Krita?

No. A view-projection bridge transfers edited view imagery; a bake writes a selected material or surface pass into the target’s UV image. Choose the process for the output you need.

Further reading