For those who don’t know the topic: Blender is a DCC with the Cycles renderer. The new texture cache sits in Cycles rendering performance, alongside existing memory and render speed controls.

The problem it aims to fix

Texture-heavy scenes can burn memory fast, even before you hit your sample count. The new texture cache in Cycles targets that pressure by changing what gets loaded at render time, and how. The core idea: instead of pulling full image textures into memory, the system loads only the tiles and resolutions actually needed for the render. That means the renderer can avoid carrying the entire source image when the shot only uses a fraction of it, or when the texture resolves to a smaller mip level in-frame.

This is a straight-up memory efficiency play for scenes that rely on lots of image textures. Claims about the size of the improvement exist, but specific benchmark numbers and test conditions are very difficult, because it wholly depends on your scene – so test before using it in production!

.tx files, generated next to your textures

Cycles Texture Cache generates a matching .tx file for each image texture and places it in a blender_tx folder next to the source image. The .tx file stores the texture in a form optimized for tiled access and multi-resolution loading, so the renderer can pull only the tiles and mip levels it needs.

# Generate tx files for all images in a blend file.
blender scene.blend --command maketx
# Generate tx file for a specific image file.
blender --command maketx image.png --colorspace sRGB

The workflow aims to stay mostly invisible. The .tx files regenerate automatically when the source image changes. Cycles also infers settings such as color space and filtering based on how the image gets used in shader nodes, rather than forcing artists to maintain a parallel set of cache settings by hand. That last part matters for production sanity: texutre caching that requires constant babysitting tends to get switched off right before deadline.

CPU, GPU, and the day-to-day reality check

The feature is working across CPU rendering and all GPU backends. It is also already available in daily builds, with additional improvements planned for render farms and production pipeline use.

If you manage shared storage, you will care about where those .tx files live, who writes them, and when. The currently accessible details do not fully spell out a studio-grade policy story for cache location, locking, or multi-user coordination. Still, the direction is clear: get memory use under control without turning texture management into another job title.

Schedule, availability, and pricing

Blender 5.2 LTS is in alpha, with a full release expected in July. Pricing is the same as always for Blender – free and Open Source. Before you roll this into a show, test it on your own shots, your own storage, and your own farm tooling, because new caching systems love to surface edge cases at the worst possible time.

https://code.blender.org/2026/05/cycles-texture-cache/

https://developer.blender.org/docs/release_notes/5.2/

The post Blender 5.2 LTS targets texture-heavy renders first appeared on DIGITAL PRODUCTION and was written by Bela Beier.