What is IFC?
IFC is not just a generic BIM file extension. At its core it is a standardized data schema that describes objects, their properties, and their relationships in the built environment. That includes physical elements such as walls, slabs, and systems, but also attributes, locations, connections, ownership, processes, schedules, and other project information.
Why was IFC created?
The main purpose of IFC is interoperability. In AEC workflows, project teams often use different authoring, coordination, analysis, and viewing tools. IFC provides a common structure for exchanging data between those systems without tying the project to a single software vendor. That is why IFC is closely associated with openBIM workflows.
Is IFC a file format?
Not exactly. IFC is often treated as a file format because users usually receive it as an .ifc file, but the standard is broader than that. buildingSMART states that IFC data can be serialized in several forms, and that IFC itself is primarily a data schema for organizing objects, properties, and relations.
| Serialization |
Description |
| .ifc |
STEP Physical File Format; the recommended exchange format for IFC 2x3, IFC 4, and IFC 4.3 |
| .ifcXML |
XML-based serialization of the same schema |
| .ifcZIP |
Compressed container holding an .ifc or .ifcXML file |
What kind of information can IFC contain?
IFC can describe much more than model geometry. The schema can represent element identity, machine-readable object types, material and performance properties, spatial structure, ownership, connections, cost-related information, work schedules, and operational data. In other words, IFC exchanges both geometry and semantics, not just shapes.
Which IFC version is current?
According to buildingSMART, the latest official release is IFC 4.3.2.0, commonly referred to as IFC 4.3, published as ISO 16739-1:2024. buildingSMART notes that IFC 4.3 expands support for infrastructure, and that earlier official versions such as IFC 4 and IFC 2x3 are still widely encountered in practice.
Applications and Industry Use Cases
IFC is widely used in architecture, engineering, construction, and operations whenever information must move between different BIM tools or between different project stakeholders. Typical uses include design handoff, coordination, bidding, as-built delivery, long-term archiving, and operations-oriented data exchange. buildingSMART describes IFC as being used both for specific business transactions and for long-term preservation and operations purposes.
IFC is also important in public-sector and regulated workflows. buildingSMART documents multiple national and agency-level mandates for IFC delivery, and notes that IFC is used to promote open, non-proprietary, vendor-neutral exchange in public infrastructure programs.
Challenges or Common Pitfalls
A common mistake is to think that any BIM tool can read and edit IFC in exactly the same way. In reality, IFC implementation is version-specific and often view-specific. buildingSMART notes that software may support only a narrower part of the standard, such as a specific model view definition, so compatibility depends on both the file version and the scope of implementation.
Another pitfall is to treat IFC as if it were only a geometry file. IFC can carry rich semantic and relational information, which means data quality matters. buildingSMART provides an official IFC Validation Service and software scorecards because valid export, correct mapping, and standards compliance are not guaranteed automatically just because a file uses the IFC name.
How Spatial Helps
Spatial handles IFC through its AEC/BIM interoperability technology, so applications can move IFC data in and out of a larger engineering workflow rather than just view it.
3D InterOp reads and writes major BIM and CAD formats, exchanging exact B-rep geometry, tessellated data, and metadata across them. It added IFC write support for AEC applications in the 2022 release line, and more recent updates extend that support to IFC 4.3.2.0.
That matters when IFC is one step in a larger pipeline: BIM import, translation, geometry reuse, and downstream engineering processing. Because 3D InterOp carries both geometry and metadata, an application keeps the semantics that make IFC useful, not just the shapes.