Importing and Exporting PLY in Blender: Scale, Color, and Axis Settings

What will you learn in this guide?

We’ll cover how to manage size and orientation differences when importing PLY files into Blender, how to set the color space for vertex colors, and which geometry data you can include when exporting. The goal is not just to open the file, but also to preserve the data needed when transferring it to another application.

PLY is listed as Stanford PLY in Blender’s import and export documentation. The steps here can serve as a checklist for anyone sending a mesh from an architectural model, interior scene, or visualization workflow to another application. However, don’t assume the receiving software supports PLY features in exactly the same way; always check the result after transfer.

Requirements and preparation

You’ll need Blender and either a PLY file to import or a scene object to save as PLY. The Blender manual states that PLY import supports ASCII and binary files, and that you can select multiple files in a single operation. The source documentation does not specify a particular Blender version, account requirement, or license plan.

Before you start, find out—if possible from the source workflow—which units and axis convention the file uses, and whether its color data is in sRGB or linear color space. If that information is unavailable, inspect the imported geometry in the Blender scene, then open the exported file in the target application to verify it. This is a practical way to see how the target software interprets the settings.

Importing a PLY file into Blender

1. In Blender, start the import process via File > Import/Export > Stanford (.ply). You can select an ASCII or binary PLY file, or choose multiple files in one operation.

2. Use Scale to set the size at which the file is imported relative to the world origin. If the model looks larger or smaller than expected, first check the scale and the source file’s unit convention. The source manual describes the scale option but does not recommend a single value for all projects.

3. The Scene Unit option applies the current scene’s unit scale to the imported data. Consider the scene’s unit settings alongside the source data’s measurement convention. Rather than scaling the geometry by eye, first test whether this option gives you the expected result.

4. Forward Axis and Up Axis convert between differences in forward and up axes across applications. Blender’s manual describes the default convention as Y Forward, Z Up. For example, if the source application treats the Y axis as up, the manual gives the mapping -Z Forward, Y Up. Don’t apply this example automatically to every file; use the source axis convention.

5. Merge Vertices attempts to merge vertices at the same location where possible. Before enabling or disabling this option, consider whether preserving the imported mesh’s vertex structure is important to your workflow.

6. For a file containing color data, check Import Vertex Colors. None skips importing vertex colors. The sRGB and Linear options specify the color space in which the file’s color data was saved. The wrong choice may make colors look different in Blender than expected; if the file’s color space is unknown, test the result visually.

Exporting from Blender as PLY

1. Open Stanford (.ply) from the export menu. To send only specific objects, use Selected Only. According to the manual, instanced objects such as collection instances are considered selected when their instancers are selected.

2. Use Scale to set the scale of exported objects relative to the world origin. Then check Forward Axis and Up Axis against the target application’s axis convention. If the target application uses a different convention from Blender’s Y Forward, Z Up, the axis conversion can affect the result.

3. Format: ASCII saves the file in simple ASCII format. The Blender manual notes that this can be useful when the next application does not support the binary file format. If you’re unsure which format the target application accepts, test compatibility before transferring the file.

4. Choose which data to write in the geometry section:

   • UV Coordinates writes the active UV layer’s coordinates to the file.

   • Vertex Normals exports face and vertex normals. According to the manual, most applications can calculate their own normals; exporting these may be important when they need to match Blender normal map textures.

   • Vertex Colors lets you choose the color space for the color data. Consider how the application opening the file interprets color.

5. Triangulated Mesh triangulates all N-gons with four or more vertices. The manual states that this does not change the meshes in the scene; it affects the exported result. This option can be useful when you need to preserve the source scene’s topology while triangulating the exported file.

6. Apply Modifiers exports objects as evaluated meshes, using the result after modifiers have been calculated. Check this option if you want the file to include the effects of modifiers. Keeping an editable copy of the source scene separately makes it easier to ensure that the export’s modifier settings do not replace the scene itself.

Common issues

The model is the wrong size: First check the Scale and Scene Unit settings, then the source file’s unit information. Rather than fixing the problem by resizing the object by eye, also verify its dimensions in the target software.

The model has an unexpected orientation: The Forward Axis and Up Axis mapping may differ between the source and target applications. Use Blender’s Y Forward, Z Up convention as a starting point, and refer to the documented axis convention for the source application.

Colors look different: Check whether the sRGB or Linear setting for vertex colors matches how the data was saved in the file. If you don’t need the color data, note that the None option skips importing it.

UV or normal data is missing in the target application: Make sure UV Coordinates and Vertex Normals are enabled as needed during export. Use a small test file to check whether the target program can read this data.

Mesh faces look different: Triangulated Mesh triangulates certain N-gons during export. Also, Apply Modifiers uses the evaluated mesh. Compare the effects of these options in a test export separate from the main file.

How to use it in architectural and visualization workflows

Transferring scene data to another application with PLY requires considering options such as geometry, UVs, normals, and vertex colors individually. When exchanging meshes across different software in architecture firms or archviz teams, it’s especially important to check axis and scale settings. The source documentation does not guarantee that a file that looks correct on one team member’s computer will open the same way in another application.

For students and visualization artists, the safest approach is to test the transfer with a small sample object first. Sending an entire scene without seeing how the target software handles ASCII format, vertex colors, UVs, and normals can be risky. The manual does not specify hardware or license requirements, so no specific requirements in those areas can be inferred. Compatibility and data-loss checks should be a fundamental part of the workflow.

Next steps

After the transfer, open the PLY file in the target application and check its size, orientation, colors, and required geometry data. If there’s a problem, change one setting at a time and run another test. This makes it easier to identify whether the issue comes from scale, axis conversion, color space, or the geometry options selected during export.

Source and license

This guide was adapted into Turkish from Blender’s Stanford PLY import and export documentation. Source: Blender Manual, “Stanford PLY”; license: CC BY-SA 4.0.