LAS Point Cloud Export
LocalExport LAS point clouds to PLY, OBJ, CSV, XYZ or JSON in your browser — no upload, no install. PLY/CSV/JSON keep intensity, classification and RGB. Pro feature.
Drag files here, or click to browse
Supports LAS, CSV, XYZ, TXT
Choose fileLarge files show progress while parsing and serializing (both directions) and can be cancelled anytime — the tab no longer freezes.
.las: export to five formats (uncompressed only) · CSV/XYZ/TXT: packed back to LAS
Exports carry no CRS metadata — coordinates are real-world values; assign the CRS downstream.
What is it? LAS Point Cloud Export converts uncompressed LAS point clouds to PLY, OBJ, CSV, XYZ or JSON — locally in your browser. PLY/CSV/JSON keep intensity and classification (plus RGB when present); OBJ/XYZ are coordinates-only. JSON exports carry the attributes and are larger than the old coordinates-only output. It also packs CSV/XYZ/TXT coordinate lists back into LAS 1.1. Pro feature.
TL;DR: Export LAS points to PLY, OBJ, CSV, XYZ or JSON locally in your browser — no upload — and pack CSV/XYZ/TXT lists back into LAS 1.1.
How to use
- Pick an output format (PLY by default).
- Drop an uncompressed .las file — parsing and serialization show progress and can be cancelled anytime; the conversion still downloads automatically when done.
- Find the converted file in your browser downloads; reverse direction: drop CSV/XYZ/TXT (x,y,z[,intensity,class]) to pack a LAS 1.1 — large lists parse and write with progress and can be cancelled too.
FAQ
Is it local?
Yes, conversion runs in your browser.
Is it free?
No — LAS Point Cloud Export is a Pro feature; on the Free plan this page shows an upgrade prompt.
What happens with very large clouds?
Clouds above ~4 million points are auto-sampled on export to stay within browser memory — the done message shows the exported point count. Use the cloud Filter Point Cloud tool for full-size processing.
Which output format should I export to?
PLY if the next step is MeshLab, CloudCompare or another scan tool — it carries intensity, classification and RGB. CSV if you need columns in Excel, QGIS or scripts. JSON for per-point attributes in code. XYZ for a lightweight text cloud, and OBJ when a 3D app only needs point positions — both are coordinates-only.
Do the exports keep intensity, classification and RGB?
PLY, CSV and JSON keep intensity and classification, and include RGB when the source file carries it. OBJ and XYZ export coordinates only — that is a limit of the formats, not a setting.
Can I pack CSV or XYZ text points back into LAS?
Yes — drop a CSV, XYZ or TXT list of x,y,z[,intensity,class] rows and it is packed into an LAS 1.1 file. Coordinates are written as-is; no CRS is assigned, so set it in your downstream software.
Is the coordinate system (CRS) preserved?
No. Exports contain real-world coordinates but no CRS metadata — PLY, OBJ, XYZ and JSON have no CRS fields at all. Assign the coordinate system in QGIS, CloudCompare or your GIS after export.
What about compressed LAZ files?
Only uncompressed LAS is parsed here. Decompress LAZ to LAS first (for example with laszip or your scanner software), then drop the .las file in.
Examples
- Drop in a .las → pick PLY/OBJ/CSV/XYZ/JSON → downloads automatically; drop CSV/XYZ/TXT to pack a .las back
Supported formats
Limitations
- Uncompressed LAS only (use LAZ tools for compressed).
- Clouds above ~4 million points are auto-sampled on export — the done message reports the exported count.
- OBJ/XYZ exports are coordinates-only; PLY/CSV/JSON keep intensity/classification (RGB when present) — JSON files are larger since they carry the attributes.
- Exports carry no CRS metadata — coordinates are real-world values; assign the CRS downstream.
- Runs locally in your browser; nothing is uploaded.
- Large clouds are memory-bound.
Privacy
Privacy first: this tool runs entirely in your browser — your input and files never leave your device, and everything is cleared when you close the page.