How to Export IFC from Revit: Step-by-Step (2026)
How to export IFC from Revit for BIM coordination and interoperability — step-by-step export settings, MVD/schema choice, and the common gotchas that break a handover.
How to Export IFC from Revit: Step-by-Step (2026)
Direct answer
A step-by-step guide to exporting a coordinated IFC file from Autodesk Revit, with the mapping settings and common gotchas that trip up handovers.
Key facts
| Metric | Value | Notes |
|---|---|---|
| Menu path | File → Export → IFC | R menu / File tab |
| Common schema | IFC 2x3 Coordination View 2.0 | widest tool support |
| Newer schema | IFC4 Reference View | check partner support first |
| Controls what exports | IFC export setup + category mapping | saved per project or shared |
Before you export
IFC (Industry Foundation Classes) is the open buildingSMART format used to hand a model to consultants, clash-detection, and review tools that are not on Revit. A clean export is mostly about preparation, not the export button.
- Agree the target with the receiving party — schema (IFC 2x3 vs. IFC4), Model View Definition, coordinate system, and units.
- Build a dedicated 3D view containing only the categories, phase, and worksets you intend to share.
- Confirm shared coordinates so the file lands in the right place in a federated model.
The IFC exporter is an Autodesk add-in that updates independently of Revit. Options and labels vary by version and exporter build — the steps below are the general flow.
Step-by-step
- Open the coordination 3D view you prepared and make it the active view.
- Go to the File tab (or R menu) → Export → IFC.
- In the IFC export dialog, set the Current selected setup, or click Modify setup to create one.
- On the General tab, choose the IFC Version / schema (e.g. IFC 2x3 Coordination View 2.0) and the file type (IFC, IFC XML, or zipped IFC).
- On Additional Content, decide whether to export linked files, only elements visible in the view, and 2D plan elements.
- On Property Sets, enable the base quantities and any custom or user-defined property sets your recipient needs.
- On the Advanced tab, review options such as exporting parts as building elements and using the active view's phase.
- Check the category mapping (IFC export classes) so each Revit category maps to the correct IfcEntity — this is where elements go missing or misclassified.
- Click Export, then open the result in a free IFC viewer and spot-check geometry, classification, and placement before you send it.
Common gotchas
| Symptom | Likely cause |
|---|---|
| Elements missing | Category set to Not Exported in the mapping, or hidden in the view |
| Wrong IFC class | Category mapped incorrectly, or a bad IfcExportAs parameter on a family |
| File lands in wrong location | Shared coordinates not set / internal origin exported instead |
| Bloated file | Whole model exported instead of a filtered coordination view |
| Missing data | Required property sets not enabled in the setup |
After export
Always round-trip check the file in a neutral IFC viewer before handover — what Revit thinks it exported and what the recipient opens are not always the same. Save your export setup with the project so the next issue is identical and repeatable.
Frequently asked questions
Which IFC schema should I export — IFC 2x3 or IFC4?
IFC 2x3 Coordination View 2.0 remains the safest choice for general coordination because nearly every reviewer and clash tool reads it reliably. IFC4 (Reference View or Design Transfer View) carries richer geometry and data but support is uneven across downstream tools. Agree the schema and Model View Definition with the receiving party before you export — do not assume.
Why are some elements missing or wrongly classified in the IFC?
IFC export is driven by category-to-IfcEntity mapping. If a Revit category is set to Not Exported in the mapping table, those elements are dropped; if it maps to the wrong IFC class, they arrive misclassified. Open the export setup, check the category mapping, and make sure IfcExportAs parameters on families or the Export Type table are correct. Model-in-place and generic elements are the usual offenders.
Should I export the whole model or a coordination view?
Export a purpose-made 3D view. Use a dedicated coordination 3D view with only the categories and phase you intend to share, links handled deliberately, and worksets set. This keeps file size down, avoids leaking work-in-progress, and gives you a repeatable, reviewable export rather than dumping the entire model.
Source & method: Compiled from official Autodesk Revit documentation (IFC export) and the buildingSMART IFC standard. Revit's IFC exporter ships as an Autodesk add-in; menus and options vary by version and by the installed exporter build. Confirm against your release.