PLY to OBJ converter
Drop your .ply file — we convert it to .obj right in your browser. Files never leave your computer.
Why convert PLY to OBJ?
PLY is the Stanford-pedigree scan format — RealityCapture, Meshroom, and Agisoft Metashape all export it. OBJ is where scans enter Blender / ZBrush for retopology, cleanup, and compositing. The path from raw capture to usable DCC asset usually runs through this pair.
Who runs this conversion
Photogrammetry users moving a RealityCapture / Meshroom output into Blender for cleanup, LiDAR scan operators processing field data, and researchers / academics handling Stanford-format 3D scan archives.
Things that commonly go wrong
- PLY per-vertex colours drop — OBJ has no built-in vertex colour channel. For colour, go PLY → GLB instead.
- Pure point-cloud PLYs without faces convert to an empty OBJ (OBJ is face-based). Mesh the cloud in MeshLab or Blender Remesh first.
- Large scans produce enormous OBJ text files; consider GLB or decimating the mesh first for smoother downstream work.
Technical note for this tool
Three.js PLYLoader accepts both ASCII and binary-little-endian variants, produces a BufferGeometry, then OBJExporter writes a single .obj with positions, normals, and UVs when present. No .mtl emitted.
PLY vs OBJ— what's the difference?
Stanford Polygon format — the preferred mesh format for 3D scanning, photogrammetry, and point clouds.
- Stores per-vertex colour, normals, and custom attributes
- Handles both meshes and raw point clouds
- Compact binary mode available
- Less common in art / game pipelines
- No material or texture references
Human-readable Wavefront mesh format — ubiquitous in 3D graphics, game art, and asset pipelines. Pairs with a .mtl material file.
- Supported by virtually every 3D tool (Blender, Maya, 3ds Max, Unity, Unreal…)
- Plain-text, easy to diff and hand-edit
- Keeps UV coordinates and vertex normals, unlike STL
- Material references via companion .mtl file
- Text format — larger on disk than binary meshes
- No scene hierarchy, no animation, no skeletons
- Materials live in a separate file; easy to lose
Deeper context on the formats
PLY — where it came from
Designed at Stanford in the mid-1990s by Greg Turk and colleagues for the Stanford 3D Scanning Repository — the "Bunny" and "Dragon" reference meshes that every graphics student has rendered at least once. PLY's header-driven schema means it can describe point clouds, meshes, or anything in between without a spec change.
- ASCII PLY inflates huge point clouds to multi-gigabyte files; always save binary little-endian unless you specifically need human-readable output.
- Per-vertex colour is encoded differently across exporters (RGB vs RGBA, 0-255 vs 0.0-1.0) — validate that colours survive the round-trip.
- Tools that expect triangles will silently drop n-gons and edges-only PLY data; pre-triangulate if the downstream is a mesh renderer.
Real-world use: Photogrammetry outputs (Meshroom, RealityCapture, Agisoft Metashape), LIDAR scans, cultural-heritage scanning projects, and academic graphics research. If a dataset comes from a camera rig or laser scanner, it is usually PLY.
OBJ — where it came from
Created by Wavefront Technologies in the late 1980s for their Advanced Visualizer software. When Wavefront was absorbed into Alias (then Autodesk), the format stayed public and became the lingua franca for academic 3D research, hobbyist modeling, and early game art. Its ASCII simplicity is why every graphics textbook still ships an OBJ example file.
- The .mtl material file must travel with the .obj — ship them as a zip or the textures will vanish on the other side.
- Negative indices and per-face normals exist in the spec but many importers silently misread them. Re-export from a round-trip through Blender if a downstream tool complains.
- Triangulate before export if the target is a game engine — Unity and Unreal OBJ importers choke on n-gons.
Real-world use: Computer-graphics research papers still use OBJ as the reference format for meshes. Hobbyist marketplaces (TurboSquid, CGTrader free tiers) distribute OBJ + MTL packs. Photogrammetry pipelines (Meshroom, RealityCapture) output OBJ as the portable intermediate. It is still the safest format to hand to a stranger who just said "I need a 3D model."
How to convert PLY to OBJ
- 1Drop a .ply file onto the page. Both ASCII and binary-little-endian PLY parse natively.
- 2Preview the mesh (or point cloud) in 3D — inspect vertex colour and topology before converting.
- 3Click Download .OBJ. Open directly in Blender, Maya, 3ds Max, or any Wavefront-aware viewer.
FAQ
Why convert PLY to OBJ?
PLY is the canonical scan / photogrammetry format (RealityCapture, Meshroom, Agisoft all export it). OBJ is the canonical DCC format. Converting lets you take a scan into Blender or ZBrush without a plugin.
Will vertex colours come across?
OBJ has no per-vertex colour channel in the base spec. Colour data from the PLY is dropped during conversion. If you need colour, convert PLY → GLB instead (GLB stores vertex colour as a PBR attribute).
What about point clouds?
OBJ is a face-based format — it cannot represent pure point clouds. If your PLY is a raw point cloud without faces, the resulting OBJ will be empty. Mesh your scan first (Meshlab, Blender remesh, etc.) before converting.
Are UV coordinates preserved?
If the PLY includes UV (most scanner exports do not), the OBJ writer emits vt lines. Textures are not moved — a companion .mtl is not generated.
Is anything uploaded?
No. The PLY is parsed in your browser and re-exported as OBJ locally. The file never leaves your device.