In brief
- Alembic stores animated geometry and transform data; it does not transfer the production tree or rig structure.
- In Blender, an export scale of 1.0 preserves Blender units.
- For motion blur, you can set the sample count to 5, Shutter Open to -0.25, and Shutter Close to 0.25.
- On import, Validate Meshes checks for data errors; this can slow down the import.
Blender’s current online manual describes Alembic as a format for transferring animated geometry between applications. This guide walks through the key options for 3D artists and visualization teams who want to export animations created by simulation or intensive rig calculations and use them in another scene. Since the documentation does not specify a Blender version number, this article is based on the current Blender manual, with no version number specified.
What data does Alembic transfer—and what does it leave behind?
Alembic stores the calculated geometric results of a complex scene over time. For example, animated mesh positions and object transforms can be written to a file. However, the rig, dependency graph, or working setup of the simulation tools that created the animation is not preserved. In other words, Alembic transfers the calculated result, not the source production process.
This distinction matters when planning a workflow: the receiving application may be able to shade and light the geometry, but the Alembic file does not contain the structure needed to edit the animation’s rig in the same way. Blender’s manual says that Alembic files from other software can be used in Blender, and that animations created in Blender can also be transferred to other applications.
1. Choose the objects and time range before exporting
If Selection Only is enabled in the export settings, only selected objects are written; if it is disabled, all objects are exported. Sending only the required character, furniture, or part of a scene helps control the scope of the file. The manual does not specify the full menu path to the export panel, so no interface path should be assumed here.
Frame Start and End define the frame range to export. According to the documentation, the default range is the current scene’s frame range. If only a specific section needs to be delivered, check that the export range matches the scene.
The manual’s recommendation for scale is straightforward: leave the export scale at 1.0 to preserve Blender units. Choosing a different scale can affect size matching between applications, so compatibility with the receiving scene should be tested separately.
2. Set sampling for moving geometry
Alembic export lets you define transform and geometry samples separately. Transform Samples sets how many times per frame animated transforms such as position, rotation, and scale are sampled; Geometry Samples sets the sample count for animated geometry. Subframe sampling can be used when more detailed motion information is needed.
The manual also provides a sample setting for motion blur: set the sample count to 5, Shutter Open to -0.25, and Shutter Close to 0.25. Valid shutter values range from -1 to 1; -1 represents the previous frame, 0 the current frame, and 1 the next frame. In this example, samples are taken both before and after the current frame. If more samples are needed, file size and transfer time should also be considered in the team’s workflow; the source documentation does not specify the exact performance cost of these settings.
| Setting | Recommended value | Effect |
|---|---|---|
| Export scale | 1.0 | Preserves Blender units. |
| Sample count | 5 | The example value given in the documentation for motion blur. |
| Shutter Open | -0.25 | Extends the sampling interval before the current frame. |
| Shutter Close | 0.25 | Extends the sampling interval after the current frame. |
3. Review geometry, UVs, and object relationships
When UV Coordinates is enabled, UV maps are exported. Although the Alembic standard supports a single UV map, Blender exports all UV maps so that other software can read them. Merge UVs can merge UVs that share the same vertex and position; according to the documentation, this can reduce file size slightly.
The Normals option exports normals, while Color Attributes exports color attributes. Face Sets transfers material names per face; it does not export the material data itself. So don’t assume the file will arrive with its materials ready to use. The Subdivisions option applies Subdivision Surface modifiers before writing the file, while Triangulate splits the mesh into triangles. Before using these options, consider the receiving application’s requirements and whether further editing will be needed.
If you need to preserve the object hierarchy, leave Flatten Hierarchy disabled; this transfers parent-child relationships. When enabled, relationships are not exported and transforms are written in world space. Use Instancing exports duplicate or instanced objects as Alembic instances. Blender’s manual says this can speed up export, but the option can be disabled when compatibility with other software is required.
4. Import the file and check the data
Mesh Sequence Cache modifiers are automatically added to imported meshes that change over time. Transform Cache Constraints are used for animated object transforms. If Set Frame Range is enabled, the scene’s start and end frames are updated to match the range in the Alembic archive. If the file is a sequence split into separate parts, enable Is Sequence accordingly.
Validate Meshes checks imported meshes for corrupt data and fixes it if necessary. This option can slow down the import; however, the documentation notes that data errors are not always immediately apparent and recommends running the check. With the option disabled, faulty data can cause crashes when viewing or editing meshes.
Implications for architecture and archviz workflows
Alembic is useful for teams that need to hand off animated geometry produced by simulation or intensive calculations between scenes and applications. In architectural animation, delivering the calculated result of moving objects can remove the need to share the source rig or procedural setup as well; however, that does not mean the source structures will be editable in the receiving application.
Before delivery, offices should check scale, frame range, UVs, normals, and hierarchy. Confirm that the other software in use is compatible with the sampling, UV, and geometry options; in particular, test Use Instancing when compatibility is required. Since Blender’s manual does not provide information about licensing, hardware requirements, or compatibility between specific versions, these points should be verified separately against the applications and team requirements in use.
Common mistakes
Assuming the Alembic file will also include the animation rig and dependency graph.
Setting a scale other than 1.0 when Blender units need to be preserved.
Interpreting
Face Setsas meaning that material data will also be transferred.Overlooking the
Is Sequenceoption when importing sequence files.Failing to account for the fact that
Validate Meshescan increase import time.
Transforming objects before export
If you need to change an object’s type before exporting Alembic, you can use the conversion paths given in the manual. To convert a selected mesh or text object to a curve, use Object › Convert › Curve in Object Mode. For mesh objects, only loose edges not connected to faces are included in the conversion; text objects become curve outlines that retain their shape. The result is a Poly Curve by default; for smooth segments, you can choose Bézier Curve using Set Spline Type.
To convert a curve, metaball, surface, or text object to a mesh, use Object › Convert › Mesh. The operation uses the objects’ defined resolution and preserves faces and volumes created by closed or extruded curves. The Keep Original option in the Grease Pencil conversion creates a copy before converting during this specific operation; it should not be treated as an option available for general object conversions.
Sources
2 sourcesSource texts are not republished; short quotes are marked, everything else is our own summary and commentary.
For architecture and visualization offices in Turkey, Alembic’s practical value lies in being able to move animated geometry from the scene where it was calculated into another application. This can simplify workflows, especially when handing off heavy simulations or rig results, but it’s important to remember that the source setup does not travel with the file.
The best approach is to test scale, sampling, and compatibility with the target software using a small section of the scene first. The impact of higher sample counts and mesh validation should be assessed for each file and workflow; the documentation does not specify hardware or licensing costs. Adding UV, normal, and material expectations to delivery notes can also help reduce visual differences.
Frequently asked questions
Does an Alembic file also transfer the rig from Blender?
No. Alembic stores calculated animated geometry and transforms; it does not transfer the rig or dependency graph that created them.
What should the Alembic export scale be in Blender?
The manual recommends leaving the scale at 1.0 to use Blender units.
Should mesh validation be enabled when importing Alembic into Blender?
Validate Meshes checks for corrupt data and fixes it if necessary, and the manual recommends using it. It can increase import time.



