How to Export Blender Geometry Nodes Simulations to Alembic

What you’ll learn in this guide

This guide covers how to manage the cache of a Blender Geometry Nodes simulation, bake the result to disk, and export animated geometry to an Alembic file. The goal is not just to inspect a simulation running in the scene, but to prepare its results for use in another application or a rendering workflow.

Blender’s Simulation Zone structure allows the result of one frame to affect subsequent frames, making it possible to create simulations that evolve over time. Alembic, in turn, is designed to store calculated geometry and animated transforms in an application-independent format. It helps to treat these as two separate steps: first prepare the simulation result in Blender, then write the required animation data to Alembic.

Requirements and scope

You’ll need Blender and a scene containing a Geometry Nodes simulation. The source guides do not specify a particular Blender version, so no version requirement is listed here. The sources also do not define any account or subscription requirements.

Save the blend file to your computer before baking to disk. According to the Blender manual, the location where bake data is stored depends on the location of the blend file. A simulation cache makes it easier to jump between frames and inspect the result; don’t confuse this cache with persistent export data.

Alembic does not carry a complex node network or dependency graph. It stores calculated geometry, animated vertices, and object transforms. So, in the receiving application, the goal is to use the precomputed result—not edit the simulation’s node logic.

Prepare the simulation step by step

1. Run the Geometry Nodes simulation. The Simulation Zone in your scene is used to pass results between frames. Blender caches the simulation automatically during playback. The strong purple line in the Timeline Editor helps you identify cached frames.

2. Review the relevant frames. After playback, go to earlier frames and check that the simulation progresses as expected. According to the source guide, the cache lets animators review previous frames quickly. If only the current frame matters, caching can be disabled to conserve memory; consider whether that option suits your need to review the full simulation.

3. Save the blend file. Make sure the file is saved on your computer before baking. Since the location for bake data depends on the blend file’s location, don’t rely on a bake performed before saving the project file.

4. Bake the simulation to disk. The Bake operation in the Geometry Nodes simulation and physics interface bakes simulations in the modifiers of selected objects. Keep in mind that this may include all simulations on the selected objects. Calculate to Frame calculates from the beginning up to the current frame, while Delete Cached Simulation deletes baked simulations.

5. Adjust the cache location if needed. The simulation guide says that the directory for bake data can be changed for each modifier under Internal Dependencies. When working with multiple modifiers or objects, keep track of which data is written to which location.

6. Review the Alembic export options. By default, the start and end frames for export use the scene’s current frame range. If you only need to transfer specific objects, consider the Selection Only option; when enabled, only selected objects are exported. Global Scale can be left at 1.0 to use Blender units.

7. Set geometry and time sampling. Transform Samples controls the number of transform samples per frame, while Geometry Samples controls the number of samples for animated geometry. Shutter Open and Shutter Close define the time interval over which these samples are taken; the valid range is -1 to 1. For more detailed mesh motion blur data, the guide describes an example using 5 samples and shutter values of -0.25 and 0.25. Choose these settings based on the needs of your intended output.

8. Include the required geometry data. With UV Coordinates enabled, UV maps are exported. The Normals and Color Attributes options export the corresponding data. Face Sets carries material names per face, not the material data itself. The Subdivisions setting can apply Subdivision Surface modifiers before export. Select the data the target application actually needs to keep the transfer focused.

9. Prepare to use the file in another application. When Blender imports Alembic files, it adds Mesh Sequence Cache modifiers to meshes that change over time and Transform Cache Constraints to animated location, rotation, or scale transforms. During import, Validate Meshes checks for and attempts to fix invalid data. This option can slow down the import, but data errors may not always be obvious.

Using this in architecture and visualization workflows

This workflow is useful for architecture firms and visualization teams that want to move animated geometry created with Geometry Nodes into another DCC application, or into a lighting or rendering stage. The Blender manual says that Alembic files created in other applications can be imported into Blender, and that animations created in Blender can also be transferred to other software via Alembic.

However, the transfer carries the calculated result, not the editable procedural system. Teams that want to continue working on the node network in the receiving application should keep in mind that Alembic is not designed for that purpose. Before exporting, also check where the bake data is stored, which objects are selected, the frame range, and options such as UVs and normals. The sources provide no specific hardware requirements or licensing costs, so it isn’t possible to make a definitive recommendation on those points.

Common mistakes

• Starting a bake before saving the blend file: The blend file must be saved on your computer to bake to disk. Save the project file first.

• Assuming the bake scope is limited: Baking can process all simulations in the modifiers of selected objects. Check the selection and scene scope before starting.

• Treating Alembic as a backup of the node network: Alembic stores calculated geometry and animation results; it does not store the procedural dependency graph.

• Assuming materials will transfer completely: Face Sets exports material names, not material data. Plan the material setup in the target application separately.

• Ignoring time sampling: Alembic works with time samples and has no frame-rate concept in the file format. Blender uses the current scene frame rate to convert frames to seconds; check how other applications interpret this data.

Next steps

For your first transfer, use a small scene that’s easy to check. Export only the objects you need, and review the frame range and UV and normal options based on the target application’s requirements. After importing the file, inspect the animation timing and geometry. If the import is slow, assess the effect of the Validate Meshes option—but remember that data errors may not be visible.

Sources and license

This guide has been adapted into Turkish using the Simulation Nodes, Convert, and Alembic pages in the Blender Manual. All three pages are licensed under CC BY-SA 4.0. The content has been adapted under the terms of this license.