An AI concept can reach Revit or Archicad without being redrawn, provided it exists as a model with classified elements and leaves as IFC4. Walls, slabs, columns, beams, windows, doors, roofs and rooms arrive as their own categories, with quantities and openings related to the walls they cut. Families, types, wall build-ups and materials as your office defines them do not transfer and were never in the file. The honest workflow is: settle the concept in the AI tool, export IFC4, link it into Revit as a reference, then swap elements for your own types as the design develops. What you save is the remodelling week, not design development.
This article is for BIM users who have seen “export to Revit” on an AI tool’s feature list and want to know what that means in practice. It uses Nuit’s IFC4 export as the worked example because we can show the file, but the mechanics apply to any tool that writes IFC honestly.
Why IFC, and why it is the only realistic bridge
Revit and Archicad are authoring environments. Their native formats (RVT, PLN) are closed, version-bound and structured around each program’s own element logic. No third-party AI tool can write a native Revit family; even Autodesk’s own tools do it through the Revit API from inside Revit.
IFC (Industry Foundation Classes) is the neutral schema the industry agreed on for exactly this problem. An IFC file describes a project as a hierarchy (project, site, building, storey) containing elements with a class (IfcWall, IfcDoor), a placement, a geometric representation, property sets and quantities, and relations between elements (this opening voids that wall; this door fills that opening). Revit and Archicad both import it and map classes to their categories.
The consequence for AI tools is stark: an AI tool can only export to BIM if it knows what its elements are. An image-based tool cannot. A mesh-based tool (one that reconstructs a surface from a picture, or generates a mesh from a prompt) can write a valid IFC in which everything is IfcBuildingElementProxy, which is technically BIM and practically a lump. The transfer is only useful when the classification happened at the moment the geometry was made.
That is the design decision behind Nuit’s 3D mode: the model is written as a script in which each element is tagged with its class as it is built. Walls are IfcWall from the first line, rooms are IfcSpace with a name and a floor area, openings are IfcOpeningElement related to their wall. The IFC export is a serialisation of what the model already knew, not a classification pass run afterwards.
What transfers
Here is what the Mirror Lake House IFC4 file, downloadable from the examples page, contains. The counts are read from the file at build time, so the page and the file cannot disagree.
| In the file | Count | Arrives in Revit / Archicad as |
|---|---|---|
| IfcWall | 12 | Walls |
| IfcSlab | 16 | Floors and roof decks |
| IfcRoof | 2 | Roofs |
| IfcColumn | 12 | Columns |
| IfcBeam | 205 | Structural framing (rafters, joists, eaves beams, standing-seam ribs) |
| IfcMember, IfcPlate | 103, 8 | Structural framing, generic structural |
| IfcWindow, IfcDoor | 5, 7 | Windows, doors |
| IfcStair, IfcRailing | 6, 45 | Stairs, railings |
| IfcCovering | 566 | Cladding boards, floor and ceiling finishes |
| IfcFooting | 9 | Structural foundations |
| IfcFurniture, IfcLightFixture | 12, 2 | Furniture, lighting |
| IfcGeographicElement | 57 | Site elements (water, rocks, banks) |
| IfcBuildingElementProxy | 7 | Generic models |
| IfcSpace | 5 | Rooms / spaces, with area: 56.8, 14.1, 13.9, 13.9, 11.8 m² |
| Elements, total | 1,079 |
Beyond the elements themselves, the file carries:
- Quantities on every element (IfcElementQuantity with length, area and volume as appropriate), which is what schedules read.
- Standard property sets (Pset_WallCommon, Pset_SlabCommon and so on) on the elements where the model had something to write: 15 sets in the example file, so most elements carry quantities but no Pset. The schema slots exist; the concept has not filled them.
- Openings related to walls: 12 IfcOpeningElement, each with its IfcRelVoidsElement to the wall and IfcRelFillsElement to the window or door. This is what lets Revit understand a window as in a wall rather than floating next to it.
- Spatial hierarchy: IfcProject, IfcSite, IfcBuilding, one IfcBuildingStorey, spaces aggregated to the storey.
- Geometry as extrusions where possible. Where the model knows an element’s profile and direction (walls, slabs, columns, most beams), it writes IfcExtrudedAreaSolid: 216 of them in Mirror Lake. Revit and Archicad can treat these as editable bodies. Where it does not, it writes IfcTriangulatedFaceSet (875 here, mostly cladding, site and library assets) with the correct class.
- Units: metres, square metres, cubic metres, declared in the header.
The generating brief for this model was two sentences plus four reference images: an elongated single-storey house on a rocky lake shore, about 120 m², living room with kitchen at the lake end, two bedrooms, bathroom, entrance hall. Five spaces came out, totalling 110.4 m². Program in, program out, countable in the file.
What does not transfer
Now the part that a BIM manager needs to hear before anyone in the office says “the AI did the model”.
Families and types. IFC has no concept of a Revit family. Imported walls are generic walls with a thickness; imported doors are generic doors with an opening size. Your office’s Ext_Timber_Clad_250 wall type is not in the file and cannot be. Expect to swap.
Wall build-ups and materials. Nuit’s exporter can write IfcMaterialLayerSet where the model declares layers, but the published example files carry no material assignments. Cladding is exported as separate IfcCovering elements rather than as a layer in the wall. Materials in the sense of your BIM library are a design development task.
Type objects and shared parameters. There are no IfcWallType, IfcDoorType or similar type objects in the file, and no project-specific parameters. Every element is an instance with its own properties.
Multiple storeys. One IfcBuildingStorey. A two-storey concept would arrive on one level. This is the most significant current limit and is stated plainly on the product page.
Anything the concept did not decide. Fire ratings, U-values, acoustic ratings, structural sizing, services. Most elements carry no property set at all, only quantities. The file is honest about what it does not know.
Level of development. Think of it as LOD 200 in geometry and classification, with LOD 100 information content. It is a concept model in a BIM container.
The workflow that holds up
1. Settle the concept before exporting
Export is free and unlimited, but importing five versions of a concept into Revit is a week wasted. Do the exploring in the AI tool, where an edit costs 5 to 25 credits or nothing at all (sliders and direct manipulation are free; the full price list is on the 3D page) and every edit is a checkpoint you can branch from. Compare the branches side by side. Export the one the client approved.
For the images side of the same project, AI + Revit and Archicad: Where AI Fits in a BIM Pipeline covers concept images and where they sit in the BIM process.
2. Link before you open
Revit. Use Link IFC rather than Open IFC for the first look. Revit creates an intermediate RVT from the IFC and links it; the concept sits in your project as a reference you can measure, section and trace, and reload if the concept changes. Once the design is agreed and you want editable elements, Open IFC converts the file into a Revit project with generic families you can develop in place.
Archicad. File → Open an IFC, or place it as a Hotlink module. Archicad maps classes to its tools where the geometry allows (extrusions become walls, slabs, columns) and brings mesh geometry in as morphs. Check the IFC translator settings; the default translator handles a standard IFC4 file, but if your office has a custom one, use it for consistent classification.
3. Check the import against the exporter’s own report
Before looking for problems in the geometry, read what the file says it contains: element counts per class, the number of spaces, the linked openings. The examples page prints these for the published files. If your import shows 12 walls and the file says 12 walls, the classification survived. If your import shows 12 generic models, your translator or category mapping needs attention, not the file.
4. Swap, do not rebuild
The productive move is to select the imported generic walls, apply your office wall type, and let Revit or Archicad re-host the openings. Because the openings are related to walls in the file, most hosting survives the swap. Rooms are already there with names; they only need your room tags.
5. Keep the AI model as the concept record
The IFC is dated, exact and cheap to store. When a client asks in month four why the living room is 56 m², the file answers.
Pitfalls we have seen in IFC imports
These apply to IFC from any source, including ours.
Units and origin. The file is in metres. Revit will convert; check that a 20 m house is not a 20 mm house. The model origin is the site origin in the AI tool, not your project base point; move the link once and pin it.
Mesh elements look editable and are not. An IfcTriangulatedFaceSet wall arrives as a wall category with a mesh body. You can select it and read its properties; you cannot change its thickness with the type editor. Extruded elements can be developed; mesh elements should be replaced. In Mirror Lake, the structural and enclosure elements are mostly extrusions; cladding boards, site and library assets are meshes.
Proxies are not errors. IfcBuildingElementProxy elements (7 in the example, all parts of a wood stove the schema did not cover) come in as generic models with their names intact. Reclassify them if they matter, delete them if they do not.
Coverings inflate the count. 566 IfcCovering elements are cladding boards written individually because the model built them individually. They are correct and they are heavy. Hide the category while working on the plan.
Site geometry. Water, rock and bank surfaces come as IfcGeographicElement. Revit shows them as site or generic; Archicad as morphs. They are useful for the section and useless for topography tools; build your toposurface from the survey.
One storey. Said already; worth saying twice.
When not to bother
If the project is already in Revit and the question is what it should look like, an IFC round trip is the wrong tool. Render from your model, or use an AI render plugin. If the concept is a competition scheme that will be rebuilt from scratch by a different team, an image set is enough. The IFC route earns its keep when the same office carries the concept into schematic design and would otherwise remodel it from pictures. That case is common enough that we built for it.
The companion articles cover the other two exports: AutoCAD + AI for the DXF route and what that DXF contains, SketchUp + AI for GLB, and From an AI Floor Plan to a 3D Model for how the model is generated in the first place.
Frequently Asked Questions
Can an AI concept be opened in Revit?
Yes, when the concept exists as a model with classified elements and is exported as IFC. Revit maps IfcWall to walls, IfcWindow to windows, IfcSpace to rooms. An image opens only as a picture.
What transfers from an AI-generated IFC into Revit or Archicad?
Elements with class, name, placement and geometry; quantities per element; standard property sets; openings related to their walls; rooms with names and areas; the project–site–building–storey hierarchy. Extruded solids where the exporter knows the profile, meshes with correct classes where it does not.
What does not transfer?
Revit families and types, Archicad tool settings, your office’s wall build-ups and material library, template parameters. IFC carries what an element is and where it sits, not the authoring logic. Swap for your own types once the design settles.
Should I open or link an IFC in Revit?
Link first, as a reference that can be reloaded. Open once the concept is agreed and you want editable generic elements to develop in place.
Why do some elements come in as generic models or morphs?
Their class is outside the exporter’s schema (written as IfcBuildingElementProxy with the element name kept) or their geometry is a mesh rather than an extrusion. Both are correct behaviour. Mirror Lake House has 7 proxies out of 1,079 elements.
Does the IFC carry multiple storeys?
Not yet. One building storey; every element sits on it. Split by level after import or use the file as a massing reference until multi-storey export ships.
Is this a BIM model or a concept model?
A concept model in a BIM container: real classes, quantities and relations, exact geometry, early-schematic level of development. It saves remodelling; it does not replace design development.
Try Nuit free — 300 credits (12 images), no card required. Open the Mirror Lake House IFC4 file in Revit or Archicad first, then request 3D access from the Images | 3D switch in the studio. Start your project →