Simplify PLY geometry and export a more compact binary PLY.
Please wait
PLY is common for 3D scans and research meshes. This tool performs mesh decimation and writes the result as binary PLY. glTF-only encodings such as Meshopt and Draco are not applied. Everything runs locally in your browser.
Default50%
Range0% – 100% · step 5%
Reduces the number of faces and vertices using mesh simplification. Default medium strength; increasing strength shrinks file size further but may lose surface detail. Only affects geometric density, not the container format.
Drag a PLY file onto the upload area
Adjust mesh simplification strength
Preview the result, then download optimized binary PLY
PLY vertex compression keeps the source format: the tool simplifies the mesh and writes compact binary PLY rather than converting to GLB. A GLB with Draco or Meshopt is only produced by the dedicated GLB/GLTF vertex compression tools.
Meshopt and Draco are extension codecs for the glTF container, so they cannot be applied to a PLY file. PLY compression is achieved through mesh simplification plus binary encoding, which is the effective approach for scan and research meshes.
This tool is designed for mesh models with polygonal surfaces. A pure point cloud has no faces to simplify, so it is better handled by a dedicated point cloud processing tool. PLY files that contain a triangulated surface work normally.
Yes. Simplification only reduces the face count. Vertex colors, normals, and other per-vertex attributes are carried over unchanged, so the compressed PLY remains suitable for visualization and analysis.
PLY has both ASCII and binary variants. The tool reads ASCII and binary input and always writes binary PLY, which is much smaller and faster to load while containing the same vertex data, colors, and normals.
Yes. Binary PLY is a standard format supported by Blender, MeshLab, CloudCompare, and most scan and post-processing pipelines. Only the face count changes, so the compressed file opens anywhere the original PLY did.
How many bytes does vertex data actually take? Quantization, MeshOpt, and Draco - which tool fits which scenario? It's not about 'Draco is best,' but 'the right tool for the right job.'
Take a 50MB PBR model through the full pipeline—Blender export, vertex compression, KTX2 texture conversion, engine loading—and get it under 5MB. Includes a complete automation script and a series cheat sheet.
Desktop, mobile, VR, mini-programs—which compression combination should you use? This article consolidates the knowledge from the previous four articles into a decision matrix and an automation script—just follow it.
Don't fall for the AI rendering hype. See the real strengths and hard limitations of 3DGS in production, understand the browser performance bottlenecks of PLY/SPLAT files, and face the brutal truth about converting splats to mesh geometry.
