TL;DR
TL;DR: Revit links indexed RCP/RCS files, not raw E57, so index an E57 in ReCap first, then use Insert > Point Cloud and pick the positioning option that matches the provider's coordinate note (usually By Shared Coordinates or Origin to Origin). The cloud is a link, managed from Manage Links. Ask the provider for RCP/RCS plus E57, a coordinate note, survey control notes, a registration report and per-floor splits.
To bring a point cloud into Revit, you link an indexed Autodesk ReCap file (an RCP project or an RCS scan), not the raw E57. If you received an E57, open it in ReCap first, let ReCap index it, and save the result as an RCP project. Then, in Revit, go to Insert > Link > Point Cloud, choose the RCP, pick a positioning option (usually Auto - By Shared Coordinates or Auto - Origin to Origin), and click Open. The cloud comes in as a link, which you manage afterward from the Manage Links dialog. Most of the trouble comes earlier, from what the scanning provider did or didn't hand over, so this article ends with a checklist for that.
Can Revit open an E57 file directly?
No. Revit's point cloud command takes two file types: point cloud projects (*.rcp) and indexed point clouds (*.rcs). Autodesk's help for inserting a point cloud file says ReCap is the tool that converts "scan file data (raw format) to a point cloud format that can be viewed and edited in other products, such as Revit."
That split explains why a good delivery includes both formats. E57 is the vendor-neutral master: it opens in almost any registration or modeling package, and it's the copy you archive. RCP/RCS is the working copy your Revit team links. An RCP is a small project file that points at a folder of RCS files, and the RCS files hold the indexed points. An RCP delivered without its RCS folder is an empty project. Point cloud file formats explained goes through each format and when to ask for it.
How do you turn an E57 into an RCP with ReCap?
If your provider sent only an E57, you have to index it yourself. ReCap can import E57 files directly, and Autodesk's ReCap help notes that it can read the panorama images stored in an E57 to build RealViews (ReCap's scan-position views). The process is:
- Start a new project in ReCap and give it the name and folder you want the RCP to live in.
- Import the E57. ReCap indexes each scan in the file into RCS data.
- If the E57 is already registered (a single, aligned dataset), don't register it again. Re-registering a delivered cloud can quietly shift it away from the coordinate system the provider documented.
- Save the project. The RCP and its supporting folder are what Revit links.
Index onto a local drive, not a network share, and keep the RCP and its data folder together. If someone later moves the RCP without the folder, the Revit link will still load but show nothing.
The provider can do all of this before delivery. If anyone on your project models in Revit, put RCP/RCS in the scope.
How do you insert the point cloud in Revit?
These are the steps in Autodesk's Revit help:
- Open the Revit project.
- Click the Insert tab, then Point Cloud on the Link panel.
- In Look in, browse to the delivered RCP.
- For Files of type, choose **Point Cloud Projects (\*.rcp) or Point Clouds (\*.rcs)**. Hold Ctrl or Shift to select several files.
- Choose a Positioning option (see the next section).
- Click Open.
Two notes from the same page matter in practice. First, "to improve performance and reduce network traffic in a worksharing environment, point clouds should be linked from a local location." On a workshared model, each modeler should keep a local copy of the RCP/RCS at the same path. Second, "the cloud is visible in all views except drafting and schedule views." If you can't find it in a drafting view, nothing is broken. Check a 3D view or a plan.
Which positioning option should you choose?
The positioning option decides where the cloud lands relative to your model. Revit offers four:
| Option | What Revit does | When to use it |
|---|---|---|
| Auto - By Shared Coordinates | Assumes the point cloud coordinates are in the model's shared coordinate system | The model already has shared coordinates set up from a site or survey model, and the provider registered the cloud to that same survey control |
| Auto - Origin to Origin | Places the cloud's world origin (0,0,0) at the Revit project origin | A new existing-conditions model where the provider registered to a local project coordinate system |
| Auto - Center to Center | Aligns the center of the cloud with the center of the model | A quick look only. The result depends on what's already in the model, so it won't reproduce |
| Auto - Origin to Last Placed | Aligns the cloud with the previously inserted cloud | Linking more floors or buildings from the same registration after the first one is placed |
The Revit help adds that "by default, project origin and shared (survey) origin are in the same location." On a fresh model where nobody has set up shared coordinates, By Shared Coordinates and Origin to Origin put the cloud in the same place. The two only diverge once the survey point has been moved or coordinates have been acquired from a site model. At that point the choice matters, and the right answer is whichever frame the provider says they registered to.
That's why the coordinate note is the most important page in a scan delivery. Survey coordinates such as state plane values often sit a long way from Revit's origin, so many teams have the provider deliver the cloud in a local project coordinate system, together with a documented transform back to the survey system. Either approach works. What causes trouble is an approach nobody wrote down.
What does linking mean, and how do you manage the link?
Autodesk's overview of point clouds says it plainly: "a Revit model links a point cloud as a reference rather than embedding the file." That has four consequences for how you work:
- The RVT file doesn't contain the scan. When you send the model to a consultant, send the RCP/RCS too, or tell them where to get it.
- The path matters. If the RCP is renamed or moved, the link breaks. Agree on one folder location before modeling starts.
- Updates are a reload, not a re-insert. If the provider sends a corrected registration, replace the files at the same path and reload the link instead of inserting it again.
- You can unload what you aren't using. Unloading a floor you aren't modeling keeps the model responsive.
The same page notes that "the Manage Links dialog includes a Point Clouds tab that lists the status of all point cloud links (types) and provides standard Reload/Unload/Remove functionality." When a cloud goes missing, that tab is the first place to look.
What should your scanning provider deliver so this goes smoothly?
Most Revit problems trace back to a missing item in the delivery package. Write this list into the scope, then check it the day the files arrive:
| Deliverable | Why it matters in Revit | What to check on arrival |
|---|---|---|
| Indexed RCP project with its RCS folder | Links directly, with no indexing step on your side | The RCP opens in ReCap and shows points, not an empty project |
| Registered E57 | Neutral archive and fallback for non-Autodesk tools | Same extents and coordinates as the RCP |
| Coordinate system note | Tells you which positioning option to pick | States the system (local or survey), units, vertical datum, origin location and the transform to survey coordinates if one applies |
| Survey control notes | Ties the cloud to the site and to other consultants' models | Lists the control points used and where they came from |
| Registration report | Shows how well the scans fit together before anyone models from them | Residuals reported per setup, not one project average |
| Split by floor, zone or building | Keeps links light and lets modelers load only what they need | Every split shares one coordinate frame and follows a consistent naming convention |
| Coverage map and unscanned-area list | Separates measured geometry from assumed geometry | Locked rooms, hard ceilings and blocked walls are named, not silently missing |
Two points on that list come up often enough to spell out.
Accuracy and format are separate questions. A perfectly indexed RCP can still be registered badly. Ask for the accuracy statement and the registration report alongside the files. Our registered point clouds hold ±5mm, verified against control, and what ±5mm accuracy means explains how a figure like that is checked.
Splits only help if they line up. Exports split by level or building should all sit in one coordinate frame, so that linking the second floor with Origin to Last Placed or By Shared Coordinates drops it exactly on top of the first. Organizing point cloud data for Scan to BIM covers folder structure and naming, and the point cloud deliverables guide for BIM managers has a day-one receiving checklist you can run before modeling begins.
Through our point cloud services, the registered point cloud ships in 3 to 5 business days as E57 and RCP/RCS, with a registration report that documents the residuals. If you'd rather skip the modeling step as well, our Scan to BIM team builds the Revit model from that same cloud.
What goes wrong most often, and how do you fix it?
- The link loads but nothing appears. Either the RCS folder is missing or the cloud landed far from where you're looking. Check the RCP in ReCap first, then open a 3D view and zoom to fit.
- The cloud is offset or rotated against the grids. You picked a positioning option that doesn't match the frame the provider registered to. Remove the link and insert it again with the option the coordinate note specifies.
- The floors don't stack. The splits were exported in different frames. Send them back to the provider. Don't nudge them into place by hand.
- The model crawls. The cloud is being linked across the network, or it's one monolithic file. Link locally and ask for per-level splits.
With the delivery requirements in the scope before capture, linking the cloud is one of the shortest steps in the project. To scope a scan with a Revit-ready delivery, contact us.
