How to Import a Point Cloud into Revit (and What a Revit Model From It Actually Includes)
Importing a point cloud into Revit takes about a minute: Insert > Point Cloud, pick the file, choose how to position it, and it appears in your views. The part that decides whether it is actually usable happens before and after that click - the file format, how the scan was registered, which coordinate system it carries, and what the Revit model was scoped to include.
This covers the click path, the format rules, the coordinate problem that makes a good scan look broken, and - because most people asking this are really asking “what do I get” - what a Revit model built from the cloud does and does not include.
The 60-second version
- Have the cloud in a Revit-readable format first (see RCP vs RCS below).
- Insert > Point Cloud, browse to the
.rcpor.rcs. - Choose Positioning. If the scans were registered into a real-world or site coordinate system that your project already shares, use Auto - By Shared Coordinates; for a standalone scan, Auto - Origin to Origin or Auto - Center to Center.
- The cloud links into the project. It is a reference, not editable geometry - you model over it.
- Manage it later under Manage > Manage Links > Point Clouds (visibility, reload, unload).
If the cloud does not appear, it is almost never a corrupt file - it is coordinates or visual range. That is covered below in the coordinates section.
RCP and RCS are not the same thing
The Insert > Point Cloud file browser offers indexed Autodesk ReCap formats only:
.rcs- a single indexed point cloud file..rcp- a ReCap project that references one or more.rcsfiles. This is what you want for a whole building.
Raw scanner exports - E57, PTS, LAS, PTX - are not in that file-type list. They have to be indexed in Autodesk ReCap Pro first, which is a separate Autodesk product from Revit. A clean handoff gives you an .rcp already indexed, so you open Revit and link it.
If your scope said “Revit-ready” and you receive only an E57, ask for the indexed .rcp.
Indexing is not registration, either. A project file whose scans were never aligned to each other will link into Revit without complaint and still be unusable to model from; that is a separate thing to check on receipt, covered in registered vs unregistered point clouds.
Link, or model from it? (there is no “import as geometry”)
A common misunderstanding: people expect the point cloud to become walls and floors. It does not. In Revit a point cloud is always a linked visual reference - millions of measured points that Revit’s drawing tools can snap to, either directly or via planar surfaces it detects on the fly near the cursor (press Tab to cycle between the two kinds of snap). Turning that into walls, floors, ceilings, and families is the modeling work, and that is a scope decision, not an import setting.
So there are really three questions, not one:
| You have / want | What happens in Revit |
|---|---|
| Just the cloud, your team models | Link the .rcp and model over it with your own staff |
| Cloud + you want the model built | The cloud is traced to a defined scope (below) and you receive the Revit model |
| Already have a model, want to verify | Link the cloud and check the model against it |
The wider order of operations around all three is laid out in the scan-to-BIM workflow.
Why a good scan looks “broken”: coordinates
The single most common “the import didn’t work” issue is not the file - it is the origin. If the scan carries a real-world or surveyor coordinate system and you link it with Auto - Origin to Origin, it can land kilometers away and read as missing or clipped. Worth knowing: by default a Revit project’s internal origin and its shared/survey origin sit in the same place, so Origin to Origin and Shared Coordinates give an identical result until someone actually establishes shared coordinates in the project.
Distance from the origin is not only a display annoyance. Revit’s modeling workspace is about 20 miles (32 km) across - roughly 10 miles (16 km) in any direction from the internal origin. Autodesk’s guidance is to keep all model geometry inside that radius; a link whose extents exceed the workspace is refused outright, and precision degrades well before the limit.
Fix: use the positioning that matches how the cloud was registered, and confirm the origin, the coordinate system, and the units with whoever registered the scans. Agreeing on that before anyone goes to site is part of the site prep conversation, and it is the cheapest question on this list to ask early.
File size and performance
A whole-building .rcp can be large enough to slow Revit on ordinary modeling hardware. Two practical habits: work inside a section box so Revit only draws nearby points, and unload the cloud when you are drafting sheets and do not need it visible. Turning the point cloud category off in Visibility/Graphics for views that do not need it does the same job per view. None of this changes the data - just what Revit has to draw.
What a Revit model from the cloud actually includes
This is the real buyer question. “A Revit model” can mean a wall-and-openings shell or a multi-trade coordination model - very different effort. What is included is set by scope and LOD, not by the scan:
| Element group | Typically included | Notes |
|---|---|---|
| Architectural | Walls, floors, roofs, openings, stairs, ceilings | The standard core of most scopes |
| Structural | Columns, beams, visible framing | Only what the scan can see - not concealed steel |
| MEP | Major equipment, primary routing | Usually selected, not every conduit; called out per project |
| Sheets / drawings | Plans, elevations, sections | Often a separate deliverable from the model |
Two rules that prevent disputes:
- LOD is a decision, not a default. Tie it to how the model is used - a renovation layout model and a coordination model start from the same cloud but are not the same job. If you are pinning a number to it, what LOD 300 actually means is the definition to argue from.
- The scanner only captures visible, accessible surfaces. Above-ceiling, in-wall, buried, and otherwise concealed conditions are not in the cloud and therefore not in the model unless they are opened up, or investigated by some other method, and modeled separately. Say so up front.
Anything not named in scope - furniture, fine MEP, hidden structure, families beyond a stated level - should be listed as excluded so the handoff matches expectations.
How to check the model after you get it
When a model arrives, link the original cloud back in and spot-check: do walls and key elements sit on the points, is the Revit version right for your team, are the requested categories present, and are sheets included if you asked for them. A quick deviation check against the cloud catches most issues before they reach a consultant.
Common errors and fixes
- Nothing appears after linking - coordinate/origin mismatch. Re-link with Center to Center; use Shared Coordinates only if the project has real shared coordinates established (otherwise it behaves like Origin to Origin).
- Far-from-origin warning on link - same cause: Revit flags geometry sitting a large distance from the model; reposition.
- Revit is crawling - large cloud; use a section box, hide the point cloud category in views that do not need it, or unload it when drafting.
- You can select the cloud but not edit anything in it - expected. The linked instance selects as one object so you can move, pin, or unload it; individual points are never editable geometry. Model over it.
- Wrong scale/units - the cloud was indexed in different units; re-index in ReCap Pro with the correct units.
FAQ
Can you import a point cloud directly into Revit?
Yes - via Insert > Point Cloud, but only in indexed ReCap formats (.rcp/.rcs). Raw E57/PTS/LAS have to be indexed in ReCap Pro first.
What is the difference between linking and importing a point cloud?
In Revit there is effectively no separate “import” - a point cloud is always a linked reference you model against, not editable geometry.
Why is my point cloud not showing up in Revit?
Almost always coordinates: the cloud carries a survey coordinate system and lands far from the internal origin. Re-link using Center to Center - use Shared Coordinates only if a shared coordinate system was actually established and confirm the origin and units with whoever registered the scans.
How much does a Revit model from a point cloud cost?
It depends on LOD, area, and how much MEP/structure is modeled. See how much scan-to-BIM costs for the ranges and drivers, and 3D laser scanning cost for the capture side of the same budget.
If you need a clean, indexed point cloud and a Revit model scoped to exactly what your project uses, tell us what you need a quote on and we will scope it with you.
