If you have ever received 3D scan data and found yourself staring at a file extension you did not recognize — .rcp, .e57, .las, .pts — you are not alone. Point cloud file formats are one of the most confusing aspects of reality capture for owners and even for design teams new to the technology. Yet choosing the right format matters: the wrong one can mean data your software cannot open, files too large to work with, or lost information. This guide explains the major point cloud formats in plain language and helps you request the right one for your workflow.
You do not need to become a data expert. You just need to understand the handful of formats you are likely to encounter and which one fits the tools your team uses.
Why point cloud formats differ
A point cloud is a collection of millions or billions of measured points, each with a position and often color and intensity values. Storing that much data efficiently, while keeping it usable across different software, is a genuine engineering challenge. Different formats solve it in different ways — some prioritize universal compatibility, others prioritize tight integration with a specific software ecosystem, and others prioritize simplicity. That is why several formats exist rather than one universal standard.
The practical consequence is that the best format depends on what you plan to do with the data. A format that is perfect for Autodesk modeling may be awkward for archiving, and a universal exchange format may need converting before it drops into your tools.
E57: the interoperable standard
E57 is a vendor-neutral, open format designed specifically for storing 3D point cloud data along with images and metadata. Its great strength is interoperability — it is widely supported across software from different manufacturers, which makes it the preferred choice for sharing data between teams and for long-term archiving. If you want a format that is not tied to any single vendor and will remain broadly readable, E57 is usually the safe answer.
Because it balances broad compatibility with reasonable file size and the ability to carry color and intensity, E57 has become something of a default exchange format in the industry. When in doubt about sharing data with another party, E57 is a dependable request.
RCP and RCS: the Autodesk workflow
RCP and RCS are the formats produced by Autodesk ReCap, the company’s reality-capture software. RCS files hold the actual scan data, while an RCP file is a project that references one or more RCS files. Their advantage is seamless integration with Autodesk tools: Revit, AutoCAD, and Civil 3D read RCP files natively, so the point cloud drops straight into the modeling environment without conversion. If your team works in the Autodesk ecosystem — which many architecture and engineering firms do — RCP is often the most convenient delivery format.
The trade-off is that these are Autodesk-oriented formats. They are ideal inside that ecosystem but less suited to universal exchange, which is why many providers deliver both an RCP for modeling and an E57 for archiving and sharing.
LAS and LAZ: the survey and GIS standard
LAS is a widely used format born in the aerial LiDAR and surveying world, and it is common in GIS and geospatial workflows. It efficiently stores point data along with attributes like classification and intensity. LAZ is simply a compressed version of LAS that dramatically reduces file size without losing data. If your project involves survey, mapping, civil, or geospatial work, LAS or LAZ is often the expected format, and its compression makes it practical for very large datasets.
PTS, XYZ, and text formats
PTS and XYZ are simple text-based formats that store points as plain lists of coordinates and, in some cases, color and intensity. Their virtue is universality and simplicity — almost anything can read a text file. Their drawback is size and speed: text formats are large and slow to load compared with optimized binary formats. They are useful for simple exchange or when a receiving program supports little else, but they are rarely the best choice for large working datasets.
How to choose the right format
Choosing a format comes down to your software and your purpose. For Autodesk modeling, request RCP. For sharing between different platforms or long-term archiving, request E57. For survey, civil, or GIS work, request LAS or LAZ. For simple, universal exchange, a text format may suffice. The best practice, and what good providers often do by default, is to deliver more than one — for example an RCP for immediate modeling and an E57 as a neutral archive — so you have both convenience now and flexibility later.
The most important step is simply to tell your provider what software you use and what you intend to do with the data before the project begins. That single conversation prevents the frustrating and avoidable problem of receiving data in a format your tools cannot use.
Managing point cloud file size
Point clouds are large, and file size is a practical concern. A single building can produce many gigabytes of data, which affects storage, transfer, and how smoothly your hardware can work with it. Compression (as in LAZ), sensible density choices during capture, and splitting large sites into manageable regions all help. If your team struggles to open a dataset, the issue is often hardware or an inefficient format rather than the data itself — and a provider can often deliver a more workable version without sacrificing the accuracy you need.
Common questions about point cloud formats
Which format should I ask for?
Tell your provider your software and purpose. For most Autodesk users, RCP for modeling plus E57 for archiving is a strong default combination.
Can formats be converted?
Yes. Point clouds can generally be converted between formats, though conversion takes time and occasionally loses some metadata, so it is better to receive the right format from the start.
Why is my point cloud file so large?
Point clouds contain millions of measured points with color and intensity. Density, colorization, and site size all drive file size; compressed formats and sensible density settings keep files manageable.
Point cloud formats are less complicated than they first appear. Learn the handful you are likely to meet — E57, RCP/RCS, LAS/LAZ, and text formats — and tell your provider your software and goals, and you will always receive data you can actually use.
Formats and long-term archiving
Point cloud data is a valuable record, and how you store it affects whether it remains usable years from now. Proprietary formats tied to a specific software version can become difficult to open as tools evolve, while open, vendor-neutral formats like E57 are far more likely to remain readable over time. For owners who view a scan as a long-term asset — documentation of a building that may inform renovations, insurance, or facility management for decades — archiving in an open format is a wise precaution. Many providers deliver a working format for immediate use alongside a neutral archive format precisely so the data survives changes in software.
It is also worth keeping the original registered dataset, not just a converted or reduced version. The full-resolution archive preserves every option for future work, whereas a decimated or format-converted copy may quietly discard detail you later wish you had. Storing the master data safely is inexpensive insurance for an asset that is expensive to recreate.
Sharing data with non-technical stakeholders
Not everyone who needs to see scan data has CAD or BIM software, and this is where lightweight and web-based deliverables matter. Rather than sending a multi-gigabyte point cloud to a stakeholder who only needs to look, many providers offer navigable web viewers that open in a browser and let anyone explore and measure the space without specialized tools. When you plan your deliverables, consider who will need access and in what form — the modeling team needs a working format, but executives, owners, and other stakeholders are often better served by a simple viewer or exported images and drawings.
Matching the delivery format to each audience prevents both frustration and wasted effort. The right answer is frequently a small set of formats — a working file for the technical team, an open archive for the record, and an accessible viewer for everyone else.
Do I need to understand these formats myself?
Not in depth. You only need to tell your provider which software your team uses and what you plan to do with the data. They will translate that into the right format — or combination of formats — for you. The goal of understanding the basics is simply to have a productive conversation and avoid receiving data your tools cannot open, not to become a data specialist yourself.
Related guides
Planning a project in the Pittsburgh region? CAD Construct LLC delivers survey-grade 3D laser scanning, Scan-to-BIM, and virtual tours with field-verified accuracy. Request a scanning quote.
0 Comments