Point cloud file formats fall into two groups: open formats that most software can read, such as E57, LAS and PLY, and native formats tied to one scanner maker or software house, such as FARO’s FLS or Autodesk’s RCP. The format you receive decides which programs can open your survey, whether the scan positions and panoramic images come with it, and whether you can take the data to another company later.
Below, each of the main point cloud file formats gets a short summary: where it’s used, its pros and cons, and anything worth knowing before you ask for it.
What file format do 3D laser scanners use?
Most scanners record in their maker’s own format, and the registration software then exports the finished point cloud in open or software formats. FARO scans are stored as FLS files, Trimble X7 data comes out of Trimble Perspective as a TDX project, and Leica’s Cyclone REGISTER 360 publishes LGS files.
We scan with a Trimble X7, register in Trimble Perspective and RealWorks, and also work with FARO and Leica data in SCENE and Cyclone REGISTER 360. Clients rarely need the native data on its own. They need a registered export their own software can read, which is where the open point cloud file formats below come in.
Open point cloud file formats
E57 (.e57)
Of the open point cloud file formats, E57 is the one built for exchange, defined by ASTM standard E2807. One E57 file can hold the points with their colour and intensity, the panoramic images, and each scan’s registration.
- Best for: handing over and archiving a registered survey, and moving data between different makers’ software.
- Pros: open and fully documented, and read or written by Autodesk ReCap, Leica Cyclone 3DR, Trimble Perspective and RIEGL RiSCAN PRO.
- Cons: AutoCAD, Plant 3D and Revit can’t attach it directly, so it’s converted from E57 to RCP in Autodesk ReCap first.
- Worth knowing: exports come either structured, with each scan kept as its own grid, or as one merged cloud, and Trimble Perspective, for example, offers both. ReCap’s RealView only works with structured scans, so ask for gridded E57 if you want it.
LAS (.las)
LAS is the ASPRS standard format for lidar data, widely used in mapping and GIS. Each point carries attributes such as intensity, return number, classification and GPS time, with RGB colour in some point formats.
- Best for: GIS, mapping, terrain models and lidar workflows.
- Pros: open and widely supported. Coordinates are stored as whole numbers with a scale and offset, so precision is fixed: a scale of 0.001 keeps millimetres.
- Cons: no panoramic images, and exports usually arrive as one merged cloud. LAS 1.2 tops out at about 4.2 billion points per file, so large projects need LAS 1.4.
- Worth knowing: the .las extension is also used by the Log ASCII Standard for well log data, maintained by the Canadian Well Logging Society. On oil and gas jobs, check which kind of LAS file you’ve been sent.
LAZ (.laz)
LAZ is LAS compressed with LASzip, an open source library created by Martin Isenburg. The compression is lossless: a LAZ file is typically 7 to 20% of the size of the original LAS and decompresses to a bitwise identical copy.
- Best for: storing and sending large lidar datasets.
- Pros: far smaller than LAS with nothing lost, and free to use under an Apache 2.0 licence.
- Cons: the same limits as LAS, and every program in your chain must read LAZ, or you decompress it back to LAS first.
- Worth knowing: if a LAS delivery is too big to send, ask for LAZ rather than a thinned cloud, and you keep every point.
PLY (.ply)
PLY, the Polygon File Format (also called the Stanford Triangle Format), stores vertices and faces, so one PLY file can hold a point cloud or a mesh, in plain text or binary.
- Best for: meshes, and passing data to 3D and visualisation software.
- Pros: simple, flexible and widely supported, including by CloudCompare and Cyclone 3DR.
- Cons: no standard fields for scan positions, panoramic images or a coordinate system.
- Worth knowing: PLY allows coordinates to be saved as 4 byte floats, which costs accuracy on large National Grid coordinates. At an easting of 500,000 m a 4 byte float can only step in increments of about 31 mm, so check the file was written in double precision or around a local origin.
PTS (.pts)
PTS is one of the simplest point cloud file formats, a plain text format that came from Leica. The first line gives the number of points, then each line lists X, Y, Z, intensity and RGB colour.
- Best for: moving a merged cloud into software that won’t read the binary formats.
- Pros: readable by people and by almost any program.
- Cons: no scan positions or images, and plain text files are much larger and slower to load than binary ones.
- Worth knowing: Autodesk ReCap can export a whole project as one PTS file or E57 file for people who can’t open RCP files.
PTX (.ptx)
PTX is Leica’s other text format, and it keeps each scan separate. Every scan starts with a header holding its grid size, the scanner position and a transformation matrix, followed by its points.
- Best for: passing registered scans between programs when E57 isn’t an option.
- Pros: keeps each scan as its own grid with its registration, in an open, readable format.
- Cons: very large files that can be slow to import.
- Worth knowing: Trimble Perspective writes one PTX file per scan, so expect a folder of files rather than one.
XYZ, TXT and CSV
The simplest point cloud file formats are plain text columns of coordinates, sometimes with intensity or colour.
- Best for: small extracts, survey points and quick checks.
- Pros: anything can read them.
- Cons: no fixed column order, no header and no scan positions, so the software has to work out the layout. Cyclone 3DR, for example, detects the columns and lets you correct them.
- Worth knowing: fine for a section through a tank, but a last resort for a full survey.
Software point cloud file formats: RCP, RCS and POD
Some point cloud file formats belong to the design software rather than the scanner, and they’re usually the ones your designers will actually open.
RCP and RCS (.rcp, .rcs)
RCP and RCS are Autodesk’s indexed formats, created by Autodesk ReCap. An RCS file holds the points from one scan position or one unified cloud, and an RCP file is the project that collects a set of RCS files.
- Best for: AutoCAD, Plant 3D and Revit.
- Pros: indexed for display in Autodesk software, and the only two formats Revit’s point cloud link accepts.
- Cons: Autodesk only. To share outside Autodesk software, export E57 or PTS from ReCap.
- Worth knowing: the RCP doesn’t contain the scans. Autodesk says the RCS files must be available, so send the .rcp on its own and there is nothing to load. Always send the folder of RCS files with it.
POD (.pod)
POD is the Bentley Pointools format, used as the single point cloud format across MicroStation and the Bentley products built on it.
- Best for: design teams working in Bentley software.
- Pros: one format across Bentley’s tools, so there’s no repeated conversion.
- Cons: of little use outside Bentley software.
- Worth knowing: Trimble Perspective warns that a POD export can take several minutes per scan, so allow time on large projects.
Native point cloud file formats from scanner makers
These point cloud file formats are the ones each manufacturer’s scanners and software work in. They hold the fullest record of a survey, but you need that maker’s software, or a program that supports it, to open them.
FARO: .fls and .lsproj
FARO scans are stored as FLS files and organised in a FARO SCENE project (.lsproj). Older versions of SCENE also used .fws files. Since SCENE 5.0, the registration is kept separate from the FLS files, so a loose set of FLS files doesn’t carry the registration unless you export copies with it saved in.
Trimble: .tdx and .tzf
Trimble Perspective, the field software for the X7, exports a TDX (Trimble Data eXchange) project holding the stations, registration, panoramas and measurements, with one zipped TZF scan file per scan. TDX goes straight into Trimble RealWorks and Trimble Business Center. For anyone else, Perspective exports E57, PTX, LAS, POD and RCP.
Leica: .lgs and .lgsx
Leica Cyclone REGISTER 360 publishes a whole project as one LGS file, with the point cloud, panoramas, setups and measurements, and it can be password protected. LGS opens in Leica’s own tools, including Cyclone, TruView Desktop and the CloudWorx plugins, and recent versions of REGISTER 360 PLUS also publish LGSx. If an LGS password is lost it can’t be recovered, and the project has to be published again.
RIEGL: .rxp and .rdbx
RIEGL VZ series scanners produce RXP scan data, and RiSCAN PRO keeps point clouds in its RDB 2 database format (.rdbx). RiSCAN PRO exports E57 with registration and images, as well as LAS, LAZ, PTS, PTX and POD.
Z+F: .zfs
Zoller + Fröhlich scanners and LaserControl software use ZFS, a binary scan format that supports compressed point data. LaserControl can export to PTS and ASCII text.
Topcon: .cl3 and .clr
Topcon ScanMaster works with CL3 and CLR files. Topcon describes CL3 as storing the scan details, such as date, time, temperature, angle ranges and the instrument model, alongside the point list.
Which point cloud file formats should you ask for?
Ask for the point cloud file formats your own software reads, plus an open E57 copy and the raw native data. Your team can start work straight away, and anyone can pick the data up later.
- AutoCAD, Plant 3D and Revit: RCP with its folder of RCS files. Anything else has to be indexed into those formats in ReCap first.
- MicroStation and other Bentley software: POD.
- GIS and mapping: LAS, or LAZ for big datasets.
- Handover and archive: structured E57, plus the native project from the scanner software.
For our own 3D process models, the cloud goes into Plant 3D as RCP and RCS files, because Plant 3D runs on AutoCAD, which only attaches those two formats.
Whichever point cloud file formats you choose, make sure you own the data. We took on a client whose previous surveyor handed over a 3D model of government plant rooms but kept the registered point cloud. That left the client unable to commission a different deliverable or get a second opinion without scanning again. Our guide to what drives 3D laser scanning cost covers data ownership in more detail, and our checklist on how to prepare your site for laser scanning lists what to ask for before you sign.
How do I open a point cloud file?
Most point cloud file formats open best in the software they were made for, but a free general viewer covers the open ones. CloudCompare is free, open source software that reads E57, LAS, LAZ, PLY and PCD files among others. Leica LGS files open in TruView Desktop, and Autodesk RCP files open in ReCap.
To share a cloud with people who have no point cloud software at all, use a browser viewer such as Potree, a free, open source WebGL renderer. The example point cloud on our 3D laser surveys page runs in it.
How do I convert a point cloud to a 3D model?
Whichever point cloud file formats you start with, a point cloud becomes an engineering model in four steps:
- Register and clean the scans, then check the registration report so you know the cloud fits together.
- Export in the format your modelling software attaches: RCP for AutoCAD, Plant 3D and Revit, or POD for MicroStation.
- Attach the cloud and model over it. Pipework, steel and equipment are modelled with the points as the reference.
- Check the model against the cloud before it’s issued.
A mesh made straight from the points, saved as PLY or OBJ, is useful for visualisation, but it isn’t an engineering model with line numbers, specifications and connections.
Point cloud file formats at a glance
This table sums up the point cloud file formats covered above.
| Format | Extension | Type | Best for |
|---|---|---|---|
| E57 | .e57 | Open, ASTM E2807 | Handover, archive and exchange |
| LAS | .las | Open, ASPRS | GIS and lidar mapping |
| LAZ | .laz | Open, LASzip | Compressed LAS for storage and transfer |
| PLY | .ply | Open | Meshes and visualisation |
| PTS | .pts | Plain text, Leica origin | A merged cloud as text |
| PTX | .ptx | Plain text, Leica origin | Registered scans as text |
| XYZ, TXT, CSV | .xyz, .txt, .csv | Plain text | Small extracts |
| RCP, RCS | .rcp, .rcs | Autodesk | AutoCAD, Plant 3D and Revit |
| POD | .pod | Bentley | MicroStation |
| FLS | .fls | FARO | FARO SCENE |
| TDX, TZF | .tdx, .tzf | Trimble | Perspective, RealWorks and Business Center |
| LGS, LGSx | .lgs, .lgsx | Leica | Cyclone, TruView and CloudWorx |
| RXP, RDBX | .rxp, .rdbx | RIEGL | RiSCAN PRO |
| ZFS | .zfs | Z+F | LaserControl |
| CL3, CLR | .cl3, .clr | Topcon | ScanMaster |
Not sure which point cloud file formats your designers need? Give us a call or drop us an email. Tell us what software they use, and we’ll agree the formats before we scan so the data works first time.
About the author: Lewis Boxer is Founder and Director of Neonex Digital. He has 25+ years in the oil and gas industry, including time at Coryton Refinery, and 15+ years in terrestrial laser scanning, and is Autodesk certified.



