Convert LAS to XYZ coordinates.

Export the coordinates in a LAS file as plain X, Y and Z columns.

Point cloud preview

Bring your scan into view

Add a cloud, or try the sample to explore.

Rotate · Zoom · Inspect
Preview uses up to 80,000 points
Points—
File size—
Extent (X / Y / Z)—

How to use this tool

  1. Upload a LAS file, or try the synthetic LAS sample.
  2. Check the imported coordinate bounds against your source data. Keep XYZ selected; this export does not change the coordinate reference system.
  3. Click Convert cloud and download the coordinate text file.

Try an example

Use the LAS sample to check the handoff to a text reader: export its 1,000 points, read three whitespace-separated columns as X, Y and Z, and compare their minimum and maximum values with the imported bounds. Record the source units separately; the text has no unit field.

Before you start

Up to 100 MB and 5,000,000 points are accepted. Scaled LAS coordinates are exported without reprojection or unit conversion. XYZ omits colors, intensity, classification, GPS time, return information, CRS and other metadata. It has no header or unit field.

Are the LAS coordinates converted to another coordinate system?

No. The source scale and offset are applied when reading coordinates, but the coordinate reference system and units are unchanged. Record that context separately.

Files stay in a temporary 2-hour session. Switching tools in this tab keeps your uploaded clouds and results. Read about file privacy.

Check LAS coordinates before handing off the text

Scaled coordinates, not the stored integers

LAS stores coordinate integers with a scale and offset for each axis. The reader applies coordinate = integer × scale + offset. For an illustrative X value of 12345, a scale of 0.01 and an offset of 500000, the coordinate is 500123.45. These numbers explain the calculation; they are not measurements from the sample file.

Compare bounds rather than the first row

Read the downloaded file as three whitespace-separated numeric columns in X, Y, Z order, with no header. For an export without cropping or subsampling, compare the row count and each column’s minimum and maximum with the imported cloud. Bounds avoid relying on point order. Small rounding differences are possible; twelve decimal places in the text do not add measurement accuracy.

Set the reference system in the receiving tool

An easting is not automatically a longitude, and a height is not automatically in metres. The exporter does not reproject coordinates or convert units. Obtain the horizontal reference system, vertical reference and units from your source documentation, then configure the receiving application accordingly. Keep the LAS original: XYZ carries none of that metadata or the point classification.

Checks when a LAS export looks misplaced
SymptomCheck before changing coordinates
Very large X and Y valuesThey may be projected coordinates; confirm the source reference system
The shape is stretched or appears sidewaysCheck column order and axis units in the receiving tool
The height differs from another datasetCheck the source vertical reference and units
The row count is lower than expectedCheck whether a cropped or subsampled result was selected

Common questions

Should I apply the LAS scale and offset to XYZ again?

No. The exported coordinates already include the source scale and offset. Applying them again changes the locations. Configure the destination to read coordinate values, not raw LAS integers.

Can the text tell me which points are ground?

No. This export contains only X, Y and Z, so LAS classification is omitted. Choose LAS to PLY to retain the supported classification property, and use a suitable downstream tool if you need to filter ground points.

Service limits: 100 MB, 5000000 points, one running job, 2-hour sessions. E57: up to 64 scans, stored poses and common RGB/intensity. No registration or cloud-to-cloud distance.