Revit® can import a SketchUp file directly. Everyone who has done it knows what arrives: one block that cannot be exploded, cannot be isolated by part, cannot be cut by a cut plane unless it lands in a cuttable category, and cannot be built on. Autodesk’s own help page lists these limitations without softening them. The usual advice that follows is to trace over the import with native elements — which is not an import; it is redrawing.
There is a second route. It goes through 3ds Max®, and it ends with a Mass family that Revit treats as its own.
What the direct import cannot do
From Autodesk’s “Limitations of SketchUp Data Imported to Revit”:
| Limitation | What it means in practice |
|---|---|
| “You will not be able to explode 3D data” | The model stays one object. Try, and the 3D faces disappear |
| “Cannot isolate parts of whole elements with visibility/graphics” | You cannot hide a wing, a floor, a wall of the import |
| “Imports cannot be cut by a cut plane unless imported into a cuttable family category” | Plans and sections show it only if you chose the right container first |
| “Smooth” curved surfaces not supported | Curves arrive as their facets |
| Scaled groups “may be incorrectly scaled” | A scaled component can land at the wrong size |
Autodesk Help: Limitations of SketchUp data imported to Revit
None of this is a bug. It is what a foreign block is in Revit. The import is a picture of a model, not a model.
The route through 3ds Max
3ds Max imports SKP natively — it is on Autodesk’s list of supported import formats, no converter required. The SketchUp model arrives in 3ds Max as editable mesh objects, at the right scale.
From there the route is the same as for any 3ds Max scene:
- Import the SKP into 3ds Max.
- Push from 3ds Max with Levlin Bridge.
- Pull in Revit.
What arrives in Revit is not an import. Every 3ds Max object becomes its own Mass family — whether or not it sits inside a group — with solid faces rebuilt from the mesh, ten reference planes for dimensioning, and an ElementId that survives the next pull. Instances of the same object share one family type, one instance each. And the rule cuts both ways: a SketchUp model whose parts were all merged into a single object before export is one object in 3ds Max, and returns as one element in Revit. How you split the model in 3ds Max is how it arrives.
Why SketchUp geometry comes back especially clean
SketchUp models are made of flat faces. A SketchUp wall is a rectangle; a SketchUp roof is a few planes; a SketchUp arc is a run of flat segments. Flat faces are exactly what the coplanar merge rebuilds as a single solid face. A simple SketchUp building returns as a clean solid with one face per plane — measured on a simple SKP model, which returned entirely as solid faces with no mesh residual at all. How the solid-or-mesh decision is made.
Everything the direct import refuses becomes ordinary:
| The direct import | The returned Mass |
|---|---|
| One block, cannot explode | One Mass family per 3ds Max object — hide, isolate, select each one |
| Cannot dimension to it | Dimension to any face, or to the reference planes |
| Cannot build on it | Wall by Face on any face; Mass Floors per level |
| Cut plane only in a cuttable category | Category Mass cuts in plan and section |
| Redraw to update | Pull again; the same element updates in place |
What to expect with curves
SketchUp stores an arc as segments, so a curved SketchUp wall arrives in 3ds Max as a fan of flat facets and returns to Revit as those facets — each one a real planar face you can dimension to. That is more useful than it sounds, because it is exactly what SketchUp showed you. Geometry that was smoothed or sculpted before export is the only kind that returns as a mesh residual, still inside its Mass family and still grounded by the reference planes.
The honest boundary
The measured case is a simple SketchUp model imported into 3ds Max 2024 and pulled into Revit 2026, returning as a clean solid Mass. Larger SketchUp models follow the same rule per surface — flat returns solid, freeform returns mesh — because 3ds Max converts every import to the same mesh representation before Levlin Bridge reads it. We publish the case we ran. What the architect can do with the result.
Frequently asked
Why is my SketchUp import in Revit one block I cannot edit?
Because Revit’s SketchUp import produces a single imported object. Autodesk documents that it cannot be exploded, isolated by part, or cut outside a cuttable category.
Does 3ds Max open SketchUp files?
Yes. SKP is on Autodesk’s list of native 3ds Max import formats. The model arrives as editable mesh objects.
What does the SketchUp model become in Revit through Levlin Bridge?
One Mass family per 3ds Max object, groups included, with solid faces rebuilt from the flat SketchUp geometry, ten reference planes, and an ElementId that is kept on the next pull. Instances share one type; a model merged into one object returns as one element.
Can I use Wall by Face on it?
Yes, on any solid face. A simple SketchUp building returns entirely as solid faces.
What about curved SketchUp walls?
SketchUp stores arcs as flat segments, and they return as those segments — each a real planar face. Only smoothed or sculpted geometry returns as a mesh residual.
Do I need SketchUp Pro or a plug-in for this?
No. Any SKP file 3ds Max can import is enough. Levlin Bridge runs in 3ds Max and Revit; it does not touch SketchUp.
Related field notes
- How to get a 3ds Max model into Revit as a Mass family
- Which 3ds Max import formats can travel on to Revit?
- Blender to Revit: the FBX, OBJ, glTF and USD route through 3ds Max
- Rhino and Grasshopper geometry into Revit through 3ds Max
- Flat faces vs curved surfaces: what comes back from 3ds Max as a solid Mass, and what stays a mesh
- What can an architect do with a Mass that came back from 3ds Max?
- Do dimensions and tags survive when you pull again from 3ds Max into Revit?
- Why Levlin Bridge returns 3ds Max geometry to Revit as a Mass family, not a DirectShape
- Is there a plug-in that links Revit and 3ds Max in both directions?
- Why the Revit model arrives at the wrong scale in 3ds Max
- Why the Revit model appears twice in 3ds Max after a reload
- 3ds Max cannot link the Revit file? Four causes, in order
- Revit File Link or FBX for 3ds Max?
- Do Revit and 3ds Max versions have to match?
- What happens to deleted Revit elements in 3ds Max?
- Why modifiers and UVW break when a Revit link reloads
- What Combine By Revit Material actually does to your model
- Why “Keep material parameters on reload” doesn’t save your 3ds Max materials
- Does Datasmith move a Revit model into 3ds Max?
- Can Speckle sync Revit and 3ds Max?
- Is NVIDIA Omniverse still a Revit to 3ds Max route in 2026?
Levlin Bridge
Levlin Bridge is a Windows plug-in that moves geometry between Autodesk Revit and Autodesk 3ds Max in both directions. Push the model from Revit, pull it into 3ds Max, and push the geometry you changed back into Revit as real elements. Only the difference ever moves, so materials, modifiers and UVW stay exactly where you left them. Any Revit 2022–2027 works with any 3ds Max 2024–2027.
Levlin Bridge is in final testing and is not released. There is nothing to download yet. Leave your email and you get the 30-day trial the day it ships.