Top 7 Tips to Improve IFC Exports from Revit with the IFC Exporter

IFC Exporter for Revit: Complete Guide to Settings & Best PracticesThe IFC (Industry Foundation Classes) format is the backbone of open BIM workflows. Revit’s IFC Exporter enables accurate exchange of building information with consultants, contractors, facilities managers, and other BIM tools. This guide walks through the exporter’s settings, common pitfalls, and practical best practices to produce reliable, interoperable IFC files.

Why IFC matters

IFC is an open, neutral data format developed by buildingSMART to enable interoperability between BIM applications. Unlike proprietary formats, IFC preserves geometry, classification, relationships, properties, and metadata in a standardized schema. Correct IFC export from Revit ensures downstream tools can read the model for coordination, analysis, costing, and facilities management.

Which IFC version to use

Choose the version based on recipient requirements and target applications:

IFC2x3 Coordination View (commonly IFC2x3) — widely supported by older tools. Use when recipients require IFC2x3.
IFC4 — recommended when possible. IFC4 improves geometry handling, richer property sets, better units, and enhanced support for spaces and materials. Many modern tools and workflows prefer IFC4 (Reference View, Design Transfer View, etc.).

Always confirm recipient requirements before export.

Installing and updating the IFC Exporter for Revit

Revit includes a built-in IFC exporter, but Autodesk and buildingSMART periodically release improved exporter add-ins/plugins. Best practice:

Keep Revit and the IFC Exporter updated to the latest compatible versions.
Install the official Autodesk IFC exporter add-in when specific fixes or features are needed (check release notes).
Test exports after updates to spot behavior changes.

Pre-export model preparation

Effective IFC export starts in the Revit model. A tidy model reduces errors and increases usefulness of the IFC file.

Clean up unnecessary model elements (in-place families, unused detail items).
Purge unused families, types, and parameters.
Use worksets and linked models intentionally; decide whether to export links or include them manually.
Ensure element categories are correct (walls, floors, roofs, doors, windows, coverages).
Verify levels and grids are consistent.
Coordinate shared coordinates if exporting multiple linked files to maintain position.

Revit-to-IFC mapping and classification

IFC is class-based (IfcWall, IfcDoor, IfcSpace, etc.). Revit categories map to IFC classes via the exporter configuration.

Review category-to-IFC mappings in the exporter settings.
Use the built-in Revit parameters (e.g., Type Name, Comments) and custom shared parameters to populate IFC property sets.
For compliance with COBie or client schemas, map Revit parameters to the correct IFC property sets (Psets).
Consider using classification systems (Uniclass, Omniclass, MasterFormat). Store classification values in parameters like “OmniClass Number” and map them in export configuration.

Export settings — walkthrough

Open the IFC export dialog (File > Export > IFC or via the Exporter add-in) and configure these key areas.

General

File format: Choose IFC4 where possible; fallback to IFC2x3 if required.
Export setup: Use a named setup for consistent, repeatable exports across projects.

Include/exclude

Export links: Choose whether to export linked Revit files. If exporting links, ensure shared coordinates are correct.
Site and topography: Decide whether to export site elements. For coordination, include them; for separate deliverables, exclude.

Geometry and Tessellation

Use “Export solids as BRep” where target software supports BReps to preserve precise geometry. If BReps cause file size/performance issues, export as tessellated geometry (mesh).
Adjust tessellation quality if applicable — higher quality improves accuracy but increases file size.

Property Sets & Parameters

Include Default property sets: keep them unless you have a custom Pset strategy.
Export user-defined parameters: ensure important shared parameters are checked so they become IFC properties.
COBie: enable/export COBie if COBie deliverable is required; map fields accordingly.

Level of Detail (LOD)

Revit doesn’t directly export LOD labels, but control detail by which families/types are used and whether symbolic/detail-only elements are included.
Exclude 2D-only detail items to avoid noise.

IFC Entity Mapping

Adjust mappings for specific categories (e.g., map special family categories to IfcMember, IfcFurnishingElement).
For complex families, ensure the family category is set correctly so the exporter maps it properly.

