How to Import and Export PLY and Alembic Files in Blender

What you’ll learn in this guide

You’ll learn how to use Blender’s PLY and Alembic import and export options to prepare models and animated scenes for other applications. For PLY, we’ll focus on file format, axes, scale, and color settings; for Alembic, we’ll cover frame range, animation sampling, geometry, and hierarchy options.

The two formats serve different purposes. PLY can be used to transfer geometry and selected mesh data. Alembic is an interchange format for saving baked animated geometry and object transformations so they can be read in another application. Alembic does not store the dependency graph of the rigs or procedural tools used to create the scene; it stores the results.

Requirements

• You’ll need Blender and the PLY or Alembic file you want to transfer.

• The Blender Manual explains these options, but the source does not specify a particular Blender version or hardware requirements.

• Make sure the other application that will use the file supports the format and the data you need. Binary PLY support can vary between applications.

Importing and exporting PLY files

1. Open the import operator. In Blender, go to File > Import/Export > Stanford (.ply). You can select an ASCII or binary PLY file, and you can also select multiple files at once.

2. Check the scale and axes. Scale determines the size of imported objects relative to the world origin. The Forward Axis and Up Axis options help match differences in forward and up directions between applications. Blender uses Y Forward and Z Up. If the other application uses a different axis convention, adjust the conversion options accordingly.

3. Check scene units and colors. Scene Unit can be used to apply the scene’s unit scale to imported data. If the PLY file contains vertex colors, choose their color space: the data may be saved as sRGB or Linear. Select None if you don’t want to import color data.

4. Choose what to export. If you enable Selected Only for PLY export, only selected objects are written. ASCII format can be used when the application that will open the file does not support binary format. Check the scale and axis settings for the target application as well.

5. Choose the mesh data. Export options include writing the active UV layer’s coordinates, normals, and vertex colors. The Blender Manual notes that most other applications can calculate their own normals; however, you may need to export normals when matching Blender normal map textures. N-gons with four or more vertices can be converted to triangles using the Triangulated Mesh option. Apply Modifiers exports the evaluated mesh—that is, the mesh after modifiers have been applied.

Transferring animated scenes with Alembic

1. Set the export scope and scale. If Selection Only is enabled for Alembic export, selected objects are exported; if it’s disabled, all objects are included. You can leave Global Scale at its default of 1.0 to use Blender units. By default, the export’s start and end frames use the scene’s current frame range.

2. Configure animation sampling. Transform Samples determines how many times per frame animated location, rotation, or scale transformations are sampled. Geometry Samples works similarly for animated geometry. Shutter Open and Shutter Close define the sampling time range; values are between -1 and 1. As an example, the manual gives a setting of 5 samples, -0.25 for the shutter opening, and 0.25 for the shutter closing to produce detailed mesh motion blur data.

3. Review geometry and UV options. When UV Coordinates is enabled, UV maps are exported. Although the Alembic standard supports only one UV map, Blender exports all UV maps so that other software can read them. Normals, Color Attributes, and Triangulate can also be used as needed. The Subdivisions > Apply option lets you apply Subdivision Surface modifiers before writing the file. Use Schema determines whether polygonal meshes are written with the SubD or PolyMesh schema.

4. Consider instanced objects and hierarchy. Use Instancing exports duplicated or instanced objects as Alembic instances; according to the manual, this can speed up export, and it can be disabled for compatibility with other software. When Flatten Hierarchy is disabled, parent-child relationships are preserved; when enabled, those relationships are not exported and transformations are written in world coordinates. Custom Properties is enabled by default and can export supported custom properties.

5. Consider validation on import. Meshes that change during Alembic import receive Mesh Sequence Cache modifiers; changing object transformations use Transform Cache Constraint. Validate Meshes checks for corrupted data and repairs it if needed. This check can slow down the import, but the manual recommends enabling it, noting that data errors may not always be obvious. Set Frame Range updates the scene’s start and end frames to match the range in the Alembic archive.

What to consider in architectural and visualization workflows

For static model transfer, PLY lets you choose whether to include UVs, normals, or color data along with the geometry. Before sending a file to another application, check that the required data is actually exported and that the axes match. Alembic is suited to teams that need to transfer animated meshes and transformations between applications; the Blender Manual gives an example of a hybrid workflow in which files from Houdini or Maya are shaded and rendered in Blender.

Alembic transfers baked results, not the procedural tools or rigs themselves. Keep this limitation in mind if you need to continue editing the production setup in another application. Frame rate also matters: Alembic works in time, and Blender uses the current scene frame rate to convert frame numbers to seconds. When transferring between teams, checking this setting and testing how the target software interprets the file can help prevent unexpected timing differences.

Common mistakes and next steps

• If the file won’t open in another application, try selecting ASCII for PLY export; the manual notes that this can help with applications that don’t support binary PLY.

• If an object appears at the wrong scale or orientation, review the scale and Forward/Up Axis settings for both import and export.

• If colors look different than expected, check whether the PLY color data is sRGB or Linear.

• If animation timing is off, verify the Blender scene frame rate and remember that Alembic is time-based.

• If you encounter problems importing a mesh, enable Validate Meshes; keep in mind that the check can slow down the import.

Start by testing the file in the target application to check that it opens correctly and that its orientation, colors, and animation look right. If the results meet expectations, apply the same settings to the full scene. For animated geometry transfers, also review UV, normals, sampling, and hierarchy options according to the project’s requirements.

Source and license

This guide was translated and adapted from the Stanford PLY and Alembic sections of the Blender Manual. Both sources are licensed under CC BY-SA 4.0.