Cycles Texture Cache in Blender 5.2: Render Texture-Heavy Scenes Without Running Out of Memory
If your Cycles render dies from lack of memory, it's rarely the polygons: it's the textures. Blender 5.2 adds the Cycles Texture Cache, which loads only the tiles and resolutions a render needs and frees up VRAM. Here's what it does, how to enable it in three clicks, and when it's worth it.
Why a Render Runs Out of Memory (and It's Rarely Geometry)
It's a memorable error: the scene opens fine, the materials already show in the viewport, you hit render, and a few seconds later the out-of-memory warning appears. The first suspect is usually the mesh, but most of the time the culprit is something else.
What Cycles Keeps in Memory While It Renders
To compute the color of a point the camera sees, Cycles needs the color value of every texture involved, pixel by pixel. Knowing the material exists isn't enough: the engine has to have the image within reach. If a scene drags along dozens of 4K images, they all ask for their space at once even if the camera is looking at one wall.
VRAM, RAM and "Out of Memory": Three Places Where It Breaks
Where the limit shows up depends on how you render. With a GPU, the ceiling is the card's VRAM; on the CPU, it's system memory. On machines with 8 or 12 GB of VRAM the problem hits sooner, but it isn't limited to modest cards: an interior scene with many materials weighs the same for everyone.
Read also
The Classic Case: 60 PBR Materials at 4K in One Interior
Picture an archviz living room with sixty different PBR materials, each with its color map, roughness and normal. The camera shows one corner, but the engine must be able to serve any texture that enters the frame. That's where a perfectly modeled scene runs out of air.
What a Texture Cache Is, Without the Jargon
The idea is old and simple: instead of uploading the whole image, upload only what will be looked at, at the resolution it will be looked at. Blender 5.2's Cycles Texture Cache does exactly that.
From the Whole Image to Tiles: Loading Only What's Seen
The engine splits each image into equal chunks, the tiles, and works out which ones fall inside the frame. It loads nothing from the rest. It's the same trick games already use so that giant textures don't swamp the card's memory.
Detail Levels (Mipmaps): the Texture at the Resolution It Occupies on Screen
An object that looks small doesn't need a 4K texture. The cache stores the same image at several resolutions and serves the one that matches its on-screen size. A homely way to picture it: taking only today's recipe page into the kitchen instead of the whole book.
The Same Problem Game and Production Engines Already Solved
This kind of cache isn't a Blender invention: production renderers and real-time engines have worked with texture streaming and detail levels for years. The news is having it built into Cycles, with nothing external to configure.
What Blender 5.2 Actually Brings
Blender 5.2 LTS was released on July 14, 2026, with the current version at 5.2.2 (September 15, 2026) and support running until July 2028. Within that branch, the project's documentation flags the Texture Cache as one of the most important performance changes.
The Cycles Texture Cache: Less Memory and Faster Startup
The release notes are blunt: on scenes with many textures, the cache significantly reduces memory usage and startup time. That's not a marginal optimization: it's the difference between a scene that fits and one that doesn't.
What You Pay: Disk Space and a Small Rendering Cost
It isn't free. The documentation itself warns of two trade-offs: the cache uses more disk space and adds a small rendering performance impact. Manage the expectation: the message isn't that renders get faster, but that they become more manageable in memory.
The Startup-Time Fix in the 5.2.x Releases
The feature shipped with a known annoyance: with many tiles, initialization could take too long. The 5.2.x maintenance notes already carry the fix (including a minimum 64x64 tile size for texture cache loading). If you noticed it in early versions, updating within the same 5.2 solves it.
How to Enable It, Step by Step
Step 1: Keep Textures as Files (Unpack Them If They Came Inside the .blend)
The cache needs to write a file next to each image, so images packed inside the .blend won't work. If your project comes from a downloaded pack or an archive that stores them internally, use File → External Data → Unpack Resources. Otherwise Blender warns that it can't find image files to generate the .tx files.
Step 2: Render, Performance and the Texture Cache Section
With textures unpacked, open the properties editor, Render tab, and expand the Performance panel. In Blender 5.2 there's a new Texture Cache section there, with an Auto Generate option and a Generate button.
Step 3: Auto Generate or Generate: When to Use Each
Auto Generate lets Blender build the optimized versions during rendering, with no intervention. Generate builds them by hand, whenever you decide. The practical rule: if the project is still changing a lot, generate manually once it's stable so you don't rebuild the cache on every test; if it's locked down, turn on Auto Generate and forget about it.
Step 4: Where the Files Go and How Much Space They Take
For every image, an equivalent .tx file is created in a blender_tx folder next to the original image; there's no single central cache folder. Two consequences: the space spreads out wherever your textures live, and it's worth checking the total before backing up or moving the project to a drive that could fill up.
Step 5: Render With the Cache Already Built
Ideally you reach the render with the .tx files already written, especially on animations, so they aren't rebuilt on every frame. The cache also regenerates itself when the source image changes, so you don't have to delete .tx files by hand each time you edit a texture. For batches, the 5.2 branch lets you generate the .tx files for a whole file from the command line with the maketx command, which is handy in a render pipeline.
When It's Worth It (and When It Isn't)
Scenes That Benefit: Interiors, Archviz, Prop Packs
If your scene has many high-resolution materials —interiors, furniture, product visualization, prop packs— the cache is the difference between rendering and dying trying. That's the scenario it was designed for.
Scenes Where You Won't Notice
With few or small textures, the memory saving is minimal and you'll only pay the disk cost. If your scene is stylized or low poly, enabling the cache won't change your day.
What's Still Essential: Lower Resolutions and Simplify
The cache helps; it doesn't fix a badly built scene. It's still wise not to use 8K where something is seen a couple of millimeters wide, and to lean on Simplify → Texture Resolution, which scales images down to reduce memory. It's the natural companion to the cache.
Estimating Memory Before You Load Anything
Before loading anything, it pays to have a rough idea of the weight. A 4096 x 4096 texture takes, uncompressed, around 67 megapixels of data per channel; multiplied across dozens of materials, the count climbs fast. To do that math without opening Blender, the blog has a resolution-to-total-pixels converter built for exactly this.
Common Mistakes and Questions
"I Turned It On and Nothing Changed"
The bottleneck probably wasn't textures. If the scene has too much geometry, high subdivision levels or a simulation eating all the memory, the cache doesn't touch that problem.
"The Cache Takes More Disk Than the Project"
That's the documented trade-off: the .tx files add up. Measure the folder before archiving the project and factor it into your backup plans.
"Does It Work in EEVEE?"
No. The Texture Cache is a Cycles feature; EEVEE and Workbench don't use it. Nor does it make a render free: the gain is in memory and startup.
The Right Order: Fix the Scene First, Cache Later
Fix resolutions and materials first, then enable the cache. Done the other way around, you build a large cache for a scene you were going to optimize anyway.
Conclusion: For Whom It's a Game Changer, and For Whom It Isn't
If you render interior scenes with many textures on a machine with 8 or 12 GB of VRAM, the Cycles Texture Cache is night and day. If your scenes are light, it's a marginal improvement that will only cost you disk. You can see the workflow in motion in the Cycles cinematography guide and the Mantaflow fluid simulation tutorial, and keep going with more tutorials in the 3D Design section.
