Preserved
- Triangle and convex quad surface geometry is preserved.
- Vertex positions are retained; no missing scene transforms are invented.
From scanned surfaces to printable triangles
PLY to STL Converter Online
Prepare a PLY surface mesh from a scanner or photogrammetry workflow for STL-based slicing. Inspect the geometry, confirm its physical scale, and download a verified STL. Scan colors are removed; point clouds need surface reconstruction first.
Drop PLY file here
or browse your computer
Max 100 MB · processed locally
Your model stays on this device. Parsing, conversion, verification, and download preparation run locally in this browser.
What the conversion keeps and removes
Converted
- Convex quads become STL triangles. Point clouds and larger polygons require a mesh export first.
- PLY is treated as one mesh. Custom object labels and disconnected shells are not automatically split.
- PLY and STL are unitless. Confirm the intended source unit and check output dimensions.
- The source up axis is a guess until confirmed; the selected rotation is applied once.
- Smooth vertex normals become flat triangle normals.
Lost
- Texture coordinates are lost in STL.
- Scan colors and transparency are lost; STL contains only geometry.
- Custom material properties are not written to STL.
- Texture image references are ignored; no companion images are loaded.
- Scanner confidence, custom attributes, comments, and manufacturing metadata are discarded.
Unsupported input
- Cameras and lights cannot be reconstructed from PLY.
- PLY point clouds and Gaussian splats are not reconstructed into surfaces; animation is unavailable.
- Exact CAD curves, features, and missing scan surfaces cannot be recovered.
- Supports, layer settings, and other slicer settings must be configured in a slicer.
Does your PLY contain a surface or just points?
A PLY file may describe a colored surface mesh, a point cloud, or Gaussian splats. This converter needs face records that connect vertices into triangles or convex quads. It reads ASCII, little-endian binary, and big-endian binary PLY 1.0 locally. A file containing only points has no defined surface to write to STL: reconstruct a mesh in your scanning software first. Conversion does not fill gaps or guess missing surfaces.
- ASCII and binary PLY 1.0
- Surface mesh preview
- Explicit unit and up-axis controls
- Convex quad triangulation
- Exact STL download verification
- Local browser processing
What changes in a PLY scan
Existing faces define the result
Triangles remain triangles and convex quads become two triangles. Triangulate larger or concave polygons in the source editor before uploading.
Color is separate from shape
RGB values, transparency, UV coordinates, and custom scanner properties are omitted. Both previews show surface geometry with neutral shading.
Measurements need a unit assumption
PLY has no standard unit or up-axis declaration. Confirm what one coordinate represents and which axis points up; the selected scale and rotation are applied once.
How to convert PLY to STL
Step 1
Open a PLY surface mesh
Choose a .ply file up to 100 MB. Inspect the input geometry, triangle count, and dimensions. Export faces first if the source contains only points.
Step 2
Confirm the scan coordinates
Set the intended source unit and up axis, then choose the STL coordinate unit and orientation. Standard PLY produces one surface mesh; custom part labels cannot be used to split it.
Step 3
Inspect and download verified STL
Convert the mesh, inspect the preview rebuilt after the generated STL bytes are reparsed, check dimensions, and download after validation succeeds.
Where PLY to STL fits a scanning workflow
Print a scanned object
Turn an existing scan surface into STL for a slicer. Check holes, wall thickness, and dimensions before planning a print.
Prepare a photogrammetry mesh
Use a triangulated reconstruction from photographs when the destination needs shape without its captured color.
Move a research mesh into a print workflow
Convert a PLY surface containing measurement or confidence attributes to a portable STL while keeping the original PLY as the data source.
PLY and STL are different file formats
PLY (Polygon File Format, also called Stanford PLY) stores a table of vertices and optional faces, with extensible properties such as color and scanner confidence. STL stores independent triangular facets. A PLY surface can become STL, but color and custom attributes cannot accompany those facets, and a face-free point cloud does not define them.
| Property | PLY | STL |
|---|---|---|
| Surface | Vertices with optional polygon faces | Triangle facets only |
| Scan appearance | Vertex colors and custom properties | Geometry only |
| Point cloud | Can store vertices without faces | Needs a reconstructed surface |
| Scale and orientation | No standard unit or up axis | Unitless; explicit numeric conversion |
| Parts | One standard mesh collection | One STL from this PLY importer |
Resolve PLY conversion problems
- The file is reported as a point cloud
- Use surface reconstruction in your scan software and export faces. Renaming a point cloud or Gaussian splat file cannot create a printable surface.
- The scan is too small or too large
- Choose the source coordinate unit used by the scanner, select the desired STL coordinate unit, and compare the verified dimensions with a known measurement.
- A face or coordinate is rejected
- Repair invalid face indices and zero-area triangles, then triangulate complex polygons. Re-export an uncompressed PLY 1.0 file with x, y, z and face indices.
PLY to STL limitations
- Point clouds and Gaussian splats cannot be converted until a surface mesh has been reconstructed.
- Only triangles and convex quads are accepted. Triangulate concave or larger polygons before conversion.
- STL loses PLY scan colors, texture coordinates, and custom attributes, and stores no physical unit.
- Standard PLY is treated as one mesh. Custom part IDs and disconnected shells do not create separate STL files.
- Conversion does not repair holes, self-intersections, thin walls, or scanner noise. Custom texture references are ignored and never fetched.
PLY to STL FAQ
Can this convert a PLY point cloud or Gaussian splats to STL?
No. STL needs triangle surfaces. Reconstruct and export a surface mesh first; this tool does not invent connectivity between points.
Will STL keep the colors from my scan?
STL loses PLY scan colors, texture coordinates, and custom attributes, and stores no physical unit.
Which PLY encodings are supported?
ASCII and binary PLY 1.0 in either byte order are supported when they contain valid triangle or convex quad faces. Compressed wrappers and complex polygons require re-export.
Can disconnected scan pieces become separate STL files?
Standard PLY provides one vertex and face collection rather than named scene objects. This converter writes one STL and does not infer parts from disconnected shells. Separate the pieces in a mesh editor first.
Does conversion upload my scan?
No. Parsing, previews, coordinate conversion, STL verification, and download preparation all run locally in your browser.
Did your scanner export OBJ instead?
Use OBJ to STL for a scan exported with named objects or groups; that route can split detected objects into separate STL files.