Compare point cloud file formats—E57, LAS/LAZ, RCS/RCP, PTS, and native vendor files—for Scan to BIM exchange, archiving, and Revit workflows.
BimzstudioJun 25, 202512 min
file-formatsE57LASLAZRCSRCPReCapScan to BIM
Best Point Cloud File Formats
Choosing a point cloud format is a project decision with cost and risk attached. The wrong choice creates broken Revit links, multi-day file transfers, lost intensity data, or archives nobody can open in five years. This article compares the formats Scan to BIM teams actually use—E57, LAS/LAZ, PTS/XYZ, Autodesk RCS/RCP, and vendor natives from Leica, Faro, and Trimble—and recommends when each belongs in a Europe or USA project pipeline.
Archive lossless formats; use project formats for production speed.
Point clouds are big. Formats exist to balance interoperability, compression, structure, attributes, and software performance. Problems arise when:
A surveyor delivers raw vendor projects only
A BIM team demands RCP but receives unindexed E57
LAS files strip needed attributes
Multiple RCS files lose their RCP project context
Long-term FM archives are stored only as proprietary caches
Need
Better format tendency
Open exchange between firms
E57, LAS/LAZ
Autodesk Revit / ReCap performance
RCS + RCP
GIS / wide-area LiDAR
LAS/LAZ
Quick ASCII debug
PTS/XYZ (small sets)
Vendor advanced workflows
Native Cyclone/SCENE/RealWorks
Long-term archive
Open format + documented CRS
There is no single “best” format—only best for a stage.
Why It Happens
Ecosystem lock-in. Teams live inside one vendor’s tools and treat natives as deliverables.
Email-era habits. People still try to send giant clouds like PDFs.
Attribute ignorance. Intensity, RGB, classification, and GPS time matter differently to different users; formats handle them unevenly.
Version drift. ReCap project files reference RCS paths that break when folders move.
Compression myths. “Lossless” and “good enough for modeling” are different conversations.
Spec laziness. Contracts say “provide point cloud” without naming format, structure, or metadata.
Industry Examples
EU multi-party renovation (architect DE, MEP NL, surveyor PL). E57 used as contractual exchange; each party converted to working formats (RCS for Revit shops, vendor natives for survey QA). Avoided forcing one commercial license on all.
US DOT-adjacent building + site. LAS/LAZ for exterior corridor tied to civil; RCS for interior Scan to BIM. Dual delivery matched two industries’ norms.
Hospital FM archive in Sweden. After modeling, client stored LAZ + E57 plus metadata JSON for CRS and registration report—not only the RVT. Future re-modeling possible without original SCENE license.
Retail rollout USA. Central ReCap cloud (RCP) shared via Autodesk ecosystem for speed; E57 still required at handover for non-Autodesk stakeholders.
Technical Explanation
RCP/RCS speed modeling — E57/LAZ protect the archive.
E57
Industry-neutral exchange widely supported. Stores points and often imagery/attributes in a structured way. Excellent for contractual delivery between organizations. Not always the fastest working format inside Revit—convert/index for production modeling.
Use when: multi-vendor exchange, archive, specification compliance.
LAS and LAZ
ASPRS LAS is the workhorse of airborne and many terrestrial GIS pipelines. LAZ compresses LAS efficiently. Classification fields are first-class. Great for large outdoor sets and civil coordination. Building interior Scan to BIM teams use it less as a daily Revit link format, more as exchange/archive.
Use when: civil/GIS interoperability, compressed archives, classification workflows.
RCS and RCP (Autodesk ReCap)
RCS = indexed point cloud engine file. RCP = project file referencing one or more RCS. Revit links these efficiently. This is the practical production format for Autodesk-centric Scan to BIM.
Use when: Revit/Navisworks production; Autodesk collaboration.
Watch-outs: Keep relative paths intact; deliver RCP with all RCS; version carefully.
PTS, PTX, XYZ, TXT
ASCII or simple formats. Universal but bulky and slow. PTX may preserve scanner station structure useful for some registration forensics. Fine for small clips, teaching, or debugging—poor as primary delivery for whole buildings.
Vendor native projects
Leica Cyclone / LGSx ecosystems, Faro SCENE projects, Trimble RealWorks, etc., preserve setup hierarchy, targets, and processing history. Best for registration QA and resurvey. Poor as the only deliverable if the client lacks licenses.
Other containers
Some teams exchange pods, RCP unlocked packages, or proprietary streaming formats for web viewers. Treat viewers as communication layers; keep an open archival format underneath.
Metadata that formats do not magically fix
Regardless of extension, document:
Units
CRS / EPSG or local engineering grid definition
Registration method and residuals
Date of capture and instrument class
Known exclusions
buildingSMART and ISO 19650 thinking applies: the information container needs context, not only bytes.
Comparison table
Format
Interoperability
Revit speed
Compression
Best role
E57
High
Medium (after convert)
Moderate
Exchange/archive
LAS
High (esp. GIS)
Low–Med
Low
Exchange
LAZ
High
Low–Med
High
Archive/exchange
RCS/RCP
Autodesk-centric
High
Engine-optimized
Production
PTS/XYZ
Universal
Poor
Poor
Debug/small
Native vendor
Low–Med
N/A
Varies
Registration QA
Best Practices
Formats should map to who consumes the data next.
Specify dual delivery: open exchange (E57 or LAZ) + production (RCP/RCS) when Autodesk modeling is in scope.
Never deliver RCS without RCP if the project spans multiple files.
Include a readme with CRS, units, and residual summary.
Keep raw natives in survey archive even if client only contracted E57.
Test-open deliverables on a clean machine before handover.
Agree naming:Project_Floor_Zone_v03.rcs patterns.
Avoid ASCII for whole buildings.
Do not recompress repeatedly through lossy pipelines.
Align format choices with CDE (where ISO 19650 applies).
Plan for 5-year reopen—licenses vanish; open formats remain.
Step-by-Step Solution
Step 1 — Map consumers
Who opens the cloud? Revit modelers, civil GIS, owner FM, future unknown?
Step 2 — Pick stage formats
Field native → registered master → exchange → production index → archive.
Step 3 — Register in the strongest environment
Often vendor tools or specialized register packages. Export a master.
Step 4 — Export open exchange
E57 and/or LAZ with attributes retained. Verify unit scale with a known distance.
Folder structure, hashes if required, QA PDF, coverage maps.
Step 8 — Validate in target software
Open in Revit, Navisworks, and one non-Autodesk tool if E57 was promised.
Step 9 — Handover checklist
Confirm all RCS present, paths relative, metadata complete.
Step 10 — Archive policy
Store open + native + reports. Do not rely on a single cache disk.
Case Study
Project: Courthouse renovation, US Northeast Stakeholders: County survey GIS group (LAS-centric), architect (Revit), specialty steel detailer (Navisworks), owner archive.
Initial failure: Survey uploaded only SCENE project to a portal. Architect could not open it. Two weeks lost arguing licenses.
Fix: Contract addendum required:
SCENE project retained by surveyor
E57 master registered cloud
LAZ for county GIS tie-in
RCP/RCS regions by floor for design team
Outcome: Modeling started within days of re-delivery. Steel detailer used Navisworks with the same RCP. Three years later, a new elevator study reopened the E57 successfully without SCENE.
Format planning was cheaper than the delay.
Common Mistakes
Single proprietary deliverable only
Broken RCS paths after zip/unzip
Stripping intensity “to save space” when metal QA needs it
Using XYZ for a 10-building campus
Mixing feet and meters silently during conversion
Overwriting v01 with v02 without notice while people model
Emailing sample snippets as if they represent full density
Forgetting panoramic images when E57 was expected to include them
Delivering decimated clouds for production without saying so
No CRS documentation beside the files
Expert Tips
Put CRS in the filename and the readme—redundancy helps.
For EU metric jobs, verify converters did not assume US survey feet.
Use LAZ for overnight cloud transfers; keep E57 when structure/images matter.
In ReCap, unify origins before multi-floor packaging.
Hash large deliverables (SHA-256) for dispute protection on public projects.
Teach PMs that RCP is a project, not a single blob.
When clients want Matterport-like viewers, still keep metrology formats underneath.
Check classification fields if AI segmentation will run later.
Prefer fewer, well-documented files over dozens of unexplained station exports.
Align with Autodesk and buildingSMART guidance on exchange without treating any blog (including this one) as a substitute for your BEP.
Format Decision Tree for Scan to BIM Teams
Ask four questions in order:
Who must open this without buying our scanner vendor's license? If multiple firms: include E57 and/or LAZ.
Will Autodesk Revit/Navisworks be the production environment? If yes: include RCP/RCS regions.
Is civil/GIS a stakeholder? If yes: LAZ with CRS metadata is usually expected.
Will someone reopen this in five years for FM or a new renovation? If yes: open archive plus registration report plus CRS readme are mandatory.
Detailed notes on E57
E57 remains the practical open exchange for building reality capture. It can carry structured scan data and imagery depending on exporter settings. Always verify units after import (a classic failure point), whether images were included when the contract required them, that the registered assembly—not raw unaligned stations—was exported, and file integrity via size sanity checks and opening in a second tool.
Detailed notes on LAS/LAZ
LAS/LAZ excel when classification and GIS workflows matter. For interiors, they work but may feel unnatural to building teams used to station-based projects. LAZ compression makes overnight transfers feasible. Preserve intensity when metal QA or AI classification is planned. Confirm whether your pipeline writes LAS 1.2 vs 1.4 fields your consumers expect.
Detailed notes on RCS/RCP
Autodesk ReCap indexes clouds for performance. RCP is the project glue. Delivery mistakes to avoid: sending RCS files without the RCP, breaking relative paths by flattening folders, forgetting support files after zipping, and mixing unlocked/legacy formats without testing the client's Revit version. Create floor/zone regions so modelers can isolate worksets of reality. That is often a bigger productivity win than changing format again.
Native vendor projects as the registration system of record
Leica, Faro, and Trimble native projects preserve targets, setups, and processing history better than flattened exchange files. Keep them even when the client never opens them. Future dispute resolution and partial re-registration depend on that history. Contractually, natives can remain surveyor-held while E57/RCP are client deliverables.
Packaging checklist for CDE upload
Open exchange file(s): E57 and/or LAZ
Production package: RCP + all RCS with relative folders intact
Metadata readme: CRS, units, residuals, capture dates, instrument class
Coverage map PDF
Exclusions list
Optional: SHA-256 checksums for public-sector jobs
Pointer to accepted version ID used by modelers
Performance and storage planning
Budget storage early. A hospital campaign can exceed several hundred GB across raw, registered, and indexed derivatives. Policies that keep only RCP without open archive create future lock-in. Policies that keep every intermediate without naming authority create confusion about which file is truth. One accepted registered release plus raw archive plus production indexes is a sane default.
Future Trends
Cloud streaming and reality-capture platforms will reduce local file anxiety, but contractual archives will still need open formats. Expect wider LAZ and E57 retention even when daily work happens in vendor clouds. AI pipelines will demand consistent attribute schemas—intensity, normals, confidence—pushing teams to stop discarding fields during conversion.
OpenBIM programs will keep asking for IFC models; clouds will remain companion evidence. Format literacy stays a core Scan to BIM skill.
Conversion Pitfalls and How to Catch Them
Format conversions are where silent unit and CRS errors appear. After every major export/import, measure a known baseline in the destination software. If a 10 m corridor becomes 10,000 mm incorrectly labeled—or becomes 32.8 ft without anyone noticing—the rest of the project inherits the lie. Keep a conversion log: source format, tool, version, units in, units out, CRS statement, operator, date.
Watch for clipped regions that disappear during conversion, intensity stripped to save space, and RGB present while geometry was decimated. When delivering to Autodesk ecosystems, open the RCP on a machine that is not the authoring workstation. When delivering E57, open it in a second vendor tool or CloudCompare. When delivering LAZ to GIS stakeholders, confirm the EPSG code loads correctly in their environment.
Finally, teach project managers that “the point cloud” is a package, not a single attachment. A zip that breaks relative RCS paths is a failed delivery even if every byte arrived. Pair this discipline with the modeling workflow in Point Cloud to Revit Workflow Explained.
Frequently Asked Questions
What is the best format for Revit?
RCP/RCS via ReCap is the practical best for performance and linking.
What is the best format for sharing between companies?
E57 is the usual open choice; LAZ is strong when GIS/classification matters and size is critical.
Is LAS good for interiors?
It works, but many building workflows prefer E57 exchange + RCS production. LAS shines outdoors/civil.
Do I need RGB in the file?
Only if visualization or certain classification methods need it. Geometry QA often uses intensity/mono.
Can I convert without losing accuracy?
Conversions should preserve coordinates; verify with check distances. Poor settings can resample or clip.
What about proprietary POD or other engine formats?
Fine as working caches inside a tool. Pair with open archive for handover.
Deviate from this stack only with a written reason (for example, pure civil corridor with no Revit scope). Defaults prevent the most expensive format fights: the ones that start after modeling has already begun.
Format Packaging Checklist for Distributed Teams
Archive format (often E57/project native) stored once, immutably
Modeling format (RCS/RCP or agreed) tiled by zone
README states CRS, units, color on/off, revision, source instrument
No dual “almost same” exports without a purpose note
Checksums for legal/evidentiary packages
CDE folder schema matches BEP naming
Choosing a format is necessary but not sufficient—packaging discipline is what keeps Scan to BIM schedules predictable.
Summary
The best point cloud file format depends on the stage: natives for registration depth, E57/LAZ for open exchange and archive, RCS/RCP for Autodesk production speed. Specify dual deliveries, document CRS and residuals, and test-open packages before you call the survey complete. That discipline prevents the most expensive “format problems”—which are usually planning problems in disguise.
Call to Action
Bimzstudio consumes production-ready clouds and delivers accurate Scan to BIM models with QA/QC and LOD 100–500 clarity for EU and USA clients. If your files are ready for modeling—or you need help defining deliverable packages—see Point Cloud to BIM and Point Cloud to Revit.
