Recommended Free Tools
Choose the format according to what the recipient must do with the data. Use E57 for structured, registered scan exchange; LAS for lidar and geospatial point delivery; RCP/RCS for an Autodesk production project; and IFC for semantic BIM objects, relationships, properties, and geometry. IFC is not a container for the original scanner point cloud, while an RCP is not a self-contained scan file.
Choose the format by deliverable purpose
A file extension alone does not define a usable handoff. The receiver also needs the coordinate reference system, units, registration status, classification rules, version, and any dependent files. The table below gives the practical choice for common construction workflows.
As an Amazon Associate I earn from qualifying purchases.
| Format | Primary payload | Best fit | Portability and dependency | Main validation risk |
|---|---|---|---|---|
| E57 | Structured reality-capture scans and associated point attributes | Registered scanner data exchanged between different applications | Interchange-oriented; reader support for structured fields varies | Receiver may ignore scan structure, poses, or panorama attachments |
| LAS | Binary lidar and point records | Survey, mapping, GIS, and geospatial production deliveries | Open ASPRS specification; version and point-record format must be stated | Incorrect CRS, units, classifications, returns, or LAS record format |
| RCP/RCS | Indexed Autodesk point-cloud project references and settings | Coordination and modeling in Autodesk production workflows | RCP depends on its referenced RCS files and folder paths | Missing or moved RCS files make the project incomplete |
| IFC | Semantic building or infrastructure objects, relationships, properties, and geometry | BIM and facility/infrastructure information exchange | Open, vendor-neutral ISO standard; schema and model view must match | Object semantics, property sets, units, or georeferencing do not meet the exchange requirement |
For a large construction handoff, it is normal to deliver more than one format: for example, E57 or LAS for measured evidence, RCP/RCS for an Autodesk-based production team, and IFC for the modeled asset. These files serve different purposes rather than being interchangeable copies.
E57: a structured container for scan exchange
E57 is designed to package reality-capture information in a structured form. Autodesk documents E57 support under ASTM E2807. Its import specification describes scan records that can contain Cartesian or spherical coordinates, intensity, color, scan poses, and optional panorama images. This makes E57 more than a flat list of XYZ points when the receiving software preserves the structure.
#1 Best Overall
- Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity drive(1) (Based on internal testing; performance may be lower depending on host device & other factors. 1MB=1,000,000 bytes.)
- Up to 3-meter drop protection and IP65 water and dust resistance mean this tough drive can take a beating(3) (Previously rated for 2-meter drop protection and IP55 rating. Now qualified for the higher, stated specs.)
- Use the handy carabiner loop to secure it to your belt loop or backpack for extra peace of mind.
- Help keep private content private with the included password protection featuring 256‐bit AES hardware encryption.(3)
- Easily manage files and automatically free up space with the SanDisk Memory Zone app.(5). Non-Operating Temperature -20°C to 85°C
What an E57 package can contain
Autodesk’s export description identifies a root structure with a data3D vector for scan data and an optional images2D vector for image attachments. A conforming export can carry meter-based Cartesian coordinates, radian angles for spherical data, scan GUIDs, poses, acquisition times, color and intensity values, and point counts. JPEG or PNG panorama images may be associated with scans.
- Geometry: Cartesian XYZ points or spherical measurements, according to the source and export choice.
- Per-point attributes: intensity and, where available, color.
- Scan context: scan identifiers, acquisition times, poses, and point counts.
- Imagery: optional JPEG or PNG panorama attachments in the
images2Dstructure. - Organization: structured scan records rather than only one undifferentiated point stream.
When E57 is the better exchange file
Use E57 when the recipient needs a portable package of registered scans and may need scan-level organization, poses, attributes, or imagery metadata. It is particularly useful when the project may move between scanner-processing, coordination, and analysis applications instead of remaining in one vendor’s project format.
Do not assume every E57 reader exposes every field. Autodesk distinguishes structured point-cloud-only, unstructured, and point-cloud-plus-panorama export choices, and the receiving application may preserve only a subset. Ask the recipient whether it can read structured scan records, registration poses, intensity, color, and panorama links before promising those capabilities.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →E57 export decisions that affect the handoff
- Structured or unstructured: structured export keeps scan organization; unstructured export may be easier for a limited reader but can discard context.
- Point cloud only or with panoramas: include images only when the recipient’s workflow uses them and the delivery size is acceptable.
- Coordinates and units: document the coordinate reference system, project origin, and units even though E57 uses meter-based Cartesian coordinates in the described export model.
- Registration: state whether the scans are registered and identify the transform or control basis used by the project.
- Edits and clips: Autodesk notes that a structured E57 export is a complete export and does not apply project deletions or clips. If a viewer shows a cleaned or clipped subset, verify that the exported file contains the intended full data.
LAS: the lidar interchange choice
LAS is a binary 3D point-cloud interchange specification maintained by the American Society for Photogrammetry and Remote Sensing (ASPRS). It is primarily associated with lidar and geospatial production, where point records, classification, returns, and coordinate-reference information must survive between surveying, GIS, and mapping systems.
Rank #2
- Solid state performance with up to 800MB/s read speeds in a portable drive. (Based on internal testing; performance may be lower depending on host device, interface, usage conditions and other factors. 1MB=1,000,000 bytes.)
- Back up your content and memories on a storage solution that fits seamlessly into your mobile lifestyle.
- Take it with you on your adventures—up to two-meter drop protection means this durable drive can take a beating. (Based on internal testing.)
- Secure it to your belt loop or backpack for extra peace of mind thanks to the tough rubber hook.
- From Sandisk, a brand professional photographers trust to take on assignments.
What LAS 1.4 adds
The ASPRS LAS 1.4-R15 specification, revised in 2019, expands the format with 64-bit offsets and field sizes, up to 15 returns for one outgoing pulse, 256 point classes, WKT coordinate-reference definitions, an overlap bit, and optional extra-byte records. Those capabilities are useful only when the producer writes them correctly and the recipient reads the selected point-record format.
Version is not enough to identify a deliverable. State the LAS revision and the point data record format as separate requirements. USGS lidar handling requirements published for 2025 3DEP deliverables specify LAS 1.4-R15 and point data record formats 6–10, illustrating how a production contract can require both.
What to specify in a LAS delivery
- LAS revision and point data record format: for example, LAS 1.4-R15 with the agreed record format.
- CRS and WKT: identify the horizontal and vertical reference systems, datum, zone, epoch where relevant, and whether the definition is embedded in WKT.
- Units and coordinate scale: state whether coordinates represent metres, feet, or another project convention.
- Classification: provide the class-code scheme and identify any project-specific or extra-byte fields.
- Returns and overlap: explain how return numbers, number of returns, and overlap flags are populated.
- Compression: state whether the delivery is uncompressed LAS or a compressed LAZ derivative, and confirm that the recipient accepts it.
LAS is usually the stronger choice for lidar mapping and broad geospatial interoperability. It is not automatically the best replacement for E57 when scan poses, scanner organization, or panorama relationships are part of the required evidence.
Free tools Windows power users keep installed
One-click scans. No signup required.
RCP and RCS: Autodesk project references, not raw scan archives
An RCP is a relatively small Autodesk point-cloud project file. Autodesk describes it as a file that references indexed point-cloud laser-scan files and stores project settings such as scan regions; it does not contain the referenced scans itself. The associated RCS files are the indexed point-cloud files or project components that the RCP expects to find.
Rank #3
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
RCP versus RCS
| Item | Role | What happens if it is missing |
|---|---|---|
| RCP | Project-level reference and settings file, including organization such as scan regions | The project cannot resolve its point-cloud sources |
| RCS | Indexed point-cloud data referenced by the project | Referenced scans or regions fail to load, even if the RCP remains present |
Deliver an RCP only with every referenced RCS file and the original relative folder structure. Moving or renaming an RCS after packaging can break the project. Treat the complete folder as the working deliverable, not the RCP extension by itself.
When to use another format instead
RCP/RCS is appropriate when the recipient is continuing production in an Autodesk workflow and needs the indexed project organization. It is not a neutral archival exchange format. Autodesk also describes E57, PTS, and PCG as single-scan files that can combine project information for software that cannot read RCP/RCS. If the recipient uses software without RCP/RCS support, agree on E57 or another accepted interchange format instead.
IFC: semantic BIM information, not a scanner point-cloud container
Industry Foundation Classes (IFC) is an open, vendor-neutral standard for machine-interpretable descriptions of built assets. buildingSMART publishes IFC as ISO 16739. Its specification database lists IFC 4.3.2.0 (IFC 4.3 ADD2) as an official release tied to ISO 16739-1:2024, published in April 2024.
IFC represents objects such as walls, slabs, doors, equipment, spaces, infrastructure components, and their relationships. It can carry geometry, properties, classifications, and links between objects so that downstream software can interpret the model rather than merely display a cloud of measured points. As buildingSMART puts it, IFC provides machine interpretability of information and enables workflow automation.
Rank #4
- NEARLY 2X FASTER THAN OUR PREVIOUS GENERATION(8) – move 1,000 high-res photos in under 60 seconds(6) with up to 2000MB/s transfer speeds(2).
- IP65 RATING AND UP TO 3M DROP PROTECTION(3) – protects against spills and drops.
- POCKET-SIZED – fits easily in pockets and small bags.
- SPACE TO OWN YOUR AI CONTENT – speed and capacity to download your high-res clips and photo edits.
- 256-BIT AES ENCRYPTION(4) – helps keep private files secure with password protection.
Can IFC store a point cloud?
Not as the original scanner point-cloud container. IFC is the semantic model exchange layer, whereas E57 and LAS are measured point-cloud delivery layers. A typical reality-capture workflow keeps the measured cloud in E57 or LAS, uses it to model or classify the existing asset, and exchanges the resulting object-based BIM model as IFC.
Before exporting IFC, confirm the required schema release, exchange requirement or model view, units, georeferencing convention, and property sets. A file that opens in a viewer can still fail a coordination requirement if the target application expects a different IFC version, object type, property set, or coordinate basis.
How AutoCAD-oriented workflows handle these formats
Autodesk’s documented workflow is application-specific: AutoCAD attaches RCP/RCS point clouds directly, while E57 and LAS are converted through ReCap before attachment. Therefore, “Can AutoCAD open E57 or LAS?” should be answered as “not necessarily as a direct attachment”; plan for the supported conversion path in the exact product and version being used.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Confirm the target product and version. Verify whether it accepts the source extension directly, requires ReCap conversion, or needs a different export.
- Inspect the source before conversion. Record the CRS, units, registration state, scan count, classifications, and any required panorama or intensity data.
- Convert E57 or LAS through the supported ReCap workflow when required. Preserve the original source as the evidence file; do not treat the converted project as a substitute archive without agreement.
- Attach the resulting RCP/RCS in AutoCAD. Keep the RCP and all referenced RCS files together, preserving relative paths when moving the project.
- Check the drawing after attachment. Compare a known control point, extents, units, registration, visibility regions, and the presence of expected attributes.
A practical delivery procedure for construction projects
- Define the purpose first. Decide whether the recipient needs raw or registered scan exchange, lidar mapping, Autodesk production coordination, or a semantic BIM model.
- Write the acceptance specification. Name the format, version, CRS, units, registration status, classification scheme, imagery policy, and whether edits or clips are included.
- Choose E57 for structured scan exchange. State structured versus unstructured output, whether panoramas are included, and which scan attributes must survive.
- Choose LAS for lidar delivery. State the LAS revision, point data record format, CRS/WKT, units, classes, return information, extra bytes, and compression policy.
- Package RCP/RCS as a complete folder. Include the RCP, every referenced RCS, and any required project support files; preserve relative paths.
- Specify IFC separately from the cloud. Name the IFC schema and exchange/model-view requirement, then list required object types, property sets, units, and georeferencing.
- Run a sample-file acceptance test. Open a representative subset in the recipient’s target application and inspect coordinates, units, registration, classifications, imagery links, and semantic properties before shipping the full dataset.
Common failures and how to prevent them
The cloud is shifted or appears at the wrong scale
Check the stated CRS, vertical datum, units, coordinate scale, and project origin. Compare a surveyed control point or known grid intersection rather than relying only on visual alignment. A conversion can preserve points while changing how the target application interprets coordinates.
Best Value
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
An RCP opens but shows missing scans
Locate every RCS referenced by the project and restore the original relative paths. Do not send only the small RCP file. If the folder must be relocated, use the receiving application’s path-relinking process and verify each scan region afterward.
LAS classifications or attributes disappear
Confirm that the recipient supports the selected LAS point data record format, extra-byte records, overlap bit, and classification codes. Re-exporting to an older record format may remove fields even when the points themselves remain visible.
E57 registration or panoramas are absent
Check whether the export was structured, whether poses and image attachments were included, and whether the receiving reader supports those E57 elements. A reader that imports only an unstructured point stream cannot display metadata it does not parse.
The IFC model looks correct but fails coordination checks
Validate the schema release, model view or exchange requirement, units, georeferencing, object classes, and required property sets against the recipient’s specification. Visual appearance alone does not prove that the model’s semantics are usable.
Bottom line for a construction handoff
Use E57 when scan structure and registration context matter, LAS when lidar interoperability and explicit point-record requirements matter, RCP/RCS when an Autodesk team needs its indexed working project, and IFC when the deliverable is a semantic BIM model. Keep the measured cloud and the modeled IFC as separate, purpose-built deliverables unless the receiving party has explicitly defined another workflow.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
