01 / 21

Baking
Simulations

Learn how to bake simulations and manage cache files in Blender for efficient, reproducible physics workflows.

Blender

What Is Simulation Baking?

In Blender, baking a simulation means pre-calculating every frame of a physics simulation and storing the results to disk. Instead of re-computing cloth, fluid, or particle behaviour in real time, Blender reads the pre-computed data, giving you consistent, frame-accurate playback every time.

Why Baking Matters

✓ Consistency
Every playback and render produces the exact same result: no random-seed surprises.
✓ Performance
Baked frames play back instantly. No waiting for the solver to catch up on each frame.
✓ Render Farms
Render farms need baked caches to render frames out of order without dependency errors.

The Simulation Cache

Every physics system in Blender writes to a cache: a folder of per-frame data files. There are two types of cache states you will encounter:

Dynamic Cache
Temporary, auto-generated as you play the timeline. Lost when you scrub backwards or change settings. Stored in memory or temp folder.
Baked Cache
Permanent, written to disk via Bake button. Survives scrubbing, scene changes, and file saves. Required for final renders.

The Baking Pipeline

1. Configure Physics settings 2. Bake Pre-compute all frames 3. Cache Files Stored on disk 4. Render Read cached data Free Bake (clears cache) Modify settings → re-bake

Bake vs Free Bake

Bake Free Bake
Action Pre-computes all frames to disk Deletes cached frames from disk
When to use Settings are finalised Need to change physics parameters
Timeline scrub Instant, any direction Must re-play from frame 1
Render safety Safe for render farms Not safe: frames may differ

Cache File Types

Different simulation systems produce different cache file formats. Understanding these helps you manage disk space and troubleshoot missing simulations:

Cloth / Soft Body
Point cache format (.bphys files). Relatively small: stores vertex positions per frame.
Rigid Body
Point cache format. Stores object transforms (location, rotation) per frame. Very lightweight.
Fluid (Mantaflow)
OpenVDB (.vdb) files. Very large: stores full 3D voxel grids for density, velocity, and more.

Estimating Cache Size

Cache file size depends on the simulation resolution and frame count. For fluid simulations, voxel resolution is the main driver:

Where Caches Live

project_folder/ scene.blend cache/ cloth_cache_*.bphys fluid_*.vdb Set cache path relative to .blend for portability

How to Bake a Simulation

1
Select the object with the physics modifier (cloth, fluid domain, soft body, etc.).
2
Open the Physics panel in the Properties editor. Scroll to the Cache section.
3
Set the frame range: Start Frame, End Frame, and optionally the cache directory path.
4
Click "Bake" (or "Bake All Dynamics" from the top menu for multiple objects).
5
Wait for computation. The progress bar shows frame-by-frame progress. Do not interrupt.
6
Save the .blend file. The cache references are stored with the file. Without saving, paths may be lost.

Example: Cloth Bake

Cloth Cache Settings Start Frame 1 End Frame 250 Cache Directory //cache/cloth/ Bake Free Bake 70%

Example: Fluid Domain Bake

Fluid simulations are the most resource-intensive bake type in Blender. A Mantaflow domain at resolution 256 generates OpenVDB files that can be 50-100 MB each.

1
Select the domain object (the box that contains the fluid).
2
In Physics > Fluid, set Type: Domain and Domain Type: Liquid.
3
Set Resolution Divisions (start low: 64, increase to 128 or 256 for final).
4
Under Cache, set the path and click "Bake Data", then "Bake Mesh" for the surface.

Example: Bake All Dynamics

When your scene has multiple physics objects (cloth, rigid bodies, particles), you can bake everything at once:

Cloth Rigid Body Particles Bake All Dynamics ✓ All caches written to disk

Managing Cache Files

1
Name your caches clearly: Use descriptive folder names like //cache/cloth_curtain/ instead of defaults.
2
Use relative paths: Start paths with // so they resolve relative to the .blend file location.
3
Version your bakes: Before changing settings, duplicate the cache folder (e.g., cloth_v1, cloth_v2) so you can revert.
4
Clean up unused caches: Old bakes can consume gigabytes. Delete cache folders for discarded simulations.
5
Check disk space before baking: A high-res fluid sim at 300 frames can need 30+ GB of free space.

Common Mistakes

✕ Forgetting to bake
Sending a scene to render without baking means frames compute sequentially, wasting hours and risking inconsistent results.
✕ Editing after bake
Changing physics settings while a bake exists has no effect. You must Free Bake first, adjust, then re-bake.
✕ Absolute cache paths
Using absolute paths (e.g., C:\Users\...) makes the project break when moved to another computer or render farm.

Simulation Baking Summary

Simulation Type Cache Format Typical Size Bake Button
Cloth .bphys Small (MB) Physics > Cache > Bake
Soft Body .bphys Small (MB) Physics > Cache > Bake
Rigid Body .bphys Tiny (KB) Scene > Rigid Body > Bake
Particles .bphys Medium (MB) Physics > Cache > Bake
Fluid (Mantaflow) .vdb Large (GB) Physics > Bake Data + Mesh

Question 1 of 5

What does "baking" a simulation mean in Blender?

Question 2 of 5

You want to change the stiffness of a cloth simulation that is already baked. What must you do first?

Question 3 of 5

Which Blender simulation type typically produces the largest cache files?

Question 4 of 5

Why should you use relative paths (starting with //) for cache directories?

Question 5 of 5

A Mantaflow fluid domain has two separate bake operations. What are they?