Convert LAZ to XYZ coordinates.

Decompress a LAZ scan and export its coordinates as plain text.

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 LAZ file, or try the synthetic LAZ sample.
  2. After decompression, check the point count. Crop or subsample the imported cloud first if you need fewer output rows.
  3. Click Convert cloud and download the coordinate text file.

Try an example

Try the LAZ sample, which contains 1,000 points. Export once, then select the imported cloud and subsample to 500 points. Select that result and export XYZ again. Compare the row counts and downloaded file sizes; conversion alone keeps the points, while subsampling removes some.

Before you start

Compressed size does not indicate point count. Up to 100 MB and 5,000,000 points are accepted; the point limit still applies after decompression. XYZ text may be larger than the LAZ source. XYZ omits colors, intensity, classification, GPS time, return information, CRS and other metadata. It has no header or unit field.

Does this make my LAZ file smaller?

Not necessarily. LAZ is compressed and XYZ is plain text. Compare the actual result size; crop or subsample a working cloud if you need fewer points.

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

Control the size of a decompressed coordinate export

Budget for points, not just upload bytes

LAZ compression can pack many point records into a small upload. The 100 MB upload limit and 5,000,000-point limit are separate checks. If the source exceeds the point limit, it cannot be imported for cropping here; split or reduce it with a desktop tool first. A successful upload alone does not mean import has succeeded.

Choose the working cloud before exporting

For an accepted file, crop first when you only need a particular region. Subsample when you need coverage of the whole scene with fewer points. Each operation creates a separate result: select that result before converting to XYZ. Exporting the original again will keep its original point count. Inspect small features before deciding that the reduction is acceptable.

Estimate text size from a trial result

XYZ stores readable coordinate strings without LAZ compression. As a rough planning example, 60 bytes per row across 1,000,000 points would require about 60 MB of text. Actual row length depends on coordinate magnitudes, signs and formatting. Measure a downloaded trial result and divide its bytes by its row count for a better estimate; this is not a prediction of processing time.

Choose a response to a large LAZ export
What you needSuggested action
All points in coordinate textAllow for a larger download and keep the original compressed archive
Only one area of the surveyCrop the imported cloud, then export the cropped result
Fewer points across the full sceneSubsample and inspect the retained detail before exporting
A source above the point limitPrepare smaller input files outside this website

Common questions

Does a larger XYZ file mean decompression duplicated points?

File size alone cannot tell you that. Compare the point count of the selected cloud with the number of XYZ rows. Text coordinates often take more bytes than compressed records even when the point count is unchanged.

Which copy should I keep for another editing session?

Keep the original LAZ for its compression and source metadata. Download a PLY working result if you want to upload the reduced cloud here later; XYZ input is not supported. Session files expire, so download these copies before leaving.

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.