Smooth PLY Files Online — Remove 3D Scan Noise
PLY files from 3D scanners (Artec, Faro, RealSense, Polycam, photogrammetry pipelines) carry sensor noise that shows up as a rough, grainy surface texture.
Last updated Mar 2026
Usually under 5 seconds — depends on mesh size and iterations.
When to Smooth PLY Files
Clean Photogrammetry Output
RealityCapture, Metashape, and COLMAP produce PLY meshes with reconstruction noise. Smoothing removes the grainy texture while preserving color data for textured rendering.
Polish LiDAR Scans
iPhone/iPad LiDAR scans from Polycam or 3d Scanner App have visible noise at close range. A few smoothing iterations produce a clean mesh for 3D printing or web display.
Prepare Scans for Measurement
Industrial scans used for dimensional inspection need clean surfaces. Smoothing reduces noise that would otherwise affect measurement accuracy at contact points.
Pre-process for Poisson Reconstruction
Running Poisson surface reconstruction (MeshLab, Open3D) on noisy PLY data? Pre-smoothing the input vertices produces a cleaner watertight output.
How It Works
PLY (Stanford Triangle Format) is the native output of most 3D scanning pipelines. Scanned PLY meshes almost always need some smoothing because physical sensors introduce noise at every point capture.
This tool uses Taubin’s volume-preserving smoothing algorithm. For each iteration, it computes the average position of each vertex’s neighbors (Laplacian), moves the vertex toward that average (λ step), then immediately moves it slightly back (μ step). The net effect is noise reduction without model shrinkage.
For scanner output: use 3-5 iterations for structured-light scanners (Artec, EinScan) which produce relatively clean data. Use 8-12 iterations for photogrammetry (RealityCapture, Metashape) which tends to be noisier. iPhone LiDAR scans (Polycam, 3d Scanner App) typically need 5-8 iterations.
Vertex colors are preserved through the process since smoothing only changes positions, not per-vertex attributes.