If you came to stl viewer to inspect or prepare a scan, this guide explains how PLY-to-OBJ conversion affects mesh data, scale, normals, UVs, and vertex colors.
PLY is a useful scan format, but OBJ is often easier to open in Blender, ZBrush, Maya, Unity and other 3D applications. This tutorial shows how to convert a binary or ASCII scan while checking its mesh data, scale, normals, UVs and vertex colors along the way.

The short version
- Open the scan in ply to obj, then check that it contains triangles rather than vertices only.
- Set File units to match the units used by the scan. PLY has no unit field, and a meter-based scan left as millimeters will be 1,000 times too small.
- The conversion keeps faces, normals, UV coordinates and per-vertex colors. It does not load a separate texture image referenced by a PLY comment.
- Test the resulting OBJ in your target application because some OBJ importers ignore vertex colors and display the model gray.
What OBJ can carry from a PLY scan
PLY and OBJ both describe polygon meshes, but they organize color and supporting data differently. A PLY file can contain vertices, faces, normals, UV coordinates and RGB values stored at each vertex. OBJ can represent the geometry, normals and UVs, while vertex color support depends on a commonly used extension rather than the original OBJ specification.
That distinction matters for colored photogrammetry and structured-light scans. A model may look correctly colored in MeshLab or Blender, then appear gray in another application even though the color data is still present in the file.
The conversion also works with both binary and ASCII PLY files. Binary files are compact, while ASCII files are readable text, but both can describe the same mesh. The browser converter accepts files up to 200 MB and runs without uploading the scan.
Step 1: Open the scan and confirm it has faces
Start by dropping the .ply file onto the converter or choosing it from disk. You can also use its sample file to inspect the controls before loading a scan.
Before exporting, look at the preview and the information panel. A mesh has vertices and triangles. Those triangles are the surfaces that OBJ will write and that a modeling application can shade, edit or deform.
A PLY containing vertices without faces is a point cloud, not a mesh. It may look dense and solid from one angle, but there are no surfaces between the points. An OBJ export cannot invent those surfaces. If the panel reports Points and shows no triangles, reconstruct the surface in MeshLab or CloudCompare first, save the result as a mesh PLY, then return to the conversion step.
For a second inspection, the ply viewer shows whether a file opens as a shaded mesh or as a point cloud. It also displays the vertex and triangle counts, bounding box and file size, while showing vertex colors when the PLY stores them.

The PLY Viewer distinguishes a shaded mesh from a point cloud and exposes the counts needed before conversion.
Step 2: Set the scan's units
PLY does not contain a standard unit field, so the converter needs to know how to interpret the coordinates. File units starts at mm, which suits many desktop and handheld scanners.
Phone, LiDAR and photogrammetry applications commonly produce coordinates in meters. If that describes the source file, switch File units to m before exporting. Otherwise, a scan intended to be two meters tall can become 1,000 times too small when the OBJ is opened elsewhere.
Use the live size information as a sanity check. Think about the object rather than trusting the filename: a person, room or large statue should not measure like a small tabletop part, and a small object should not suddenly become room-sized. If the preview dimensions are wrong, correct the units before downloading instead of trying to rescue the scale in every application later.
This check is especially important because OBJ has no reliable unit metadata that every program interprets consistently. Keeping the source scale correct at conversion gives you a known starting point, but still verify the import size in the destination application.
Step 3: Export the OBJ
Once the mesh and scale look right, choose Convert to OBJ. By default, the download is a ZIP containing the .obj file and a small .mtl file. The MTL is the companion material file used by many OBJ workflows.
If a bare geometry file is more convenient, turn off Include materials & textures before converting. This does not turn vertex colors into a texture. It simply avoids packaging the material-related output when you do not need it.
Keep the original PLY as the archive copy. It contains the scan's original property data and is the better source for future processing. The OBJ is the interchange copy for applications that prefer Wavefront geometry.

The PLY to OBJ page provides the file preview, unit setting and export options before the OBJ is written.
What survives the conversion
For a typical meshed scan, the important data behaves like this:
- Vertices and faces — Kept. Faces are written as triangles.
- Vertex normals — Kept when present. If the PLY has none, normals are computed.
- Texture coordinates — Kept when present and written as
vtentries. These coordinates tell a 3D application how an image should map across the surface. - Vertex colors — Kept as
v x y z r g bvalues. The RGB values are written in the range from 0 to 1. - Texture image named in a PLY comment — Not loaded. The converter reads the PLY itself, but does not fetch a separate image referenced by a comment.
Normals describe the direction each surface points, so they affect smooth shading and lighting. UV coordinates are a separate two-dimensional layout for an image texture. Vertex colors are attached directly to vertices, which is why they can survive without a conventional image texture, provided the importing application understands the extension.
The geometry is not automatically simplified or retopologized during this format change. If the scan contains dense, uneven or messy topology, the OBJ will reflect that. Conversion is the handoff between formats, not a replacement for scan cleanup.
Import checks in Blender and other applications
In Blender, use File, Import, Wavefront OBJ and select the converted file. If the MTL is beside the OBJ, Blender can read the associated material information. Check the model's dimensions, orientation and shading before continuing to sculpt, retopologize or export it again.
For vertex colors, inspect the imported mesh data rather than relying only on the viewport's default material. MeshLab, CloudCompare, Blender's OBJ importer and three.js read the common vertex-color form. Many other DCC tools and game engines ignore the extra RGB values and show the model in gray.
That gray display does not necessarily mean the conversion failed. It may mean the application supports OBJ geometry but not OBJ vertex colors. In that case, bake the colors to an image texture in Blender and export an OBJ with an MTL and image, or use a format with standardized color attributes.
Also check the mesh at close range. A scan can contain holes, floating fragments, thin parts or a scanning platform. OBJ preserves the converted geometry; it does not automatically make a scan watertight or ready for manufacturing.
When GLB or STL is the better choice
OBJ is a practical editing and interchange format, especially when the target application already has a reliable OBJ importer. It is less dependable when vertex colors must display consistently across web viewers, mobile AR tools and game engines.
For that workflow, ply to glb stores per-vertex RGB as the standard glTF COLOR_0 attribute. GLB also keeps positions, normals and UV coordinates, and is designed for browsers, AR and engines. The same unit warning applies: GLB uses meters, while the PLY source does not state its units.
For a one-color print, color data is unnecessary. ply to stl is the shorter route to a slicer, but STL drops vertex colors and UVs because the format stores only triangles and facet normals. A scanned STL may still need repair before slicing, particularly if the scan has holes or loose pieces.
FAQ
Why is my converted OBJ the wrong size?
The source PLY was probably interpreted with the wrong units. PLY has no unit field, so choose mm for millimeter-based scans or m for scans exported in meters, then check the output size again.
Why does my OBJ appear gray?
The OBJ may contain vertex colors, but the importing application may not read the common v x y z r g b extension. Try Blender, MeshLab, CloudCompare or three.js, or bake the colors into an image texture.
What happens to a PLY texture image?
A texture image named in a PLY header comment is not loaded during conversion. The mesh's UV coordinates can remain, but you must apply the image again in the 3D application or bake a new texture there.