Skip to content

Convert PLY to TXT

Convert PLY point clouds or mesh vertices into a documented TXT coordinate table.

Convert PLY files online

We don’t have a dedicated online converter for PLY to TXT yet, but you can convert PLY files online to these and more formats:

Want to convert PLY to TXT?

Let us know. We pick the conversions to add next by how many people ask for them.

How to convert ply to txt file

A scanner viewer, measurement program, or custom script may require a plain coordinate table instead of a PLY model. Converting it creates an application-specific TXT file for inspection, editing, sharing, or import into software that accepts delimited text.

What the PLY format is

PLY, also called the Polygon File Format or Stanford Triangle Format, stores 3D point clouds and polygon meshes. Its header defines elements such as vertex and face, followed by properties including x, y, z, colors, normals, texture coordinates, and polygon vertex lists.

A PLY file can use ASCII, binary little-endian, or binary big-endian encoding. 3D scanners, photogrammetry software, MeshLab, CloudCompare, Blender, and research applications use PLY for scanned objects, reconstructed environments, and point-cloud datasets.

What the TXT format is

.txt is a generic plain-text extension, not a defined 3D interchange format. In 3D workflows, it usually contains one point per line in a schema such as x y z, with optional color, normal, intensity, or scalar-value columns.

Text files are easy to inspect, edit, generate, archive, and process with Python, MATLAB, spreadsheets, and command-line tools. They are normally larger and slower to process than binary PLY. A basic coordinate table does not preserve faces, materials, textures, comments, units, or other PLY metadata.

Convert with CloudCompare

  1. Install CloudCompare from its official website and open the file with File → Open.
  2. Select the point-cloud entity in the DB tree. If the PLY contains a mesh and you need a point table, export its vertices or use Edit → Mesh → Sample points when sampled points are more appropriate than the original vertices.
  3. Use File → Save As and select CloudCompare's ASCII cloud output. Enter a .txt filename only if the save dialog permits that extension; the output type, not the extension, determines the data format.
  4. In the ASCII export options, select the delimiter and the fields to write, such as coordinates, colors, normals, or scalar fields. Add a header only if the receiving program accepts column names.
  5. Open the result in a text editor and verify the delimiter, column order, decimal notation, point count, and coordinate units.

CloudCompare is suitable for point clouds because it reads ASCII and binary PLY and exposes attributes during ASCII export. A generic cloud export normally discards polygon topology. Preserve the mesh separately if face connectivity is needed.

Convert with Python

Use the plyfile package when the output must have a repeatable column layout. It reads the standard ASCII and binary PLY encodings. The following script writes all scalar properties from the vertex element as tab-separated columns and ignores list-valued properties.

python -m pip install plyfile
python ply_to_txt.py model.ply model.txt

Save this as ply_to_txt.py:

from plyfile import PlyData
import sys

ply = PlyData.read(sys.argv[1])
vertex = ply["vertex"]
names = [
    name for name in vertex.data.dtype.names
    if vertex.data.dtype[name].shape == ()
]

with open(sys.argv[2], "w", encoding="utf-8", newline="") as output:
    output.write("\t".join(names) + "\n")
    for row in vertex.data:
        values = []
        for name in names:
            value = row[name]
            values.append(repr(value.item()) if hasattr(value, "item") else str(value))
        output.write("\t".join(values) + "\n")

The result may contain columns such as x, y, z, red, green, blue, nx, ny, and nz. This script exports vertices only. A mesh requiring reconstruction must use a documented second section or a separate face file containing each face's vertex indices.

Compatibility and quality limits

  • Define the receiving schema before conversion: delimiter, header presence, column order, decimal separator, coordinate units, and whether indices start at zero or one.
  • ASCII output can increase file size substantially and may expose or round numeric precision. Retain enough significant digits for measurement, registration, and scientific processing.
  • PLY color properties may use 8-bit values from 0–255 or another numeric type. Confirm whether the destination expects RGB values from 0–255 or normalized values from 0–1.
  • PLY files can contain face lists, comments, custom elements, camera information, materials, and other properties that a coordinate export omits. Keep the original PLY as the master copy.
  • There is no universal PLY-to-TXT conversion because TXT has no standard 3D schema. Online services should be used only when the provider documents the exact output columns and supports the required PLY variant; many generic converters either do not support this conversion or produce unusable plain text. Local CloudCompare or a script is safer for sensitive scans and controlled output.

PLY vs TXT: format comparison

How the PLY and TXT formats compare on the properties that matter most for this conversion.

Comparison of the PLY and TXT file formats
Property .PLY Polygon File Format .TXT Plain Text File
Open standard Yes Yes
Compression Uncompressed Uncompressed
Typical file size Medium Very small
Opens in a web browser No Yes, natively
Further editing Easy Easy
Metadata support Basic None
Plain-text readable Yes Yes
Best used for Data exchange Data exchange
Introduced 1994 —
Developer Stanford University —
MIME type application/octet-stream text/plain

Information about file extensions and file types is provided by File-Extensions.org

Already downloaded

This file has already been downloaded. For your privacy it was deleted from our server right after the download, so it cannot be downloaded again. To get it once more, convert the file again.