Convert PLY 3D scans to binary STL locally - ready for 3D printing and any slicer. No upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
PLY (Polygon File Format, also called the Stanford Triangle Format) is the typical output of 3D scanners and tools like MeshLab or CloudCompare. For 3D printing, however, slicers such as Cura or PrusaSlicer expect STL. This tool reads your PLY - ASCII or binary - and writes a compact binary STL you can send straight to the printer.
Both ASCII and binary PLY (little- and big-endian) are recognised; the tool reads the header and decodes the vertices and faces accordingly. Faces with more than three corners are split into triangles, since STL knows only triangles, and a face normal is computed for each one. The result is binary STL, the compact form every slicer reads.
Everything runs entirely locally in the browser - your possibly confidential scan never leaves your device. Honestly framed: pure geometry is transferred. PLY vertex colours and extra per-vertex attributes have no counterpart in STL and are dropped. An invalid or empty PLY file is rejected with a clear message instead of faking an output.
| Input formats | PLY |
|---|---|
| Output format | STL |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Converts PLY (ASCII and binary, little- and big-endian) to compact binary STL: faces are triangulated, a normal is computed per triangle. Pure geometry is transferred - PLY colour and extra vertex attributes are dropped (STL has no counterpart). An invalid or empty PLY file is rejected with a clear error.
Yes. ASCII and binary PLY (little- and big-endian) are read; the header is parsed to decode the data correctly.
No. STL stores geometry only, so PLY colours and extra vertex attributes are dropped.
Binary STL, because it is compact and read by every slicer. Faces are triangulated and a normal is computed per triangle.
No, the conversion happens entirely locally in the browser; your scan never leaves your device.