Convert STL to PLY

Why convert STL to PLY?

STL to PLY is a niche conversion, but it has clear uses. PLY is accepted by MeshLab, CloudCompare, Open3D and many research or scanning workflows that expect it, and it is easy to parse in scripts. Converting STL to PLY merges identical vertices, so the file stores each point once instead of repeating it for every triangle, which usually reduces size and makes the mesh easier to process. The shape is unchanged. PLY can store per-vertex colour, but an STL contains none, so the output is uncoloured; you can add colours in MeshLab afterwards. PLY has no unit field, so the numbers remain in millimetres as in the STL, and it is worth recording that for whoever opens the file next.

How to convert STL to PLY

1. Drop your STL file onto the converter — it opens in your browser, nothing is uploaded.
2. Check the preview and the dimensions in mm; fix units or the up axis in “Units & orientation” if the size or orientation looks wrong.
3. Choose PLY as the output and click Convert. Several files download as one ZIP.

What carries over from STL to PLY

What changes

• Identical vertices are welded, giving a shared-vertex mesh instead of repeated triangle corners.
• No colours are added; the PLY has geometry only.
• Unit is not stored; numbers remain in millimetres.
• Triangle count and shape are unchanged.

Tips

• Use MeshLab or CloudCompare to add vertex colours or compute normals after conversion.
• For Open3D or Python scripts, a PLY with shared vertices loads faster than a raw STL.
• Check the viewer's watertight flag if you plan to run volume or Boolean operations.

About STL files

STL was created by 3D Systems in the late 1980s for its stereolithography machines, and it became the default exchange format for 3D printing. A file describes a surface as a list of triangles, each with three vertices and a facet normal. That is all it contains. There is no header field for units, no colour, no texture and no notion of separate parts. Two flavours exist: ASCII, which is readable text but large, and binary, which spends exactly 50 bytes per triangle after an 80-byte header and a 4-byte triangle count. Binary is what almost every modern tool writes. Because the format is so small and so old, every slicer, CAD package and mesh editor can read it, which is why hobbyists still download most printable models as STL from sites like Printables and Thingiverse.

About PLY files

PLY was developed in the mid-1990s by Greg Turk and colleagues at the Stanford Graphics Lab to store data from 3D scanners, and the Stanford Bunny and Happy Buddha models made it famous. A PLY file starts with a text header that declares elements, such as vertex and face, and the properties each element has. The body then follows in ASCII, binary little-endian or binary big-endian. Because properties are declared in the header, a file can carry any extra per-vertex data: normals, colour channels, intensity, confidence or custom scalars. This flexibility made PLY a standard output for scanners, depth cameras, photogrammetry and point-cloud tools. It can store a point cloud with no faces at all, or a polygon mesh. It does not define units or a scene structure.

3D printing notes

STL is still the safest file to hand to a slicer. Bambu Studio, PrusaSlicer, OrcaSlicer, Cura and the resin tools Chitubox and Lychee all import it, and they all treat the numbers as millimetres. The usual problems are scale (a model exported from a metre-based tool arrives 1000 times too small) and meshes that are not watertight, which makes slicers fill or skip regions. MeshShift shows the real dimensions before you convert and can scale from metres automatically. Its print check lists holes, non-manifold edges and flipped normals, and one click rebuilds a closed solid at the same size. If you need colours or several plates in one file, use 3MF instead.

More conversions