Skip to main content

Convert PLY to GLB Online — Publish 3D Scans on the Web

Turn PLY scan data into GLB for interactive web display, augmented reality, and real-time 3D applications. PLY is the standard output from photogrammetry software (Agisoft Metashape, RealityCapture, COLMAP) and 3D scanners (Artec, Revopoint, iPhone LiDAR). GLB is the binary glTF 2.0 container — the JPEG of 3D — natively supported by every major web engine.

Last updated Mar 2026

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 Changes During Conversion

Geometry (vertices and faces) is fully preserved with zero data loss. Vertex colors (RGB/RGBA) are mapped to glTF COLOR_0 accessor — this is the key advantage over the OBJ path, which has no vertex color support. Vertex normals are preserved for smooth shading. Custom PLY properties (scanner confidence values, intensity channels, timestamps, custom float attributes) are discarded because glTF 2.0 has no equivalent fields. If the PLY has no vertex colors, a default PBR material is assigned (base color #808080, metallic 0.0, roughness 0.5).

File Size: PLY vs GLB

Binary PLY and GLB store geometry similarly, so raw file sizes are comparable (a 1M-vertex mesh is ~40-50MB in both). The real savings come from post-conversion compression: gltfpack with Draco encoding typically achieves 80-90% reduction (50MB → 5-8MB). Meshopt compression offers 60-70% reduction with faster decompression. For web delivery, always compress — uncompressed GLB over 10MB causes noticeable load times on mobile networks.

Polygon Budget Guidelines

Raw scans are too heavy for real-time rendering. Target polygon counts by platform: mobile AR (model-viewer) — under 200K triangles for 60fps; desktop web viewer (Three.js) — under 1M triangles; high-end workstation — up to 5M with LOD. Decimate in MeshLab (Quadric Edge Collapse Decimation) or CloudCompare before converting. A 20M-face scan decimated to 500K faces loses minimal visual quality at web viewing distances.

PLY vs GLB: Detailed Comparison
FeaturePLYGLB
Vertex ColorsNative (RGB/RGBA per vertex)Supported (COLOR_0 accessor)
PBR MaterialsNot supportedFull metallic-roughness workflow
AnimationsNot supportedSkeletal, morph targets, keyframe
CompressionBinary mode onlyDraco (80-90%) / Meshopt (60-70%)
Custom PropertiesExtensible header (any property)Extensions (KHR_ prefixed)
Typical UseScanning, research, point cloudsWeb3D, AR/VR, game engines
Browser SupportRequires JS parserNative in all major engines

Keep PLY for scan processing pipelines (MeshLab, CloudCompare, Open3D, COLMAP). Convert to GLB when publishing scans on the web, delivering to clients, or building AR experiences. For 3D printing scanned objects, convert PLY to STL instead.

When to Convert PLY to GLB

Cultural Heritage & Museum Collections

Museums and archaeology departments publish 3D scans of artifacts online. Workflow: scan artifact → export PLY from Agisoft Metashape → convert to GLB here → embed with model-viewer on collection website. Visitors rotate and inspect artifacts with preserved scan colors, no plugin required. The Smithsonian, British Museum, and Sketchfab all use GLB for web-based 3D collections.

AR Product Visualization

Place scanned objects in augmented reality for e-commerce or real estate. Convert PLY to GLB, add to your page with model-viewer's AR mode (ar attribute), and users view the scan in their physical space on Android (Scene Viewer) or iOS (AR Quick Look with USDZ fallback). A scanned piece of furniture at 300K triangles loads in under 2 seconds on 4G.

Photogrammetry Portfolio & Client Delivery

Showcase photogrammetry work on your portfolio. Convert PLY scan output to GLB, embed interactive Three.js viewers, and let clients explore scans in full color. Deliver final scans as GLB files — clients can view them in Windows 3D Viewer, macOS Preview, or any web browser without installing specialized software.

Point Cloud to Mesh for Web Engines

LiDAR and structured-light scanners often output PLY point clouds (vertices without faces). If your PLY contains faces, this converter produces a standard mesh GLB. For point-cloud-only PLY files, the GLB will contain point primitives — viewable in Three.js (Points material) but not in model-viewer. For best results, reconstruct a mesh surface in MeshLab (Poisson Surface Reconstruction) before converting.

Frequently Asked Questions
Yes. GLB's glTF 2.0 spec supports vertex colors as COLOR_0 accessors. This converter maps PLY's per-vertex RGB (or RGBA) values directly to glTF vertex color attributes. The colors render correctly in Three.js, Babylon.js, Google model-viewer, and WebXR — no texture files needed. A 5M-vertex colored scan typically converts in 3-5 seconds in-browser.
Yes. Three options by complexity: (1) Google model-viewer — one HTML tag, supports AR on mobile, under 50KB gzipped; (2) Three.js + GLTFLoader — full control over lighting, camera, post-processing; (3) Babylon.js — built-in inspector and physics. All handle vertex-colored GLB natively. For best performance, keep models under 1M triangles and enable Draco compression.
Not for web use. A 20M-face PLY produces a ~400MB GLB — unusable on mobile. Decimate first: MeshLab → Quadric Edge Collapse Decimation → target 500K-1M faces (reduces file to 10-20MB). Then convert to GLB. For further compression, run gltfpack with Draco (can reach 2-5MB). Desktop workstations can handle up to 5M triangles in Three.js with LOD.
If vertex colors exist, they're used directly as the visual appearance — no PBR material override. If no vertex colors are present, a default PBR material is assigned (base color #808080, metallic 0.0, roughness 0.5). For photorealistic rendering, import the GLB into Blender, assign PBR materials with texture maps, and re-export.
Custom PLY properties — confidence values, scanner timestamps, intensity channels, custom float attributes — are discarded because glTF 2.0 has no equivalent fields. Geometry (vertices, faces), vertex normals, and vertex colors are fully preserved. If you need to retain custom properties, keep the original PLY alongside the GLB.
GLB is the binary container of glTF 2.0 — same format, single file. glTF uses separate .gltf (JSON) + .bin (geometry) + texture files; GLB packs everything into one file. For web delivery, GLB is almost always better: one HTTP request, no CORS issues with external resources, simpler deployment. File size is identical.

Related Converters

What's Next? Try These Tools

Learn More

More PLY Conversions