Using PLY and Alembic in Blender: Import and Export Guide

What will you learn in this guide?

PLY and Alembic files are not interchangeable in Blender. PLY is used to transfer mesh geometry and, optionally, data such as UV coordinates, normals, and color attributes. Alembic is used to transfer the computed results of animated geometry and object transforms to another application. This guide explains when to use each format, how to choose transfer settings, and how to reduce common compatibility issues.

In architectural visualization, transferring a static model to another application is a different task from sharing the geometry of an animated scene. PLY is geared toward mesh transfer, while Alembic focuses on geometry and transforms that change over time. Before creating either file, check which data the target application can read.

Requirements and preparation

This guide draws on the PLY and Alembic pages in the current Blender Manual. Since the manual pages do not specify a particular Blender version, no version number is given here; check the relevant import and export options in your installed version of Blender. The sources do not mention any paid account requirements.

Before transferring, review the scene units, object selection, and the target application's axis convention. PLY import and export both include scale and forward/up axis options. Blender uses Y Forward and Z Up. Alembic export also lets you set the scale; the manual recommends using the default value of 1.0 to preserve Blender units.

Importing and exporting PLY files

1. Choose the file type and number of files to import. Blender's PLY importer accepts ASCII and binary PLY files, and you can select multiple files in one operation. Before adding a file to the scene, check its scale, the scene unit, and the forward/up axis conversion. If you are working across multiple applications, the axis setting matters for opening the model in the expected orientation.

2. Consider merging vertices and handling color data. The “Merge Vertices” option attempts to merge vertices at the same location, when possible. If the file contains vertex colors, specify the correct color space: the source documentation offers sRGB and Linear, and also provides a None option to skip importing color data. If you do not know which color space the source file uses, check the settings in the application that created it instead of guessing.

3. Choose what to include in the export. PLY export has an option to include only selected objects. Set the scale and axes according to the target application's requirements. ASCII is an option if the application receiving the file does not support the binary format.

4. Check geometry and appearance data. Export options include writing the active UV layer's coordinates, exporting normals, and saving vertex colors in the selected color space. Most applications can calculate their own normals, but exporting them may be important if they need to match normal map textures in Blender. The option to triangulate N-gons with four or more vertices affects the exported mesh; it does not change the mesh in the scene. “Apply Modifiers” exports the mesh resulting from evaluated modifiers.

Transferring animated geometry with Alembic

1. Decide when to use Alembic. Alembic does not store how a complex rig or simulation was set up; it records computed geometry and animated transforms. For example, you can calculate an animation in one application and transfer it to another for shading and lighting. The Blender Manual gives the example of opening Alembic files from Houdini or Maya in Blender.

2. Review the import validation options. Mesh Sequence Cache modifiers are added to meshes that change over time, while Transform Cache Constraints are added to animated location, rotation, or scale values. When “Set Frame Range” is enabled, the scene's start and end frames are updated to match the range in the Alembic archive. “Validate Meshes” checks for corrupt data and fixes it if necessary. This check can slow down importing, but the source manual recommends the option, noting that data errors are not always easy to spot.

3. Set the export range and sampling. The start and end frames define the range to export; by default, Blender uses the scene's current frame range. Transform Samples sets how many times per frame animated transforms are sampled, while Geometry Samples sets the sampling count for animated geometry. Shutter Open and Shutter Close define the time range in which samples are taken. For detailed mesh motion blur, the manual gives an example with 5 samples, an open value of -0.25, and a close value of 0.25.

4. Set hierarchy, UV, and geometry options. “Selection Only” exports selected objects only. With “Flatten Hierarchy” disabled, parent-child relationships are preserved; when enabled, they are not exported, and transforms are written in world coordinates. UV Maps, Normals, and Color Attributes are separate options. Although the Alembic standard supports only one UV map, Blender attempts to export all UV maps in a form other applications can read. “Use Instancing” can export duplicate or instanced objects as Alembic instances; this option can be disabled when compatibility with other applications is required.

Common mistakes

• Using the wrong axis or scale: If the model appears in the target application with the wrong orientation or size, check the axis and scale values in the PLY or Alembic transfer settings.

• Ignoring color space: Choosing sRGB or Linear for PLY vertex colors can affect the result. Verify the source file and how its color data was saved.

• Treating Alembic as an editable rig: Rather than carrying the dependency graph from the production process, this format stores computed results. Do not assume the source rig will be recreated in the transferred file.

• Confusing frame rate with time: Alembic does not have frames as such; it stores time samples. Blender uses the scene's frame rate to convert frame numbers to seconds. Check timing when moving files between applications.

• Delivering without testing compatibility options: Choose ASCII for PLY and instancing or hierarchy settings for Alembic according to the target application's support. Open and check the file in the receiving application before delivery.

Next steps for architecture and archviz workflows

For architecture and interior design teams sharing static models or mesh-based geometry, PLY's selection, scale, axis, UV, and color options are key. If animated geometry, simulation results, or moving object transforms need to be transferred between applications, Alembic is a more suitable format. For archviz teams, sampling, frame range, and target software compatibility are particularly important to check before delivery.

Start with a small test scene: for PLY, verify the mesh's orientation and colors; for Alembic, check the animation range, geometry, and transforms. The sources do not specify hardware requirements, license fees, or guaranteed compatibility with every version of target applications. For your final workflow, the team should therefore confirm that the file works correctly with the Blender version in use and the receiving software.

Sources and license

This guide is adapted into Turkish from the “Stanford PLY” and “Alembic” pages in the Blender Manual. Both sources are licensed under CC BY-SA 4.0.