Laser Scanning Data File Formats: E57, PTS, FLS, and LAS

Laser scanning data file formats are one of those topics that come up in nearly every industrial project right after fieldwork is complete. The point cloud has been collected, the data has been processed, and then the question arises: in what format should this be delivered? The answer directly affects how the data can be used in design software, maintenance systems, or a digital twin. The wrong format choice can mean extra conversion work, degraded data quality, or, at worst, a file that cannot be opened at all.

The most common point cloud formats in industrial projects are E57, PTS, FLS, and LAS. Each was created for a different need and carries its own strengths and limitations. This article walks through what these formats are, how they differ from one another, and how to make the right choice in a real project situation.

How different formats are created and what data they contain

A laser scanner measures its environment by emitting laser pulses and recording their return time. The result is a point cloud in which each point represents one measured surface location in three-dimensional space. In addition, points can contain intensity information — that is, the strength of reflectance — RGB color values from a camera, and scan-specific metadata such as a station ID and timestamp.

The format determines how this data is stored on disk. Some formats are structured — that is, organized — meaning that points are stored in a row-and-column structure from the perspective of the scanning station. Others are unstructured point sets. A structured format enables, for example, fast retrieval of neighboring points, which makes it well suited to certain post-processing purposes. An unstructured format is more flexible when combining multiple scanning stations.

File size varies significantly depending on whether compression is used and how dense the point cloud is. A stationary laser scanner can produce up to one million points per second, so the data from a single large industrial site can grow to tens or hundreds of gigabytes before processing. A format’s compression efficiency directly affects transfer, storage, and software performance.

E57, PTS, FLS, and LAS: key differences compared

These four formats are the most common in industrial laser scanning projects, but they serve different purposes and originate from different sources.

E57

E57 is an ASTM-standardized, vendor-neutral exchange format designed specifically for transferring point clouds and associated images between different software applications. It supports both structured and unstructured data and can contain scanning station metadata, intensity, and RGB colors within a single file. E57 has become the primary format for archiving and deliveries because it does not tie the data to a single software vendor.

PTS and PTX

PTS is an ASCII-based, text-format file that originates from Leica scanner hardware. It is simple and readable by almost all software, but its text-based structure makes it heavy for large point cloud datasets. PTX is an extension of PTS that also includes the scanning station’s transformation matrix. Both are well suited to smaller datasets and situations where compatibility with legacy software is important.

FLS

FLS is the native format of FARO scanners. It is binary and structured, meaning it stores data exactly as the scanner sees it — in the scanner’s coordinate system as a row-and-column structure. FLS contains intensity and color data as well as scanner settings. The format is optimized for the FARO software environment, particularly FARO Scene, where registration takes place before data is exported to other formats.

LAS and LAZ

LAS is an ASPRS-standardized format that was originally developed for airborne laser scanning. It supports point classification, which is especially useful in terrain modeling, but it is also used in industrial terrestrial applications. LAZ is the compressed version of LAS, capable of reducing file size to one-tenth of the original without any data loss. LAS and LAZ are particularly common in connection with GIS software and drone LiDAR datasets.

Choosing a format at different stages of an industrial project

The right format depends on what stage of the project you are at and where the data will end up. There is no single universal answer, but a few clear principles help guide the choice.

During fieldwork, the scanner stores data in its own native format — such as FLS on a FARO device or, in the case of NavVis, its own internal format. At this stage, the format does not yet matter to the end user. During the registration phase, when individual scanning stations are combined into a unified point cloud, data is typically exported to processing software where it is handled and cleaned.

When delivering data to a client or for further processing, the choice of format is critical. E57 is recommended for archiving and general transfer because it is standardized and software-independent. If the target environment is Autodesk ReCap, the RCP or RCS format is used. For design software such as AVEVA E3D, data is delivered in LFM format. For GIS use or drone datasets, LAZ is often the best choice due to its file size management.

Data exported to the Reality Twin service is processed from E57 or a comparable source format into the format used by Reality Twin, which enables dynamic streaming of large point clouds without a heavy workstation. This means end users can access the data in a browser without specialist software. Based on a user survey conducted by SolidComp in May 2026, Reality Twin has already become an established part of real working situations: of the survey respondents, 22 out of 32 stated that Reality Twin reduces the need to visit a site in person often or very often. Time savings was another strong finding — the majority of those who estimated time savings placed the saving at at least 15–60 minutes per session. This shows that a point cloud dataset that is correctly delivered and deployed produces tangible benefits in day-to-day work, not just at the moment of project delivery.

Conversion and compatibility: practical challenges

Converting from one format to another is routine in industrial projects, but it carries risks that are worth identifying in advance.

The most common issue is partial data loss during conversion. For example, when transferring FLS data to the ASCII-based PTS format, the binary structure is lost and file size increases significantly. Color or intensity data may be dropped if the target software or conversion tool does not support it. Coordinate system information can also be lost if the transformation matrix is not exported along with the data.

Another challenge is file size. Large industrial sites can produce hundreds of gigabytes of point cloud data, and converting to a text-based format can multiply the size many times over. LAZ compression solves this for LAS datasets, but E57’s internal compression is also effective.

Compatibility issues arise particularly when a project team is using different software at different stages. The design office may use an Autodesk ReCap environment, the maintenance team an AVEVA-based system, and the asset owner may want data delivered directly into Reality Twin. For these situations, it is worth agreeing on formats at the start of the project — before scanning, not after. Based on the user survey, the largest use case for Reality Twin is precisely the planning of projects, investments, layouts, and changes — which means the format decision directly affects how smoothly as-built information is available as the starting point for design.

SolidComp delivers point cloud datasets in agreed formats as part of its service — for example, as colored Autodesk ReCap point clouds with 360-degree images, Navisworks meshes, or AVEVA E3D LFM files. Format questions should be addressed already during the laser scanning project procurement phase so that the delivered data is immediately usable without additional post-processing. If the project objectives or target software are still open, the request for quotation is a good moment to determine the right format solution in one go.