Convert PLY to PTS

Surveying and laser-scanning applications sometimes require the ASCII .pts point-cloud format, while scanners and 3D tools commonly produce .ply. Converting lets those applications read the coordinates and supported point attributes, but it does not preserve mesh topology.

What the PLY format is

PLY, also called the Polygon File Format or Stanford Triangle Format, stores 3D vertices and may store polygon faces, colors, normals, texture coordinates, and other per-vertex or per-face properties. 3D scanners, photogrammetry software, mesh editors, and research tools use it; Blender, MeshLab, CloudCompare, and many scanning applications can open it.

The header identifies whether the file is ASCII or binary and lists its properties. A PLY containing only vertices is a point cloud. A PLY containing faces is a polygon mesh, although it may also contain a separate or implicit point set.

What the PTS format is

In 3D scanning, PTS is a text-based point-cloud format used by surveying, terrestrial laser-scanning, and point-cloud processing software. A common PTS file starts with the number of points, followed by one row per point containing X Y Z and often intensity plus red, green, and blue values. PTS is not perfectly uniform: column order, optional attributes, and header conventions vary between applications.

Plain text makes PTS easy to inspect and import into specialist software, but it is much larger and slower to read than binary point-cloud formats. PTS stores points, not polygon faces, so it is appropriate for scan data, registration, measurement, and visualization rather than direct mesh editing.

How to perform the conversion

CloudCompare is the most practical desktop option for this conversion. It is available for Windows, macOS, and Linux from the official CloudCompare project.

1. Open CloudCompare and choose File → Open, then select the .ply file.
2. Accept the detected PLY properties in the import dialog. Check that the expected coordinates, colors, and intensity field are present.
3. Select the point-cloud entity in the DB Tree. If the PLY contains a mesh, do not assume that saving it as PTS will retain its faces.
4. For a mesh, create a point cloud first with CloudCompare's mesh sampling operation. Sample density determines how accurately the output represents the surfaces; exporting only mesh vertices does not represent the faces between them.
5. Choose File → Save or File → Save As, select PTS as the output format, and review the export options.
6. Enable color and intensity only when the receiving application supports those fields and expects the same column order. Save the file, then reopen it in the target application for validation.

CloudCompare can also process repeatable conversions from the command line. A typical command is:

CloudCompare -O input.ply -C_EXPORT_FMT PTS -SAVE_CLOUDS FILE

Command-line options and supported exporters vary by release, so verify them with the installed version's help output. Use the graphical workflow when the PLY contains multiple entities or unusual properties.

MeshLab is another desktop option for inspecting PLY data and may provide PTS export in some versions, but its available formats and attribute handling vary. Confirm the exported column structure before using it in production.

Online conversion options

There is no broadly standardized online PLY-to-PTS service that can be relied on for arbitrary point-cloud attributes. Many general 3D conversion websites support PLY but not PTS, or export only XYZ coordinates without clearly documenting intensity and RGB handling. Use a browser service only when its current format list explicitly supports PTS and its output schema matches the receiving software; do not upload confidential scans or survey data. CloudCompare is preferable for predictable results and large files.

Quality and compatibility limits

• Faces are discarded: PTS has no standard polygon-face section. A mesh-to-cloud conversion retains existing vertices or sampled surface points, not the original surfaces and topology.
• Coordinates are normally unchanged: CloudCompare generally preserves the numeric coordinates and does not automatically convert units or coordinate systems. PTS usually carries no dependable CRS metadata, so confirm units, origin, and georeferencing separately.
• Attributes are not guaranteed: XYZ is the essential content. Intensity, RGB, normals, classification, scanner metadata, and custom PLY properties may be omitted, reordered, or interpreted differently by the importer.
• Text can greatly increase file size: A PTS exported from a binary PLY may be several times larger and slower to transfer or load. Retain the original PLY and use cropping, subsampling, or a binary point-cloud format when the target software permits it.
• Check the output schema: Open a copy of the exported PTS in a text editor. Confirm that the first line contains the expected point count and that subsequent rows contain the expected number and order of numeric fields.
• Check empty and malformed data: Remove invalid coordinates and confirm that the point count matches the number of data rows if the target program rejects incomplete files.