Technical guide

Point Cloud File Formats Explained: E57, RCP, LAS and More

Every scanning project ends with a file. Choosing the wrong format slows your BIM team, breaks software imports, or loses colour and classification data. This guide explains the formats we deliver and when to use each one.

12 min read · Updated 1 May 2026

Key points

  • 1.E57 is the safest interchange format: software-neutral, preserves colour and structured scan stations, and accepted by Revit, CloudCompare, and most survey packages.
  • 2.RCP/RCS is best when your team lives in Autodesk Revit or ReCap: native indexing, fast loading, and direct link into Revit point cloud worksets.
  • 3.LAS/LAZ is the GIS and civil standard for terrain, vegetation, and aerial LiDAR workflows in QGIS, Global Mapper, and Civil 3D.

1. Why format choice matters

A point cloud is not a single type of file. It is millions or billions of coordinates, often with colour, intensity, and classification flags. Different software reads different containers. Requesting RCP when your consultant uses 12d will waste a day. Requesting only LAS for a Revit renovation will frustrate your modeller. Match the format to the next software in the chain.

Brisbane Point Cloud quotes deliverables explicitly. Tell us your target software and we export once in the right format rather than charging change fees later.

2. E57: the interchange standard

ASTM E57 is an open container format designed for 3D imaging data exchange. It stores multiple scan stations, Cartesian coordinates, optional colour, and metadata in one file. Most professional scanning software reads and writes E57.

  • Use E57 when multiple parties need the same data in different software
  • Use E57 for long-term archive when you may change BIM platforms later
  • Use E57 when importing to CloudCompare, Leica Cyclone, or Trimble Business Center
  • File sizes are larger than compressed LAZ but smaller than unoptimised ASCII

3. RCP and RCS: Autodesk workflow

ReCap produces RCP (project file) and RCS (scan cache) pairs indexed for fast viewing in Revit, AutoCAD, and Navisworks. Large clouds load progressively instead of choking the machine on import.

FormatBest forTypical size
RCP + RCSRevit renovation, Navisworks coordinationModerate (indexed)
E57Multi-vendor exchange, archiveLarge
LAS/LAZCivil 3D surfaces, GISSmall to moderate (LAZ compressed)
DWG point cloudLegacy AutoCAD workflowsVaries
Common deliverable formats compared

4. LAS and LAZ: GIS and civil

LAS is the ASPRS standard for LiDAR point data. LAZ is the compressed version with identical information. Aerial drone surveys and topographic work often deliver LAZ for terrain modelling, vegetation classification, and volume calculation.

LAS uses a defined header with scale, offset, and projection. Deliverables should state the MGA zone and GDA2020 datum so civil models align with your survey control.

5. Other formats you may see

  • PTX: Leica native; convert to E57 for wider sharing
  • PLY: mesh-oriented; common in research and some viewers
  • XYZ / ASCII: human-readable but huge; avoid for full buildings
  • Pod / RCP from Trimble: convert via ReCap or Trimble RealWorks to E57 or RCP

6. What to put in your quote request

State your target software, required datum, and whether you need colour and classification. For BIM projects, specify LOD target and whether you want raw cloud only or modelled elements. That single paragraph saves rework on both sides.

Ready to scope your project?

Fixed-price quote within one business day.

Contact Us