Calculate enabled graph outputs with the WonderTexture Engine and create or update packed Blender images for materials and other Blender workflows.
Bake to Blender calculates the active graph’s enabled Outputs and creates or updates their Blender images. Use it when a procedural result needs to become persistent Blender image data for materials or other Blender image workflows.
The graph remains procedural; baking takes the current state of selected Outputs and turns it into a Blender-owned snapshot.
Before baking, confirm that the WonderTexture Engine is running and connected, the active Standard Graph has Output nodes, at least one Output is enabled for Bake/Export, enabled Outputs have valid upstream texture results, and resolution and Color Space are configured as intended.
Open N-panel → WonderTexture and click Bake to Blender. WonderTexture gathers the enabled Outputs and asks the native engine to calculate those targets at the graph’s resolved production dimensions.
If the graph resolves to 2048 × 2048, the baked result uses that target size. Configure Resolution & Precision intentionally before production baking rather than relying only on how a small interactive preview looks.
For each successful result, WonderTexture finds or creates the corresponding Blender image. If that image already exists, new pixels are loaded into the same datablock; otherwise a new image is created. The Output’s configured Color Space is then applied and the image is packed into the Blender project.
Existing Blender materials that already reference a WonderTexture image can therefore see updated pixels after a re-bake without rebuilding the shader simply because the image contents changed.
Auto-Bake is a graph-specific option that keeps affected Blender images up to date as graph processing produces newer results. For a new setup, first configure Outputs, run Bake to Blender once, create or update the Blender material if needed, and then enable Auto-Bake.
Auto-Bake respects Include in Bake/Export and uses WonderTexture’s incremental graph updates, so only affected enabled Output branches need to be refreshed. If an Output is disabled, its existing Blender image is kept at the last baked version instead of being deleted.
Auto-Bake updates image pixels, not material structure. If you add a new Output such as Roughness or Height, run Create / Update Material so the shader gets the new connection. External files are still written only through Export Files.
Bake Settings decides which destinations WonderTexture requests; it cannot guarantee that every requested Output has usable upstream data. An enabled but unconnected Output may produce no image.
If fewer images are generated than expected, inspect the Output’s Image connection, its upstream previews, runtime status, and whether the branch produces valid texture data.
For a clean first material setup, a practical order is Configure Outputs → Bake to Blender → Create / Update Material. Material structure and baked image availability can be repaired independently later.
With Auto-Bake off, Bake to Blender acts as an explicit checkpoint: you can edit and preview repeatedly while Blender keeps the last baked images, then bake when you want production data updated.
Use Export Files when results need to become PNG, TIFF, TGA, JPEG, or OpenEXR files on disk.
WonderTexture also uses the word “bake” for Graph Baking, which packages procedural graph logic as a reusable asset. That is a separate workflow from producing texture images.
