The online PLY file viewer built for photogrammetry and LiDAR output — not just pretty meshes. Drop a .ply file and we auto-detect ASCII vs binary encoding, render vertex colors on the first frame, and fall back to point-cloud rendering when no faces are declared. Up to 200MB, fully in-browser, no account.
Drop PLY file to preview
or click to choose a file
Max file size: 200MB
Most online PLY viewers assume every .ply file contains a mesh and silently fail on the output of real photogrammetry and LiDAR pipelines, which often export points only. Our viewer parses the PLY header first: if no `element face` is declared (as in Meshroom's `sparsePointCloud.ply`, COLMAP's `fused.ply`, or the raw dense cloud from Agisoft Metashape), we render with `gl.POINTS` using an adaptive point size so the scan is actually navigable. When faces exist, we switch to triangle-mesh rendering. Either way, vertex colors (`uchar red/green/blue/alpha`), surface normals (`nx ny nz`), and confidence/quality floats are passed straight to the GPU — no tone-mapping, no color-space reinterpretation, no silent downcasting. The color you captured on-site is the color you see on screen.
Every PLY exporter writes slightly differently — a trailing newline here, a comment line there, header properties in a different order, big-endian on older Linux boxes. Our PLY parser has been iterated against output from 14 pipelines in active use: Meshroom (sparse cloud and textured mesh), Agisoft Metashape, RealityCapture (including its comment-heavy headers), Polycam (iOS LiDAR and photo-scan modes), COLMAP, Artec Studio, Revopoint POP/Range, Luma AI splat-to-PLY exports, Open3D `write_point_cloud`, PCL (Point Cloud Library) `io::savePLYFile`, Blender's PLY add-on, CloudCompare exports, MeshLab exports, and plain-text ASCII from academic research code. Drop a .ply from any of them and it loads without preprocessing.
Open any .ply 3D scan, photogrammetry reconstruction, or point cloud in seconds — no software installation, no account, completely free.
Drag and drop your .ply file onto the viewer, or click to browse. We auto-detect the encoding from the PLY header line (`format ascii 1.0`, `format binary_little_endian 1.0`, or `format binary_big_endian 1.0`) — no manual conversion required. Files up to 200MB are supported, which covers most iPhone LiDAR scans from Polycam, dense photogrammetry reconstructions from Meshroom, and research-grade point clouds.
The viewer renders in WebGL the moment parsing finishes. Rotate, zoom, and pan to inspect mesh geometry or navigate the point cloud. If your PLY contains vertex colors from a photogrammetry capture, they appear on the first frame automatically — no toggle, no settings menu. The stats overlay shows vertex count, face count, and whether vertex colors/normals were detected, so you can catch a broken export at a glance.
Once scan coverage, color data, and mesh integrity look right, move on to post-processing: clean in MeshLab, register in CloudCompare, retopologize in Blender, or convert to STL for 3D printing. Not happy with the scan? Swap in another .ply and compare in seconds, or one-click switch to another format viewer without re-uploading elsewhere.
MeshLab and CloudCompare are powerful desktop tools — but heavy to launch just to check if a scan came out right. Generic online viewers rarely handle point-only PLYs or preserve vertex colors correctly. This viewer closes the gap.
Most free online PLY viewers cap between 50 and 100MB and degrade to a downsampled preview once you cross the line. We load the full 200MB file into browser memory and render every vertex. That's enough for a typical iPhone Pro LiDAR room scan (~40–120MB), a Meshroom textured reconstruction of a statue (~80–160MB), or a medium-density Velodyne LiDAR frame sequence exported as a single PLY.
When your PLY has no faces (common for raw photogrammetry, LiDAR sweeps, Gaussian splat exports, and academic datasets), we render points directly with depth-sorted `gl.POINTS` and a screen-space size that scales with zoom so the cloud stays readable at any distance. Competitors either refuse to open point-only PLYs or display an empty canvas — we've benchmarked against five alternatives and this is the single biggest difference for photogrammetry workflows.
Binary PLY files come in two flavors (`binary_little_endian` and `binary_big_endian`); ASCII PLY is the debuggable but slower variant. Some tools (older Linux-authored academic code, specific scanner firmwares) still emit big-endian binary, which many viewers can't parse. We detect the format from the header and decode accordingly — ASCII, little-endian, or big-endian — without asking you to re-export.
Your .ply file never leaves the browser tab. That matters for heritage-preservation teams scanning protected artifacts, surveyors under NDA, and product studios handling pre-release 3D captures. WebGL parses and renders locally; our servers see nothing but a normal page view.
PLY is a working format, not a delivery format. The people who open .ply files most often are validating a capture or a reconstruction — not showing off a finished model. This viewer is built for that validation loop.
PLY is the default intermediate output of Meshroom, RealityCapture, Agisoft Metashape, Polycam (photo-scan mode), and COLMAP. After a 20–90 minute reconstruction finishes, you need to know immediately whether coverage, color, and mesh density are acceptable before committing to the next processing pass. Drop the .ply here to check — faster than launching MeshLab, easier than scripting Open3D.
Velodyne, Ouster, Livox, and iPhone Pro LiDAR pipelines commonly export PLY for intermediate review. Instead of booting CloudCompare or Potree just to confirm a frame captured correctly, drop the .ply to inspect point density, overall scan coverage, and whether colorization from the RGB camera aligned with the LiDAR returns.
PLY was created at Stanford in 1994 (Greg Turk, Ben Trumbore) precisely for research 3D data — from the Stanford Bunny to modern cultural-heritage and medical-imaging datasets. Load a dataset straight from a .ply in your browser, share a viewer link with a collaborator who doesn't have MeshLab installed, and skip the usual "what software do I need to open this?" back-and-forth.
Scanned a real object and got a .ply back? Before wasting slicer time, check the mesh here: is it watertight-looking, are there obvious holes, is it oriented correctly? PLY → STL conversion is easy once you know the scan is usable. A two-minute visual check at this stage routinely saves hours of failed prints.
Scan-to-asset pipelines (environments, props, character references) increasingly pass through PLY before retopology in Blender, ZBrush, or Houdini. Use this viewer to verify vertex color bake and mesh quality the instant the scan finishes — without interrupting your 3D app workflow.
Museum digitization, archaeological site documentation, and conservation scanning produce PLY files that need review by stakeholders who rarely have specialized 3D software. A browser-only PLY viewer means you can send a curator or a grant reviewer a link and let them inspect the scan themselves — no training call required.
Photogrammetrists, LiDAR engineers, and heritage researchers use this viewer as the first stop after every reconstruction — to catch broken exports before post-processing begins.
I run ~40 Meshroom reconstructions a month for architectural documentation. I used to open each `sparsePointCloud.ply` in MeshLab just to confirm the cloud was dense enough before starting the dense step. Now I drop it in this viewer — render is instant, point size auto-adjusts, colors come through correctly. Probably saves me two hours a week.
Thomas Richter, Photogrammetry Specialist, Heritage Documentation
For the museum digitization project I coordinate, most of my reviewers are archaeologists, not 3D technicians. Asking them to install MeshLab was a non-starter. A browser-only PLY viewer that just works — and keeps the scan off any server — has been the single biggest unblocker for our review workflow this year.
Elena Vasquez, Digital Heritage Researcher
The 200MB limit is the first thing I tested and it's real — I loaded a 187MB colorized Velodyne PLY and it rendered in under 5 seconds on my MacBook. Most free viewers just reject files that size. The fact that it also handles binary big-endian without complaint is a bonus — we still get those occasionally from older survey rigs.
James Nakamura, LiDAR Survey Engineer
Answers to the specific PLY questions that generic 3D viewer pages don't cover — point clouds, endianness, vertex color debugging, and exporter quirks.
Drag, drop, and inspect — in-browser, fully client-side, no signup. ASCII or binary, mesh or point cloud, 2MB phone scan or 180MB photogrammetry reconstruction. If your .ply has vertex colors, you'll see them on the first frame.
Used by photogrammetry specialists, LiDAR engineers, heritage researchers, and 3D scanning teams worldwide.