Skip to main content

Convert PLY to STL — From 3D Scan to 3D Printer

You scanned something. Now you want to print it. The problem: your scanner (or photogrammetry software) gave you a PLY file, and your slicer wants STL. This converter bridges that gap.

Last updated Mar 2026

Data Loss — Converting PLY to STL will not preserve UV coordinates, vertex colors.

1
Upload
2
Convert
3
Download

Drag PLY file here, or click to upload

Supports .ply files up to 150MB

Usually under 3 seconds — depends on file size.

What You Should Know

What Actually Happens During Conversion

Geometry (vertices and faces) is preserved with exact coordinate fidelity — same triangles, same positions, zero data loss. What changes: (1) Vertex colors are discarded (STL has no color support). (2) Per-vertex normals are converted to per-face normals (STL uses flat shading — each triangle gets one normal vector). (3) Custom PLY properties (scan confidence, intensity, timestamps, segmentation labels) are stripped. (4) The indexed vertex structure is expanded to disconnected triangles (STL stores each triangle independently). Output is Binary STL by default — more compact and faster for slicers to parse than ASCII.

Preparing Scans for Successful Prints

Raw scans almost always need cleanup. Here's the checklist, in order of importance: (1) Non-manifold edges — the #1 cause of slicer errors. Check in MeshLab: Filters > Selection > Select Non Manifold Edges. Fix with Filters > Cleaning > Repair Non Manifold Edges. (2) Holes — occluded scan areas leave gaps. Fix: Filters > Remeshing > Close Holes (set max hole size appropriately). (3) Polygon count — most FDM printers can't resolve detail beyond 500K–1M triangles. Decimate: Filters > Remeshing > Quadric Edge Collapse Decimation. (4) Noise — Laplacian Smooth (2–3 iterations) removes scan noise without destroying features. Do all of this on the PLY before converting to STL.

PLY vs STL: What You Lose, What You Gain
FeaturePLYSTL
Vertex ColorsSupported (RGB/RGBA)Not supported (discarded)
NormalsPer-vertex (smooth shading)Per-face (flat shading)
Custom PropertiesExtensible (confidence, intensity)None
Vertex StorageIndexed (compact)Duplicated (larger files)
Slicer SupportLimited (MeshLab, CloudCompare)Universal (every slicer)
File SizeSmaller (indexed + optional compression)1.5–2× larger (disconnected triangles)

Keep PLY for scan storage, analysis, and processing. Convert to STL only as the final step before sending to your 3D printer slicer.

When to Convert PLY to STL

Replica Printing from 3D Scans

Scanned a figurine, mechanical part, or anatomical model with a structured-light scanner or photogrammetry? Convert PLY to STL to print an exact physical replica. Scale in your slicer if needed — common for miniatures (scale to 50%) or enlargements (200%). For best results, decimate to 500K–1M triangles and repair non-manifold edges before printing.

Prosthetics and Medical Devices

Medical 3D scanning (structured-light scanners, CT/MRI-derived meshes) produces PLY files that feed into prosthetic design workflows. Convert PLY to STL for printing custom-fit prosthetic sockets, dental models, orthodontic aligners, or surgical planning guides. Note: medical prints typically require specific materials (biocompatible resins, PETG) — check your printer and material certifications.

Architectural and Terrain Models

LiDAR scans of buildings, terrain, and construction sites produce large PLY point clouds. Process in CloudCompare (crop, decimate, mesh reconstruction), then convert to STL for printing architectural scale models, site context models, or terrain reliefs. Typical workflow: CloudCompare for point cloud → MeshLab for meshing → this converter for STL → slicer for printing.

Reverse Engineering

Scanned a legacy part with no CAD files? Convert the PLY scan to STL for direct printing of replacement parts. For functional parts, you may want to import the STL into Fusion 360 or FreeCAD and trace over it to create a proper parametric model — but for one-off replacements, scan-to-print via PLY→STL is the fastest path.

Frequently Asked Questions
Usually, but check it first. PLY scan data frequently has mesh problems that transfer directly to the STL: holes from occluded scan areas, self-intersecting faces from registration errors, inverted normals, and non-manifold edges. Import the STL into your slicer and look for warnings — Cura shows an orange mesh-error icon, PrusaSlicer highlights problems in yellow/red. For automated repair, Meshmixer's Inspector tool (free) fixes most common issues in one click. If you want to fix before converting, use our [STL Repair Tool](/repair/stl) right in the browser.
If the file is under 150 MB, yes. But the resulting STL will be equally large — and most 3D printers don't benefit from more than 500K–1M triangles. The extra detail is below the printer's physical resolution. Decimate first in MeshLab (Filters > Remeshing > Quadric Edge Collapse Decimation, set target face count to 500K–1M), then convert the simplified PLY to STL. This gives you a smaller, faster-to-slice file with no visible quality loss in the print.
They're discarded — STL is geometry-only, no color support at all. If you need colored 3D prints, you have two options: (1) Convert PLY to 3MF instead, which supports per-vertex and per-triangle color, then use Bambu Studio or PrusaSlicer's color painting tools. (2) Convert PLY to GLB for web display where vertex colors are preserved natively.
Fix the PLY before converting — it's much easier to clean up in PLY format. In MeshLab: apply Laplacian Smooth (Filters > Smoothing > Laplacian Smooth, 2–3 iterations, lambda 0.5). For severe noise: use Statistical Outlier Removal in CloudCompare first, then Poisson Surface Reconstruction for a clean watertight mesh. Then convert the cleaned PLY to STL. Trying to smooth after conversion to STL is harder because STL's disconnected triangles make vertex-based smoothing less effective.
Yes, typically 1.5–2× larger. STL stores each triangle independently (50 bytes per triangle with duplicated vertices), while binary PLY uses indexed vertices (~24–32 bytes per triangle). A 5 MB binary PLY might become 8–12 MB STL. This is the tradeoff for universal slicer compatibility. If file size matters for sharing, consider converting to 3MF instead — it uses ZIP compression and is usually smaller than both PLY and STL.
Photogrammetry meshes have specific characteristics: very high poly count (often 5–20M faces), vertex colors from the photo texture, and potential holes where the camera couldn't see. Before converting: (1) Decimate to 500K–1M faces for printing. (2) Fill holes in MeshLab (Filters > Remeshing > Close Holes). (3) Check for non-manifold geometry. The vertex colors will be lost in STL, but the geometry prints fine. For color preservation, use PLY to 3MF instead.

Related Converters

What's Next? Try These Tools

Learn More

More PLY Conversions

Step-by-Step Guides