Coordinate systems and Units

Use shared coordinates when coordinating multiple files.
IFC stores units; verify unit settings (metric vs imperial) to ensure correct interpretations in downstream software.

Handling Revit families and geometry

Families are the most common source of IFC export issues.

Use native Revit family categories (Doors, Windows, Mechanical Equipment). Custom categories can map poorly.
Avoid using overly complex geometry (excessive voids, nested families) for large/commonly shared elements.
Use type parameters for repeated information rather than instance parameters where appropriate.
For elements that must be represented simply in IFC (e.g., furniture for coordination), create simplified representation types within the family.

Spaces, Rooms, and Zones

Accurate spaces are crucial for area/volume calculations and MEP coordination.

Ensure rooms/spaces are placed and bounded correctly.
Map rooms to IfcSpace during export; verify names, numbers, and area/volume parameters populate IFC attributes.
For thermal or energy workflows, include required properties for zones and spaces (e.g., occupancy, usage type).

MEP and Systems

MEP elements need careful handling for connectivity and systems.

Use system names and ensure connectors are properly modeled.
Use the MEP connector framework so that IFC export can preserve system relationships (e.g., ducts, pipes, electrical circuits).
For analytical purposes, verify the export includes IfcFlowSegment, IfcFlowFitting, and IfcDistributionSystem where applicable.
Consider splitting large, complex MEP families into simpler elements to improve interoperability.

Textures, materials, and information fidelity

IFC supports materials and surface appearance, but support varies by software.

Use Revit materials and specify material names, descriptions, and physical properties.
Map materials to IfcMaterial in the exporter settings.
Don’t rely on textures for critical identification — use material names and properties instead.
Be aware that some viewers ignore textures; ensure key metadata is stored in parameters.

Troubleshooting common issues

Missing elements in target software: check category-to-IFC mapping and whether elements were set to not export (e.g., turned off in view/template).
Incorrect placement: verify shared coordinates and base points; consider using “Publish Coordinates” workflows.
Large file size or poor performance: switch to tessellated geometry with lower detail, remove unnecessary detail items, or split the model.
Lost property data: confirm shared parameters are included in the export setup and mapped to IFC Psets.
Families exported as “IfcBuildingElementProxy” or generic classes: set correct Revit category and adjust mapping configuration.

Validation and QA of IFC files

After export, always validate the IFC file:

Use IFC viewers (e.g., Solibri, BIMcollab Zoom, IfcPlusPlus, simple online viewers) to visually check geometry and properties.
Run model checking rules (Clash detection, Pset completeness, required fields).
Use validation tools (IfcChecker, buildingSMART’s Validation tools) for schema conformance.
Ask recipients to confirm they can open key objects, spaces, and property data.

Automation and repeatability

Save a named export setup for each project and share it with the team.
Use Dynamo or Revit API scripts to set or populate IFC-related parameters consistently before export.
Automate pre-export checks (e.g., ensuring all rooms have names/numbers, shared parameters populated).

Collaboration and delivery tips

Agree on an IFC delivery brief with project stakeholders: required schema (IFC2x3 vs IFC4), required Psets, required objects and level of detail, coordinate system, and COBie or other data expectations.
Provide example IFC files early to validate the workflow.
For federated models, decide whether each discipline exports separate IFCs or a combined federated IFC will be produced.

Quick checklist before export

Confirm required IFC version with recipients.
Clean model: purge unused, remove 2D-only details.
Verify categories and family types.
Populate shared parameters and classification values.
Set shared coordinates and levels.
Choose named export setup and test small exports first.
Validate exported IFC with a viewer and run rule checks.

Conclusion

Producing reliable IFCs from Revit requires attention to model discipline, exporter settings, family design, and clear project agreements. Use IFC4 where supported, keep the model clean and well-classified, include required property sets, and validate exports before delivery. With consistent setup and testing, IFC exports become a dependable part of an open BIM workflow.

If you want, I can:

Create a downloadable export checklist formatted for project handovers.
Generate a sample Revit-to-IFC export setup (step-by-step) for IFC4 with recommended parameter mappings. Which would you prefer?