PLY File Viewer Online — Free Stanford Format Viewer

3D Scan Output Without MeshLab

PLY (Polygon File Format, also called Stanford Triangle Format) is the standard output of consumer and professional 3D scanners (Artec, Polycam, Revopoint, Einstar) and photogrammetry tools (Meshroom, RealityCapture, Metashape). The format was developed at Stanford in the mid-1990s and remains popular because it natively supports per-vertex color — critical for scan data. MakerSuite 3D parses both ASCII and binary PLY in your browser, so you can inspect scan output without installing MeshLab or CloudCompare.

PLY Format Internals

PLY has an ASCII header that declares the data layout, followed by either ASCII or binary records. The header lists element types (vertex, face) and properties (x, y, z, nx, ny, nz, red, green, blue, alpha, s, t). The data section follows the declared schema exactly. ASCII PLY is human-readable but slow to parse; binary PLY (little or big endian) is the production choice for large scans. The header is always ASCII regardless, so a JavaScript parser can read it first to decide how to handle the data section.

What the Viewer Handles

• Mesh PLY — vertices + faces render as a closed mesh with per-vertex colors if present in the scan data.
• Point cloud PLY — vertices-only files render as a point cloud; useful for raw scanner output before meshing.
• Per-vertex color — RGB attributes preserved and rendered, so colored scans (Polycam, Revopoint) show with their captured texture.
• Per-vertex normal — if normals are stored, they're used for lighting; otherwise computed from face geometry.
• Binary parsing — both little-endian and big-endian binary PLY decode correctly using the header's declared format.
• Large file handling — multi-million-vertex scans render via WebGL with level-of-detail rendering for smooth interaction.

How to View PLY in Five Steps

1. Open pcbviewer.app — drop your .ply file on MakerSuite 3D's canvas. Header parses immediately; data section reads asynchronously for large files.
2. For point cloud files (vertex-only), enable the Point Cloud rendering mode. Sphere splatting and color-by-height options help interpret raw scan data.
3. For mesh files, use orbit/pan/zoom to inspect the model. Per-vertex colors render automatically if present in the scan.
4. Use measurement tools to confirm scan scale. Bounding box dimensions appear in the inspector panel — useful for verifying scanner mm vs cm output.
5. For mesh reconstruction from point clouds, export to MeshLab and run Filters > Remeshing > Surface Reconstruction: Poisson. Re-import the meshed PLY into MakerSuite 3D to verify the result.

Why PLY Is Still Standard for Scans

PLY's per-vertex color support is the killer feature for scan data. STL has no color, OBJ uses material files (per-face, not per-vertex), glTF supports vertex colors but isn't the scanner industry default. Until a scanner format with both per-vertex color and per-vertex confidence/intensity becomes standard, PLY remains the natural export. Stanford's open spec and 30 years of universal tooling means every CAD, viz, and graphics tool can read it — vendor lock-in isn't a risk.

When PLY Shows Up in Your Workflow

• 3D scanner export — Artec, Polycam, Revopoint, Einstar all default to PLY for colored mesh output
• Photogrammetry result — Meshroom, RealityCapture, Metashape produce PLY as the canonical mesh+color result
• Reverse engineering — scan a physical part to PLY, then mesh and convert to STEP for parametric CAD modeling
• Cultural heritage — museum and archaeological 3D documentation widely uses PLY for color-faithful captures
• Academic graphics — textbook examples (Stanford Bunny, Dragon, Buddha) ship as PLY by default

Browser-Side Parsing, No Upload

3D scan data often represents proprietary parts, sensitive cultural heritage, or pre-production prototypes. MakerSuite 3D's PLY viewer parses files entirely in your browser using three.js's PLYLoader — no server, no upload, no cached copy. Geometry, color attributes, and metadata all stay on your machine. Safe for NDA scans, museum documentation, and IP-sensitive reverse engineering.