Getting clean IFC exports from Revit doesn’t have to feel like magic.
This article is based on my recent live webinar with Leila Secerbegovic, Product Manager and Revit interoperability expert at Autodesk.
Together, we explored the most common IFC export mistakes, and Lejla showed practical solutions, and we discussed how to properly set up IFC workflows in Revit 2023–2026.
We won’t cover every feature and option in the IFC exporter. Instead, this article focuses on the essential practices and key concepts Leila emphasized during our session.
If you’ve struggled with messy IFCs, geometry that lands in the wrong location, or properties that mysteriously disappear during export, this guide will help you fix those issues.
Why IFC exports break (and how to stop it)
Most people treat IFC export as a one-click operation.
They hit Export → IFC, expect a miracle, and then spend hours wondering why the geometry looks strange or the data didn’t show up.
The truth is simple: Revit will only export what you’ve told it to.
If the IFC schema, mapping, or view setup isn’t right, Revit won’t guess your intentions.
To get consistent, clean results, first you need to take control of 4 key categories:
- The schema you’re using (IFC2x3, IFC4, or IFC4.3) and understanding the basic components and how they are organized
- The mapping rules that tell Revit how to translate elements
- The views and filters defining what is actually exported
- The IFC exporter settings and how they affect your exported file
Set up once, export clean every time
You don’t need to reinvent your settings for every project. Set it up properly once and reuse that structure.
Start with these basics:
1. Choose the right schema.
IFC2x3 is still the most widely used, but IFC4 and 4.3 bring better structure and support for infrastructure. If you’re working on roads, bridges, or tunnels, IFC4.3 is the way forward.
Not familiar with IFC 4.3 ?
Here is a great article Marcin from BIM Corner team is going deep into IFC 4.3 – https://bimcorner.com/ifc-4-3-for-infrastructure/
2. Understand difference between linking vs opening the IFC files
This confusion causes a lot of problems. General rule is:
Link IFC files for coordination. When you link an IFC, Revit uses the translation framework to create a reference model. You can update the link whenever you receive new files, and the geometry stays clean.
But you cannot edit linked IFC geometry, which is actually a good thing for coordination purposes.
Opening IFC files should be avoided in most cases. When you open an IFC, Revit tries to recreate native Revit elements, which works fine for simple walls but quickly breaks down with complex geometry. If you absolutely must open an IFC file, use IFC 2×3 Coordination View rather than IFC4 Reference View, which was designed specifically for linking, not opening.
When you link an IFC, Revit automatically creates an IFC.rvt file and a shared parameters file in the same folder. These are useful if you need to tag or schedule IFC elements in your project.
3. Update your category mapping.
Since Revit 2025, category mapping is part of the main export setup.
You can now select IFC classes and types directly from a dropdown instead of typing them manually.
That one improvement saves hours and eliminates spelling mistakes that used to break exports.
When this setup is done once, you can reuse it as a company standard. You just simply go to File – Export – IFC.
In the export IFC window you hit Modify Setup and then in General tab you have Category Mapping – Use 3 dots … to open new window when you can manage mapping of Revit categories with IFC entities easily. 👇
Element-level control: the hierarchy that actually matters
Many people don’t realize that Revit follows a strict hierarchy when deciding what to export.
Here’s how it works:
- Global category mapping defines the default behavior. Tells Revit, ok we are going to map this Revit category with this IFC entity (class). You can set it up as I described above.
- Export view filters what’s visible. You create a specific view in Revit that includes all the elements that you would like to export to IFC. Then in the exporter setting in Additional Content section you choose option – Export only elements visible in the view
- Type settings define what should happen to all elements of one type.
- Instance settings override everything else.
The last one always wins. Let’s say you’ve globally set floors to export as IFC Slabs.
But for one specific floor finish, you change the instance property “Export to IFC” and select IFC Covering instead.
Revit will follow the instance setting and export that element differently. It’s like giving Revit your final instruction right before export.
Use this control wisely, especially when you mix floors, finishes, or MEP equipment that need different classifications.
Levels and spatial structure that make sense in viewers
This is one of the easiest things to fix and also one of the common mistakes.
When exporting IFC, Revit includes only the levels that are marked as Building Story.
If you skip this step, your IFC file will show random “level 1, level 2…” structures, sometimes these that might be just a reference level in Revit model. So the recommendation here is to create a level schedule in Revit.
Mark only the real building stories as Building Story = Yes and then leave working or reference levels unchecked.
If an element sits on a level that isn’t a building story, Revit will push it down to the next story below. That’s called the fall-down behavior and it’s why your geometry sometimes ends up on unexpected levels.
For infrastructure or horizontal projects, go one step further. Use the IFC Spatial Container parameter. It lets you manually assign bridges, roads, or tunnels as logical “containers” for your elements. That way, your IFC structure stays logical even when the project isn’t vertical.
Property sets that travel
Every IFC file carries properties but not all properties travel equally well.
There are two main categories:
- Common Property Sets (Psets) – standardized by the IFC schema.
- Custom (user-defined) Property Sets – created for your project or company needs.
Always export the common Psets first.
They’re like the passport data of your model readable by any software.
For example, Pset_WallCommon defines thickness, fire rating, and load-bearing status.
If a property from that list is missing, it’s usually because:
- It has no value assigned in Revit, or
- The property doesn’t exist in your model at all.
To fix it, you can create a matching Revit parameter with the same name and data type.
Use Label for text, Boolean for yes/no, and Real for numeric values.
When the name and data type match, Revit automatically maps them.
If you want to go further, create custom Psets using the mapping file.
It’s a simple text file where each line defines the Pset name, property name, and Revit parameter name separated by tabs. Since the topic is a bit complicated I created a separte article about it.
Read it here: https://bimcorner.com/exporting-ifc-from-revit-part-3-user-defined-properties/
What’s new in Revit 2023–2026 (and why it matters)
Autodesk has been quietly improving IFC support in every release.
These are the updates that change your workflow and it simpler.
Revit 2023
- Introduced Export to IFC parameters at type and instance level.
- Added dropdowns for IFC Class and Type selection.
- Cleaned up shared parameters and added them to the Parameter Service on ACC.
Revit 2025 – Mentioned earlier
- New Category Mapping tab inside the export setup.
- You can import, export, and reset mapping templates without text files.
- Category exclusions and subcategories are easier to manage.
Revit 2026
- Linking IFC files is now twice as fast.
- You can choose the origin point (Internal, Project Base Point, or Survey Point).
- Geometry distortion from real-world coordinates is finally fixed.
You can learn more about in my latest article:
https://bimcorner.com/linking-ifc-to-revit-2026/
Final thoughts
Getting IFC exports right isn’t about knowing every checkbox in Revit.
It’s about understanding how Revit thinks and teaching it how to behave consistently.
Once you set up your schema, mapping, and templates, the workflow becomes repeatable.
Clean IFCs stop being luck they become your standard.
In our webinar, Leila shared one powerful line that sums it up perfectly:
“When you know what you want to export and how to control it, Revit becomes predictable.”
And that’s the goal.
Predictable, reliable exports that save time, reduce rework, and make coordination smoother for everyone on the project. So take an hour, set it up once and enjoy clean IFCs for years to come. If you would like to watch the reply of this session, please use this link below.
https://becomebimcoordinator.com/w/ifc-export-from-revit/
Interactive BIM Coordination guide full of tips, graphs, mind maps, and practical exercises. It will teach you the basics of BIM Coordination. All for free.
