Skip to main content

Repair PLY Files Online — Fix Mesh Errors from 3D Scans

Every 3D scan has blind spots.

Last updated Mar 2026

Loading repair tool...

Usually under 5 seconds — depends on mesh complexity.

When to Use PLY Repair

Fix 3D Scanner Output

Artec, Faro, or RealSense scanners export PLY with holes from areas the scanner could not reach. Repair before importing to MeshLab for further processing, or before printing the scanned object.

Clean Photogrammetry Reconstructions

Converted a point cloud to mesh via Poisson reconstruction in CloudCompare or MeshLab? The resulting PLY often has small holes and artifacts at the reconstruction boundary. Repair cleans these up for a watertight surface.

Prepare Scans for Blender Import

Importing PLY scans to Blender for sculpting, retopology, or texture baking? Repair first to avoid topology errors that interfere with sculpting brushes and quad-based retopology tools.

Repair Operations

Hole Filling

Fills gaps left by scanner occlusion. Every 3D scanner has blind spots — the underside of an object on a turntable, deep concavities, or areas obscured by other geometry. Hole filling closes these gaps with new triangles that follow the surrounding surface curvature. New vertices inherit averaged colors from neighboring scan points for visual continuity.

Degenerate Face Removal

Removes zero-area triangles from noisy depth sensor data. Structured-light and time-of-flight scanners occasionally produce triangles with coincident or collinear vertices, especially at scan boundaries or on reflective surfaces. Removing these improves mesh quality for downstream operations like remeshing and smoothing.

Normal Recomputation

Recalculates surface normals for consistent orientation. Surface reconstruction algorithms (Poisson, Ball Pivoting) sometimes produce patches with inconsistent normal directions, causing lighting artifacts when rendering the scan. This operation ensures all normals point outward consistently.

How It Works

Drop your mesh PLY file into the upload area (up to 150MB on desktop, 25MB on mobile). The tool auto-detects binary vs. ASCII PLY format and reads locally.

First, a format check: the tool inspects the PLY header for face definitions. If your file contains only vertex data (a raw point cloud with no "element face" in the header), repair cannot proceed — you'll see a clear message explaining that surface reconstruction is needed first. This is the most common mistake when working with PLY from photogrammetry pipelines that export point clouds by default.

For valid mesh PLY files, the diagnostic scan reports: vertex count, face count, boundary edge loops (holes), degenerate faces, and vertex color channels detected (RGB, RGBA, or none). The color channel report matters because it confirms your scan colors will be preserved through repair.

All three repairs are recommended for scan data: hole filling to close scanner blind spots, degenerate removal to clean noise artifacts, and normal recomputation to fix inconsistencies from surface reconstruction algorithms. Poisson reconstruction in MeshLab and CloudCompare sometimes produces patches where normals flip direction at the reconstruction boundary — normal recomputation fixes these systematically.

The output preserves both ASCII and binary PLY format matching the input. Vertex colors are preserved on existing vertices and blended on new fill vertices. The repaired file is ready for MeshLab, CloudCompare, Blender, or direct conversion to STL for 3D printing.

Limitations

PLY repair addresses surface mesh errors but has limitations with scan-specific issues.

Raw point clouds are not supported. This tool requires triangulated mesh PLY files. Use CloudCompare or MeshLab to reconstruct a surface mesh from point cloud data first.

Self-intersecting geometry from overlapping mesh regions caused by multi-scan registration errors requires manual cleanup in MeshLab.

Non-manifold edges from stitching multiple scan passes create internal walls. This capability is planned for a future update.

For advanced scan processing, use MeshLab's filter pipeline or CloudCompare's mesh processing tools.

Frequently Asked Questions
This tool repairs mesh PLY files only (triangulated surfaces with face definitions). If your PLY is a raw point cloud without faces, you first need to reconstruct a mesh surface. Use CloudCompare's Poisson reconstruction or MeshLab's Ball Pivoting algorithm to generate a triangulated mesh from your point cloud, then export as mesh PLY and repair here.
Yes. PLY vertex colors (per-vertex RGB values) are preserved on all existing vertices. Vertices created by hole filling inherit averaged colors from adjacent vertices, so filled regions blend smoothly with the surrounding scan data rather than appearing as a solid color.
Yes. The repaired PLY is a standard format compatible with MeshLab, CloudCompare, Blender, and other mesh processing tools. After repair, import to your preferred tool for further processing such as remeshing, smoothing, decimation, or texture baking.

You Might Also Need

Step-by-Step Guides