Texture Baking in Blender Cycles: A Step-by-Step Guide

What will you learn in this guide?

Texture baking transfers specific information from Cycles materials or lighting to a texture or Color Attribute layer. It can be used to prepare base color and normal maps, save ambient occlusion (AO) or procedural textures as a starting point for further editing, and create light maps. It can also be useful for assets that will be taken into a game engine and for objects that appear repeatedly in a scene.

This guide covers how to prepare the target, which information each bake type captures, and how to plan a transfer from a high-detail model to a low-detail one. It draws on features described in Blender’s current Cycles documentation. Since no specific Blender version is given, the steps do not promise a version-specific interface.

Requirements and preparation

Before you begin, make sure the scene is set up to use Cycles. The object to be baked must be a mesh and have a UV map. You can use an image connected to the active Image Texture node or an active Color Attribute layer as the output target. If you choose an image target, check that the relevant image is assigned to the active Image Texture node in the material to be baked. Materials without an active target will not receive the bake result.

Cycles uses the scene’s render settings during baking, including sampling and ray bounce values. These settings therefore affect the quality of the bake. The selected bake type also determines which surface information is captured. Don’t assume that one setting will suit every use case.

1. Check the mesh and UVs

Make sure the object you want to bake is a mesh and has a UV map. If you’re baking to an image texture, check how the UV islands are laid out on the image and make sure they don’t overlap. The UV layout determines which parts of the image correspond to each region of the model’s surface.

If you’re using a Color Attribute target, make sure the target layer is active. The bake is written to the Color Attributes layer on the active mesh. Non-mesh objects don’t have Color Attributes, so this method isn’t available for them.

2. Set the bake target

To output to an image texture, activate the Image Texture node that will serve as the bake target in the relevant material. Check that the correct target image is selected for every material in the scene to reduce the risk of blank or incomplete results. For the Color Attribute method, make sure the correct target layer is active on the active mesh.

It’s also important to decide whether to clear or preserve the existing image before baking. If “Clear Image” is enabled, the image is cleared before the operation begins. Keep this in mind if you want to add to a previous output; if you need to preserve the existing content, check the option’s state.

3. Choose the right bake type

The bake type determines what data is transferred to the texture. The main options are:

• Combined: Combines materials, textures and lighting; specularity is not included. Some contributing passes can be adjusted separately.

• Ambient Occlusion: Bakes AO information defined in the World settings and ignores scene lights.

• Shadow: Bakes shadow and lighting information.

• Normal: Transfers surface normals to an RGB image. The selected normal space must match the material’s Normal Map setting.

• Diffuse, Glossy and Transmission: Capture the corresponding material passes. Selecting Color, Direct or Indirect contributions affects whether the output is in color or grayscale.

• Roughness, Emit, Environment and UV: Bake roughness, emission, the world environment or UV coordinate information, respectively.

For example, Combined may be suitable for consolidating a material’s basic appearance into a single map, while AO can be used to capture only the occlusion effect. These produce different outputs, so choose the bake type according to the intended use.

4. Transfer detail from high to low

Use the Selected to Active workflow to transfer surface information from a high-poly model to a lower-poly target. Select the low-poly object and the high-poly source object; the bake is performed on the active object. According to the guide, rays are sent from the low-poly object toward the high-poly object.

If the source model does not fit entirely inside the target, you may need to adjust the ray start using Max Ray Distance or, when using a cage, Cage Extrusion. For a more controlled transfer, you can use a Cage Object. A cage defines the area the rays will cover as an expanded version of the low-poly model. If you create a custom cage, it must have the same topology as the base mesh—that is, the same number and order of faces.

5. Check the normal space and margin

Normal maps can use Object or Tangent space. The guide describes Tangent space as a suitable default in most cases and notes that it can be used with animated objects. The important thing is to use the same space for baking and the material’s Normal Map setting; if they don’t match, the result may not look as expected.

When baking to an image, adding a margin around UV islands helps prevent interruptions at seams during texture filtering and mipmapping. The Extend method extends edge pixels outward; Adjacent Faces uses pixels from neighboring faces across the UV seam. The margin size is set in pixels. Choose a method and size by inspecting the model’s UV layout.

Common mistakes

The target node isn’t active: When baking to an image, the active and selected Image Texture node is used as the target. If a material doesn’t have one, no output is created for that material. Check each material before baking.

The UV map or target layer is missing: The mesh must have UVs. If you’re using a Color Attribute instead of an Image Texture target, make sure the correct layer and active mesh object are selected.

The normal spaces don’t match: If the bake setting differs from the material’s Normal Map setting, the normal map may not be interpreted correctly. Match the spaces on both sides.

The ray distance or cage isn’t suitable: In a Selected to Active transfer, the relationship between the target and source geometry affects the result. If you see issues around the edges, consider adjusting Max Ray Distance, Cage Extrusion or Cage Object. The guide also warns that hard splits can cause non-smooth normals at the edges.

Memory use is overlooked: Each object used as a source in baking has a fixed CPU memory overhead. Combining high-poly source objects may help reduce memory-related issues.

Next steps

For your first test, choose a small but representative object and check the target image, bake type and UV margin individually. Bake a single pass, such as AO or normals, and inspect whether the result contains the expected information; then try other types if needed. Render settings affect bake quality, so remember that sampling and ray bounce settings are also in effect when you evaluate the result.

In architecture, interiors and archviz workflows, baking can be used to prepare scene assets for different purposes by transferring material or lighting information to a texture. For models that will be reused or transferred to a lower-poly target, decide in advance which information needs to be preserved. This doesn’t mean the same approach is necessary in every render scene: if the final image requires live lighting interactions, carefully choose what information to bake. Target image resolution, UV layout, memory use and compatibility with the applications in use should also be evaluated in the production pipeline; the source guide does not specify an export format or list of compatible applications.

Source and license

This guide is adapted from Blender’s Cycles Render Baking documentation. The source documentation is published under the CC BY-SA 4.0 license; its content has been adapted and rewritten in Turkish.