Local model inspection
PLY Viewer Online
Open a PLY file that contains a surface mesh and inspect its geometry in your browser. Vertex colors appear when the file provides supported color properties. This viewer is for meshes with faces; a point-cloud-only PLY requires a different workflow.
Last updated
- Model bytes stay local
- PLY
- Maximum 50 MB total
Works locally · PLY · Maximum 50 MB combined
Select one model and its local BIN, MTL or texture files together.
Drag to rotate. Right-drag or two-finger drag to pan; scroll or pinch to zoom. Keyboard: arrows rotate, Shift + arrows pan, + / − zoom, R resets. Animation starts only when you press Play.
Choose an existing model from your device. This tool does not generate a new 3D asset.
How to open a PLY mesh
Choose a .ply file from your device. The file must contain mesh faces as well as vertices. After it loads, rotate the model to review the complete surface, then zoom into areas with small features, uneven triangles or scan noise.
PLY can describe different kinds of data. A file extension alone does not establish that the file contains a renderable surface. If your file contains only points, create a suitable surface in a reconstruction tool or use a dedicated point-cloud viewer. Changing the extension does not create faces.
- Confirm the PLY export includes a mesh, not only scan points.
- Choose the local .ply file, within the 50 MB limit.
- Compare shaded and wireframe views around detailed areas.
- Keep the source scan or model so you can review changes made during reconstruction.
Understand the data a PLY file contains
A PLY header describes the elements and properties stored in the file. A surface mesh normally provides vertex positions and face indices. It may also provide normals, colors or other properties. This viewer displays the supported geometry and appearance data; it does not interpret every custom field.
ASCII and supported binary PLY exports offer different storage encodings. Encoding and geometry quality are separate choices. A smaller binary file can contain the same dense surface as a much larger text file, so stored size alone does not establish how fast it will render.
View PLY vertex colors without a texture package
Some PLY meshes store a color at each vertex. The renderer interpolates those colors across the surface. This differs from mapping a separate image onto UV coordinates. A colored scan can therefore display without a texture image selection.
If the PLY appears gray, check whether the source actually exported supported color properties. A color visible in a scanning application may come from a separate source or a display setting that was not written into the file. A browser viewer cannot recover missing color data.
Inspect scan surfaces from several angles
A scan-derived mesh can hide missing or noisy regions behind a good front view. Rotate to inspect the underside, narrow recesses and the edge of the captured area. Wireframe can show large triangles that bridge gaps or dense patches that follow surface noise.
The preview helps you identify areas to inspect in the reconstruction application. It does not remove outliers, reconstruct holes or distinguish a desired thin feature from scanning noise. Preserve the original capture and compare any repaired or simplified copy with it.
A PLY mesh and a PLY point cloud need different tools
A point cloud stores samples in space. A mesh connects vertices into faces that form a surface. Both can use a PLY container, but they answer different inspection needs. This viewer expects surface faces and does not render a point-cloud-only capture as though it were a mesh.
If your starting data is a point cloud, choose reconstruction settings in a suitable tool before exporting a surface. Review the new topology and any filled gaps. A reconstructed surface is an interpretation of the capture, so keep that step visible in your asset records.
Check size, units and unsupported fields
The selection limit is 50 MB. Parsed geometry and color buffers can use more memory than the stored file. A smaller inspection mesh is useful on a phone or a device with limited graphics memory. Reduce the source deliberately; a lower file size does not automatically mean that important detail was preserved.
The visible model does not establish real-world units, measurement accuracy or manufacturing suitability. Use the source workflow for calibrated measurements. Custom PLY properties, classification labels and application metadata are not a substitute for the visible surface and are not presented as a full data report here.
Preserve the original PLY when preparing a new export
A PLY header describes the expected element counts, property names and data encoding. Editing those labels by hand does not convert the payload that follows. If the encoding or schema is incompatible, use the source application to create a supported mesh export instead of trying to fix the extension or header text alone.
Preserve the original capture, including its calibration information and any attributes required by your project. A display-oriented export may omit custom fields while keeping the visible surface. The fact that the mesh opens here does not establish that every original measurement or classification attribute survived.
For a review handoff, record whether the file is a raw scan mesh, a cleaned surface or a reconstructed result. Those steps can change holes, boundaries and small features. Keeping the versions separate makes it easier to explain why a region differs from the captured object.
Compare color detail with surface detail
Vertex colors and geometry have different jobs. A dark mark can be a color change on a smooth surface, while a small ridge can be a geometric feature without a strong color change. Inspect the asset in more than one material view before deciding which kind of detail you are seeing.
Vertex color detail is tied to the available vertices. A very coarse surface can produce broad interpolated color regions even when the original capture had more visual detail. Increasing display zoom cannot recreate omitted samples. Use the source scan and reconstruction workflow when you need a different balance of surface density and appearance.
If you later simplify or convert the mesh, compare both the silhouette and color transitions. Preserving a rough outline does not necessarily preserve a small painted feature. Keep the original PLY as the reference for any change rather than treating the newest export as automatically more accurate.
Choose the next format for the receiving application
Keep PLY when a workflow needs its mesh or vertex color representation. If the next tool needs a different format, export it from an application that explicitly supports the data you need to preserve. Check whether vertex colors survive that handoff before discarding the source.
Use the general viewer to compare a GLB, STL or OBJ export of the same asset. A textured GLB, a gray STL and a vertex-colored PLY can carry different appearances even when their surfaces began from the same model.
Viewer questions
Can this PLY viewer open a point cloud?
No. This page opens PLY meshes that contain surface faces. Use a dedicated point-cloud viewer or reconstruct a mesh in a suitable application for point-only data.
Does it show PLY vertex colors?
Supported vertex color properties are displayed when the file contains them. The viewer cannot recreate colors omitted during export.
Do I need separate image textures for PLY?
Vertex colors are stored in the PLY itself. This page does not provide a separate texture-package workflow for PLY. Use a suitable scene format when that workflow is required.
Can I inspect a scanned object?
Yes, if the export is a supported PLY surface mesh within the file limit. Review incomplete areas and reconstruction artifacts separately in the source workflow.
Does the preview prove the scan is dimensionally accurate?
No. Camera framing is a viewing aid. Calibration, unit interpretation and measurement accuracy require review in the capture and measurement workflow.
Does MeshCrate upload my selected files?
The tool reads selected model files and their selected dependencies in your browser. It does not upload those file bytes. The website still loads application code, fonts and public assets, and it can send usage events. Local file processing does not mean the whole website is offline. Remove the file or close the tab when you finish.
What is the file size limit?
The total selected model and dependency files must be 50 MB or less. A small file can still require substantial browser memory after parsing. If loading fails, close other demanding tabs or export a smaller model. Archives and remote model URLs are not accepted.