Updated August 2026
Wavefront in. PLY out.
Use this when a scan or research app wants PLY and you only have OBJ. For print, OBJ to STL is the straighter path. For web, OBJ to GLB.

Source OBJ, target PLY, drop, download binary PLY.
1
Source is OBJ. The File API reads it in this tab. Nothing is posted. Keep it under 80 MB.
2
Binary PLY from the OBJ mesh.
3
Open in the PLY-aware app.
This page is only OBJ → PLY. Other pairs have their own keep and lose notes so they do not repeat this conversion.
| On this conversion | What happens |
|---|---|
| Keeps | Faces in PLY. |
| Drops | OBJ groups and any MTL look. |
| Next step | MeshLab or similar. Print should be OBJ to STL. |
| Attribute | Result on the reference scene |
|---|---|
| Separate objects | Merged into 1 |
| UV coordinates | Kept |
| Vertex colour | Kept |
| Material names | Lost |
| Vertices on the reference scene | 48 of 48 |
| Mesh | Source | PLY | Change | Vertices written |
|---|---|---|---|---|
| mug.glb | 880 KB | 1,221 KB | 1.4x | 25,000 |
| lion.glb | 8,768 KB | 12,176 KB | 1.4x | 249,369 |
OBJ as the source: Geometry only. Color and clips are dropped. Measured 2026-08-27 by running this converter’s own loaders and exporters headlessly. How every format was measured.
OBJ is parsed with the File API. PLY is written in memory. OBJ groups and any MTL look. That is a format rule, not an upload. Files over 80 MB are refused because RAM is the limit.
Use this when a scan or research app wants PLY and you only have OBJ. For print, OBJ to STL is the straighter path. For web, OBJ to GLB.
Source OBJ, target PLY, drop, download binary PLY. No Blender and no account.
STL for slicers. PLY for research and scan tools that name PLY.
No. MTL is skipped. You get geometry.
No. OBJ is parsed here and PLY is written in memory. There is no convert API.
Yes. Open the OBJ viewer if you only need to orbit. Convert when the next tool actually wants PLY.
MeshLab or similar. Print should be OBJ to STL.