{"slug":"/3d-scanning/point-cloud-file-formats-e57-las-rcp","title":"E57 vs LAS vs RCP: Which Point Cloud File Did You Actually Get?","description":"E57 (ASTM E2807), LAS/LAZ, RCP/RCS, POD, PTX and PTS compared: what each file holds, which software opens it, real file sizes, and what to put in the scope.","h1":"Point cloud file formats: what each one holds and what opens it","answer":"E57 (ASTM E2807) is the neutral master: it carries scanner pose, intensity, colour and panoramic imagery in one file. LAS/LAZ carries geometry only. RCP/RCS is Autodesk's indexed derivative, and POD is Bentley's. PTX and PTS are legacy ASCII. Specify E57 as the archive deliverable plus one indexed format matching the software you already own.","expansion":"The folder you received sorts into three groups. E57 and LAS/LAZ are open exchange formats, readable by free software and published as specifications. RCP/RCS, POD and the AVEVA Point Cloud Manager dataset are indexed vendor working copies, built one-way from those sources so a workstation can stream billions of points. PTX and PTS are Leica's ASCII exports, kept alive by a few legacy tools and several times larger than the data they carry. Only one of those groups is an archive. E57 holds each scanner setup with its own pose, the structured grid, the invalid-return flags and the panoramic imagery, which is everything needed to regenerate the rest. LAS holds geometry with no pose and no imagery, and LAZ compresses it losslessly. Specify the E57 master plus one indexed working copy named after the software your team already runs, and write the [modelling scope](/3d-scanning/scan-to-cad-modelling-levels-lod) as a separate clause.","source":"ASTM E2807, Standard Specification for 3D Imaging Data Exchange, Version 1.0 (E2807-11, carried forward by reapproval; edition checked: E2807-11(2019), with a later reapproval of the same 2011 text listed as active). ASPRS LAS Specification 1.4, revision R15. LAZ Specification 1.4 (rapidlasso). libE57 Foundation API reference (bitPackCodec, CompressedVector, ScaledInteger). Autodesk ReCap and Revit point cloud documentation. Bentley MicroStation point cloud documentation. Leica Cyclone PTX/PTS format documentation. AVEVA Point Cloud Manager (formerly LFM Server). CloudCompare project documentation. Byte-per-point figures computed from the published record layouts. Verified August 2026.","table":{"caption":"Point cloud formats at handover: content, readers, compression and size","columns":["Format","What it carries","Opens natively in","Compression","Size, 100M points"],"rows":[["E57 (.e57) — ASTM E2807","Per-setup 4x4 pose, XYZ, intensity, colour, structured grid, invalid-return flags, spherical and pinhole imagery, XML metadata","CloudCompare, ReCap, Cyclone, SCENE, RealWorks, most plant CAD via import","Lossless bit-packing (bitPackCodec)","~1.7-2.5 GB"],["LAS (.las) — ASPRS 1.4 R15","XYZ as scaled 32-bit integers, intensity, classification, returns, GPS time; RGB only in record formats 2, 3, 5, 7, 8, 10. No pose, no imagery","CloudCompare, ReCap, GIS and survey software, PDAL","None","3.4 GB (record format 3)"],["LAZ (.laz) — LASzip","Identical content to the LAS it came from, stored in independently decompressible chunks","Same readers as LAS, plus LAStools and PDAL","Lossless entropy coding, roughly 7-20% of source","~250-700 MB"],["RCS / RCP — Autodesk ReCap","RCS = one octree-indexed scan. RCP = project file referencing RCS files plus registration, scan regions, distances, annotations","Revit, AutoCAD, Civil 3D, Navisworks, ReCap","Proprietary indexing, one-way","Set by index settings, not by point count"],["POD — Bentley","Octree-indexed points with colour, intensity, classification; the only format that attaches natively to a DGN","MicroStation, OpenPlant, OpenRoads, Pointools","Proprietary indexing, one-way","Set by conversion settings"],["PTX — Leica ASCII","Per-scan 4x4 transform, structured grid retained, XYZ, intensity, RGB as text; writes a row for every shot including non-returns","Cyclone, CloudCompare, most importers","None (plain text)","4-7 GB"],["PTS — Leica ASCII","Flat XYZ, intensity, RGB as text. No pose, no grid","Cyclone, CloudCompare, most importers","None (plain text)","3.5-5 GB"]],"note":"Sizes computed from the published record layouts at 100 million points carrying XYZ, intensity and colour: 17 bytes per point for a scaled-integer E57, 34 bytes for LAS point data record format 3, 40-60 bytes per line of ASCII. Embedded imagery, 1024-byte page overhead and null grid rows add to these."},"facets":[{"q":"Which point cloud format should I name in the contract?","a":"Name two. E57 per ASTM E2807 as the archive deliverable, undecimated, with each scanner setup preserved and the structured grid retained. Then one indexed working copy matching the software you own: RCP with its RCS folder for Autodesk sites, POD for Bentley sites, an AVEVA Point Cloud Manager dataset for E3D sites, LAZ where the work is georeferenced."},{"q":"Can I convert an RCP back to E57?","a":"No. ReCap indexing is one-way. An RCP references RCS files that hold points restructured into an octree, and any decimation applied at import to make the file manageable is gone permanently. Export tools produce a new cloud from the indexed data, not the original file. A survey delivered only as RCP cannot be re-purposed outside the Autodesk family later."},{"q":"Does E57 or LAS give me the smaller file?","a":"E57 is smaller uncompressed and LAZ beats both. A point with scaled-integer XYZ, intensity and colour costs about 17 bytes in E57 against 34 bytes in LAS point data record format 3. LAZ then compresses the LAS losslessly to roughly 7-20% of its size, which makes LAZ the smallest option and the right archive companion for georeferenced work."},{"q":"Why will Revit not open my E57 directly?","a":"Revit links RCP and RCS files, not E57. The E57 goes through ReCap indexing first, or through a third-party importer from the Autodesk App Store. That conversion is a real step with real hours attached, and it is where scope disputes start: the contractor delivered a valid standards-based file, the modelling team cannot open it, and nobody priced the indexing."},{"q":"What does a structured point cloud mean in a deliverable?","a":"Structured means each point keeps its row and column index in the scanner's sweep, so the cloud remembers the grid the instrument fired in. That grid is what lets software compute reliable surface normals, generate a panoramic view from the setup position, and separate a real surface from a mixed-pixel artefact at an edge. E57 and PTX preserve it. LAS and a merged export destroy it."},{"q":"Is LAZ compression lossy?","a":"No. LASzip is lossless entropy coding: decompress a LAZ and you get back the exact LAS it came from, byte for byte. It stores points in chunks that decompress independently, so software still random-accesses the file. What people call lossy compression in point clouds is almost always decimation — points deleted to hit a spacing target — which is irreversible and unrelated to the codec."}],"sections":[{"heading":"Read the extension before you read the invoice","paragraphs":["A scan delivery lands as a folder of files with six or seven different extensions, and the useful sort is not best-to-worst. It is master, derivative and legacy. E57 and LAS/LAZ are exchange formats: anyone can read them with free software, and they can regenerate everything else. RCP/RCS and POD are vendor working formats — fast, indexed and one-way. PTX and PTS are ASCII text from the Leica lineage, kept alive by a handful of old workflows. Establish which file in the folder is the master before you archive anything.","The master is the file that can rebuild every other deliverable five years from now, after the scanning contractor has changed software and the technician who ran the job has left. That file has to carry each scanner setup separately, with its own position and orientation, at full captured density, in a documented coordinate system. If the only file in the handover is an indexed vendor project, the master does not exist and the survey is now hostage to one software vendor's licence renewal.","Three checks settle the question at handover: which file holds the undecimated per-setup data, which coordinate system and units the numbers are in, and whether the scanner's own structure survived the export. Everything else — colour, panoramic imagery, classification — is recoverable or replaceable. Those three are not. Run the checks in the week the data arrives, while the crew can still remobilise, rather than during the outage where the model is needed."]},{"heading":"E57 is the only one published by a standards body","paragraphs":["E57 is standardised as ASTM E2807, Standard Specification for 3D Imaging Data Exchange, Version 1.0, originally approved in 2011 and kept current by reapproval rather than revision. The edition most implementations cite is E2807-11(2019), and ASTM's catalogue lists a further reapproval of the same 2011 text as the active version, so a scope clause reading \"E57 per ASTM E2807\" stays correct without naming a year. It is the only format in this list published by a standards body rather than by the company that sells the software that reads it.","The file is a hybrid. Binary point data is written in fixed 1024-byte pages, each carrying a checksum, and described by an XML section. That layout is why a reader can navigate a 40 GB E57 without loading it and why partial corruption stays legible. Each scanner setup is stored as its own section with a 4x4 pose, so the registration lives inside the file rather than in a separate transform list. Photographs — spherical panoramas and pinhole images — sit alongside, which is how a colourised cloud keeps the imagery that coloured it.","Two E57 features matter for plant work and get lost in casual exports. The structured grid stores each point with its row and column index in the scanner's sweep, which is what lets software compute reliable normals, build a panorama and separate a real surface from a mixed-pixel artefact at an edge. The invalid-state flag records where the scanner fired and got no return, which is the difference between \"nothing there\" and \"not measured\". Compression is a lossless bit-packing codec that shrinks integer fields to their actual range."]},{"heading":"LAS and LAZ carry geometry and throw the rest away","paragraphs":["LAS comes from airborne LiDAR and the American Society for Photogrammetry and Remote Sensing, and it shows. The current published edition is LAS 1.4, revision R15. Coordinates are stored as 32-bit signed integers with a scale factor and offset declared once in the header, so precision is a header decision rather than a format limit: at a scale factor of 0.001 the integer range spans roughly 2,147 km either side of the offset, which covers any plant on any state plane grid at millimetre resolution. Getting that header wrong is the commonest way a LAS delivery quietly loses precision.","What LAS holds per point is fixed by the point data record format, and the byte counts set your file sizes. Format 0 is 20 bytes. Format 1 adds GPS time at 28, format 2 adds colour at 26, format 3 carries both at 34. The 6-to-10 family rebuilt the record for 15 returns and 256 classes: format 6 is 30 bytes, format 7 adds colour at 36, format 8 adds near-infrared at 38. Intensity is present everywhere. Colour is present only in formats 2, 3, 5, 7, 8 and 10, so a request for \"LAS with colour\" has to name the record format.","What LAS does not hold is the reason it makes a poor master for terrestrial plant scanning. There is no scanner pose, no imagery and no structured grid, so the deliverable arrives as one merged cloud in a single frame with the setups blended together. Point Source ID, and Scanner Channel in the newer formats, are the only provenance left. LAZ fixes the size problem without touching content: LASzip is lossless, lands at roughly 7-20% of the LAS it came from, and chunks the data so readers still random-access it."]},{"heading":"RCP and RCS are a working copy, never an archive","paragraphs":["RCS and RCP are Autodesk ReCap's pair. An RCS holds one spatially indexed scan — coordinates, colour and intensity restructured into an octree so a workstation streams level-of-detail instead of loading three billion points. An RCP holds no points at all: it is a project file that references a set of RCS files and adds registration transforms, scan regions, recorded distances and annotations. Move or rename the RCS folder and the RCP opens empty, which is the most common support call in scan-to-BIM work and the reason an RCP delivery needs a folder-structure note.","This pair is what Revit, AutoCAD, Civil 3D and Navisworks attach natively. Revit does not link an E57 out of the box: the E57 goes through ReCap indexing first, or through a third-party importer from the Autodesk App Store. That conversion step is where scope disputes start, because the contractor delivered a valid standards-based file, the modelling team cannot open it, and neither party priced the indexing. Name the indexing in the scope and name who performs it.","Treat RCP and RCS as derivatives. Indexing is one-way — there is no route back to the E57 it was built from — and any decimation applied at import to make the file manageable is gone permanently. A survey delivered only as RCP is usable for two years in one software family and cannot be re-purposed afterwards. The same logic governs every indexed vendor container, which is the point of writing a proper [deliverables specification](/3d-scanning/point-cloud-to-cad-deliverables) rather than accepting whatever the contractor's software exports."]},{"heading":"POD, PTX, PTS and the plant-specific containers","paragraphs":["POD is Bentley's equivalent. MicroStation, OpenPlant and OpenRoads import a long list of formats — LAS, E57, PTS, PTX, FLS, RXP and more — but only POD attaches natively to a DGN through the point cloud engine, so everything else is converted on the way in. The one-way rule holds: POD is a working copy. AVEVA E3D consumes clouds through AVEVA Point Cloud Manager, formerly LFM Server, which builds its own indexed dataset from the same source formats and serves it to the design session.","PTX and PTS are Leica Cyclone's ASCII exports, and they are text files. PTX keeps the useful part — each scan section carries a 4x4 transformation matrix and the structured grid survives — while PTS is a flat list with no pose and no grid. Because the grid is preserved as text, PTX writes a row for every shot the scanner fired, including the ones that returned nothing, so the file is dramatically larger than the data inside it. Both formats are in decline as E57 absorbs their role.","Neither belongs in a modern scope except as a named compatibility copy for one named legacy tool. If a stress package, an old piping design seat or a subcontractor's viewer needs PTX, write that single requirement in and generate it from the E57 master. Making PTX the general deliverable multiplies your storage several times over and hands the next contractor a text file to re-parse."]},{"heading":"Where the data actually disappears","paragraphs":["Compression is not where point cloud data is lost. LAZ is lossless entropy coding and E57's bit-packing is lossless integer packing; both return the numbers they were given. Data disappears in three other places. Decimation removes points at export or index time to hit a spacing target, and it is irreversible. Quantisation sets how finely coordinates are stored — the LAS scale factor, the E57 scaled-integer precision — and a coarse setting rounds real geometry away. Structure loss merges the setups into one undifferentiated cloud and destroys pose, grid and per-setup provenance in a single operation.","Structure loss is the one buyers never see coming, because the merged cloud looks correct on screen. The cost shows up later. Normals become unreliable, so surface fitting and automatic pipe extraction degrade. Panoramic views are gone, so a remote reviewer cannot look around from a setup position. A noisy scan cannot be isolated and re-weighted, because nobody can tell which points came from which setup. Any of those failures pushes work back to a field remobilisation months after the crew demobilised.","One rule prevents all three: the archive deliverable is undecimated, per-setup and structured, in E57. Every optimised, merged and decimated file in the delivery is a derivative of that one, generated for a named tool and regenerable at will. Once that is written into the scope, working formats stop being contentious, because losing one costs an afternoon of re-conversion rather than a re-scan. If the cloud is heading into an operational [digital twin](/digital-twins), that rule is what keeps the geometry re-usable when the twin platform changes."]},{"heading":"File sizes at real plant densities","paragraphs":["Size follows from bytes per point and the arithmetic is short. A point with XYZ as three 4-byte scaled integers, 2-byte intensity and 3-byte colour costs 17 bytes, so 100 million points is about 1.7 GB before imagery and page overhead — roughly what a well-written E57 costs. The same 100 million points in LAS point data record format 3 is 34 bytes each, or 3.4 GB. Compress that to LAZ and it lands around 250-700 MB. PTX, as text, runs 40 to 60 bytes per line and clears 4 GB, plus the null rows for every non-return.","Those numbers decide who can open your data. A 2 GB E57 opens in free software on a laptop. A 40 GB merged E57 from a full process unit opens only in software that streams from disk, which is precisely what the indexed formats exist to solve — an RCP or POD is sized by its indexing settings rather than by the raw point count, and it is the file an inspector or a project engineer will actually use. Deliver both and the archive question stops competing with the usability question.","Storage cost is the weakest reason to decimate. A full unit survey held as lossless LAZ plus a per-setup E57 master fits inside the storage a mid-size operator already pays for, and it is smaller than the video footage from one turnaround. What justifies a decimated copy is the field tablet and the review session, and both are derivatives generated on demand. Never let a workstation performance problem become an archive policy."]},{"heading":"What to write into the scope of work","paragraphs":["A deliverable clause that prevents every dispute above fits on one page. Name the archive format as E57 per ASTM E2807, with each scanner setup preserved, undecimated, structured grid and invalid-state retained. Name the coordinate system, the units, the vertical datum and the plant grid or benchmark the survey ties to. Require the registration report with cloud-to-cloud and target residuals rather than a pass statement. Require the panoramic imagery inside the E57 rather than as a separate folder of JPEGs that no software will ever re-associate with the points.","Then name the working copy after the software you already own. Autodesk sites ask for RCP with the RCS folder intact and a note on relative paths. Bentley sites ask for POD. AVEVA sites ask for the Point Cloud Manager dataset. Georeferenced and drone-integrated work asks for LAZ. One named working format is enough — a scope that lists five is a scope that pays for five conversions and archives none of them properly. If the cloud will feed an operational [digital twin](/digital-twins), name that consumer too.","Close with the mechanics: a file manifest with checksums, a naming convention that encodes unit, setup number and date, and a statement that the deliverable must open in a licence-free reader. That last line is the enforcement mechanism for everything above it. Keep the [modelling scope](/3d-scanning/scan-to-cad-modelling-levels-lod) as a separate section rather than folding it into the scanning clause, because modelling effort is the real cost driver and it deserves its own acceptance criteria."]},{"heading":"The twenty-minute handover check","paragraphs":["Twenty minutes with free software settles acceptance. Open the master E57 in CloudCompare, which reads E57, LAS, LAZ, PTX and PTS without a licence. Confirm the setup count matches the field log. Confirm colour and intensity are present. Measure something you know — flange face to flange face, a nominal pipe outside diameter, a column bay — and check it against the drawing. Read the coordinates of a known benchmark and confirm they land where the plant grid says they should.","Then convert one scan yourself into your working format. If you can index one E57 into an RCS, or bring one into POD, the whole set will follow and you have proven you are not dependent on the contractor to use your own data. That single test separates a survey you own from a survey you licensed, and it applies the same evidence logic that makes [an NDT report defensible](/report-validation/what-makes-an-ndt-report-defensible): traceable, repeatable, independently readable. Book it before the retention payment, not after.","What comes next is a separate decision with a larger number attached — how much of that cloud becomes modelled geometry, and at what level. That question drives more cost than the scanning does, and it is answered on the [modelling levels page](/3d-scanning/scan-to-cad-modelling-levels-lod). If the geometry is heading into an operational model that inspection data will hang off, the [twin side of the workflow](/digital-twins/inspection-data-on-a-twin-what-it-changes) sets what the model has to support. To scope a survey against the tools you already run, [ask for a quote](/contact)."]}],"faq":[{"q":"What software opens an E57 file for free?","a":"CloudCompare is the standard answer: it is free and open source, runs on Windows, macOS and Linux, and reads E57, LAS, LAZ, PTX, PTS, PLY and around twenty other formats. It also converts between them, which makes it the right acceptance tool at handover. Autodesk ReCap, Leica Cyclone, FARO SCENE and Trimble RealWorks all read E57 as well, under licence."},{"q":"How large is the point cloud for a full process unit?","a":"Work it from bytes per point. A well-written E57 costs about 17 bytes per point carrying XYZ, intensity and colour, so a billion points is roughly 17 GB before embedded imagery. The same data as LAS point data record format 3 is 34 bytes per point. LAZ compresses that to roughly 7-20%. A congested unit surveyed at production density runs to tens of gigabytes in the master file."},{"q":"What is the difference between an RCP and an RCS file?","a":"An RCS holds the points for one scan, spatially indexed into an octree. An RCP holds no points at all — it is a project file pointing at a set of RCS files, plus registration transforms, scan regions, recorded distances and annotations. Both must be delivered together with the folder structure intact, because moving or renaming the RCS folder makes the RCP open empty."},{"q":"Should I accept a single merged cloud as the deliverable?","a":"Not as the archive. Merging the setups into one cloud destroys the per-setup pose, the structured grid and the provenance of every point, and none of it comes back. Surface normals degrade, panoramic review from a setup position becomes impossible, and a noisy scan can no longer be isolated. Accept a merged file as a convenience derivative alongside a per-setup E57 master."},{"q":"Which standard defines the E57 format?","a":"ASTM E2807, Standard Specification for 3D Imaging Data Exchange, Version 1.0. It was approved in 2011 and has been carried forward by reapproval rather than revision, so the technical content is unchanged: the edition commonly cited is E2807-11(2019), with a later reapproval of the same text listed as active. Writing \"E57 per ASTM E2807\" in a scope stays correct without naming a year."}]}