Using Alembic in Blender: Importing and Exporting Animated Scenes

What you’ll learn in this guide

Alembic is an open graphics interchange framework for moving the evaluated geometric results of complex animations and simulations between applications. The key distinction in the Blender manual is that a file can store animated vertex positions and object transforms, but it does not recreate the rig or procedural network that produced them. Alembic should therefore be treated as a cache for transferring evaluated motion to another stage of a workflow, not as a backup of an editable character rig or simulation setup.

This guide covers how to define the export scope, set the time range and sampling, choose geometry data, and review the options when importing the file back into Blender. It is based on the Alembic documentation in the current Blender manual; as the manual does not specify a particular Blender version number, no version requirement is given here.

Requirements

• Blender and an Alembic file. The Blender manual describes both import and export options.

• A scene or objects to transfer in the Blender project. On export, you can choose selected objects only or all objects in the scene.

• The manual does not specify any particular system requirements. Separately check whether the other application used by your team can read the Alembic file; some options may need to be adjusted for compatibility.

Exporting Alembic: step by step

1. Define the export scope. Use “Selection Only” if you need to send specific objects; when it is disabled, all objects are exported. This helps prevent unnecessary objects from ending up in the receiving scene. If parent-child relationships need to be preserved, plan the hierarchy setting from the outset.

2. Review the scale and frame range. “Scale” sets the overall scale of the file. To use Blender units, the manual recommends keeping the default value of 1.0. “Frame Start” and “End” define the range to export; the start value is the current scene range. Make sure it covers the required portion of the motion.

3. Set motion sampling. “Transform Samples” sets how many times animated transforms are sampled per frame; “Geometry Samples” sets the equivalent sampling for animated geometry. “Shutter Open” and “Close” define the time interval in which samples are taken. The valid range is -1 to 1: -1 indicates the previous frame, 0 the current frame, and 1 the next frame. For motion blur, the manual gives five samples with a range of -0.25 to 0.25 as an example; this is a sample setting, not a requirement.

4. Choose hierarchy and object settings. With “Flatten Hierarchy” disabled, parent-child relationships are exported. When enabled, those relationships are not carried over, and transforms are written in world space. Choose the setting based on the structure expected by the application that will open the file. “Use Instancing” exports duplicated or instanced objects as Alembic instances; according to the manual, this can speed up export, but it can be disabled for compatibility with other software.

5. Check geometry data. Options for exporting UV coordinates, normals, and color attributes can be enabled as needed. “Face Sets” carries per-face material names, not the material data itself. The “Apply” sub-surface subdivision modifier applies modifiers before writing the file; “Use Schema” writes the mesh using the SubD Alembic schema instead of PolyMesh. “Triangulate” converts the mesh into triangles. Match these options to the geometry and appearance required at the other end of the transfer.

6. Test the result. Keep the source Blender scene and check the exported file in the target application. Pay particular attention to scale, the start and end of the motion, surface normals, and hierarchy. Alembic carries evaluated results; the source rig or procedural setup is not included in the file.

Importing Alembic into Blender

1. Check the file and scale requirements. “Scale” enlarges or reduces objects relative to the world origin. Don’t assume the file uses the same scale as the scene; compare the imported geometry with known dimensions in the scene.

2. Review the time range option. If “Set Frame Range” is enabled, Blender updates the scene’s start and end frames based on the values in the Alembic archive. Consider the effect of this option if you need to preserve the current scene range. If the file is a sequence split into separate parts, use “Is Sequence” to indicate this.

3. Consider mesh validation. “Validate Meshes” checks the imported mesh data and fixes faulty data if necessary. The manual notes that this option can slow down importing, but data errors are not always obvious, and recommends using it. With a file that may contain errors, keep in mind that skipping validation could cause problems during viewing or editing.

4. Understand cache behavior. Meshes that change over time automatically receive Mesh Sequence Cache modifiers; objects whose transforms change receive Transform Cache Constraints. If “Always Add Cache Reader” is enabled, cache readers are added to objects even if they are not animated, allowing them to update when the Alembic archive is reloaded.

Use in architecture, interiors, and archviz workflows

In architectural animation, transferring the evaluated state of a moving object or geometry deformed by a simulation to a separate scene can help separate animation production from material and lighting work. For example, an Alembic file prepared in one application can be imported into Blender for shading and lighting; a file exported from Blender can also be rendered in another application. This hybrid workflow is possible because the file format carries application-independent evaluated geometry.

The trade-off is that the editable source setup is not included in the file. If the rig, simulation network, or procedural steps need to be continued in another application, Alembic alone won’t provide them. Teams should also test whether the target application reads sampling, hierarchy, normals, and color data as expected. The manual does not specify particular hardware, fees, or licensing conditions, so the choice should be based on the existing software pipeline and delivery requirements.

Common mistakes

• Assuming the source rig will be transferred too: Alembic focuses on evaluated geometry and transform results; it does not store the procedural network.

• Exporting the entire scene: If “Selection Only” is disabled, the export is not limited to selected objects.

• Not checking sampling: Transform and geometry samples are separate settings; consider the needs of animated geometry separately.

• Assuming all surface data is included: Face Sets transfers material names, not material data. Check the UV, normal, and color options separately.

• Confusing time with frame numbers: Alembic uses time samples; when converting frame numbers to seconds, Blender uses the current scene’s frame rate. Test time behavior before and after transfer.

Next steps

Start by testing an import and export on a small section of a scene. Use a single animated mesh and an object with changing transforms to check cache behavior, frame range, and scale. Then verify the geometry options and hierarchy settings required for the actual delivery with the target application. If the appearance differs, check separately which normals, UVs, color attributes, and Face Sets data are present in the file.

Source and license

This guide is adapted from the Blender manual’s current Alembic import and export documentation. Source: Blender Manual, “Alembic” (K1). License: CC BY-SA 4.0. The content has been translated and adapted into Turkish.