Deliver
Export a point cloud (LAS, PLY, CSV, USD, web)
One dialog for every point cloud export - format, subsample, colours, label columns and scalar fields - with a LAS writer that puts the class in the classification byte and every id in an exact 32-bit extra byte.
Every export is Pro, a plain format conversion included. The free edition opens, views and runs every process, and writes no file.
Part of Point cloud classification, Point cloud segmentation, Gaussian splat to floor plan and CAD.

When to use it
When the result leaves N3D: a classified cloud for a GIS, a cloud with height above ground for a forestry model, component ids for a digital twin, a quick web viewer for a client.
Step by step
- Open File › Export point cloud… (or Export… at the foot of the Knowledge pane, which opens it with every listed field ticked).
- Choose the Format: PLY (normals, labels and scalar fields), LAS (the survey standard), CSV (one row per point), USD (a text
.usdastage), Web (one self-contained.htmlviewer, 9 bytes a point, no network access) or Voxels (a MagicaVoxel.vox, see .vox). - Under Points, keep All points or take a uniform subsample of 10 or 1 million.
- Under Label columns, tick what to write: Segment ids, Class ids, Deviation, Instance ids, Primitives (
componentandprimitive_kind) and Baseline classes. - Under Scalar fields, tick the columns the file carried and the ones N3D computed, such as
hagorconfidence. - Press Export as … (the button names the format, for example Export as LAS…). The status reads
Exported n points » path.
What it was measured at
The LAS round trip is checked with laspy: the class fills the 0 to 255 classification byte, ids ride as u32 extra bytes (data type 5) and scalars as f32 (data type 9). LAS 1.2 is written when every class fits in 5 bits, LAS 1.4 when a class exceeds 31 or a coordinate system is present.
Limits, stated
- A class column above 255 is refused for LAS, with the suggestion to use PLY or CSV.
- USD and Web exports have point ceilings and carry colours only; the dialog warns before the write would be refused.
- The coordinate system is written only while the geometry is still the source’s; a layer moved by hand is written without it.
- Point clouds are not written as OBJ; meshes leave as glTF / GLB from their own export, and parametric models as IFC, OBJ or DXF from theirs.
Related questions
What goes into a LAS export?
The class column fills LAS’s classification byte (0 to 255). Segment, instance and component ids are written as exact 32-bit unsigned extra bytes, and computed scalars such as height above ground or deviation as 32-bit floats, so PDAL, laspy and CloudCompare read them back. Intensity, returns, point source and scan angle keep their standard slots. The file is LAS 1.2 unless a class exceeds 31 or a coordinate system is present, in which case it is LAS 1.4.
Which formats can it write?
Point clouds as PLY, LAS and CSV, a USD stage (.usda) or a self-contained web viewer. Meshes and voxels as glTF / GLB, voxels also as MagicaVoxel .vox. House and building models as IFC (Scan to BIM). Drawings as SVG, DXF (R2000) and PDF 1.4. Vectors as GeoJSON and Shapefile. Rasters as GeoTIFF and ESRI ASCII grid. Reports as HTML. Images as PNG or JPEG and flythroughs as MP4. Writing results out is a Pro feature.
Does it keep the coordinate system?
Yes. It is read from LAS GeoTIFF keys, the OGC WKT record and LAS 1.4 extended records, carried into reports, and stamped on a LAS export as long as the geometry is still the source’s. A cloud that was moved by hand is written without it, because the stamp would no longer be true. Vector layers are checked against it and a clash is reported.
What does a paid licence unlock?
Writing out what the program worked out: computed columns (class, segment, confidence, height above ground, deviation) on an export, drawings (DXF, PDF, SVG), terrain rasters, GIS vectors, meshes as glTF, reports, region and zone CSVs, saved images and flythrough videos. Desktop Engine, Science and SDK and the academic licence unlock the same features in the program; Science and SDK adds Neurones 3D Science, the Python research platform. The boundary is enforced in code and tested in both directions.
More in the FAQ.
Related guides
confidence column, and split a powerline corridor into individual trees, spans and poles.
Deliver
Reports
One self-contained HTML document from what the session measured - the as-built review with its per-zone punch list, the volume and how much of it rests on the classification, the measurements you kept - and a provenance block that lets someone else re-derive every number.