THE FILE FIELD GUIDE
.ifc

IFC BIM Exchange Data

CAD & 3D

IFC is buildingSMART’s BIM exchange standard, representing element identity, properties, hierarchy and relationships as well as geometry. The .ifc suffix commonly uses STEP text encoding; choose software supporting the schema and exchange purpose.

Main use
Exchange built-environment geometry, properties and relationships
Data type
Text data
All sections, questions and sources

Content reviewed: · Editor:Kai

Opening steps

Choose your environment or purpose to see its steps.

IFC-capable BIM software / viewer

Preserve the original and inspect a working copy in a compatible application.

  1. Open a copy in an IFC viewer and inspect its schema version.
  2. Inspect hierarchy, elements, properties and placement.
  3. Link/import into BIM software as required while retaining the source.
Inspect the received file and its requirements

Establish dependencies and settings before proceeding.

  1. Agree on supported schema versions such as IFC2x3 or IFC4.
  2. Specify required properties/classifications and exchange purpose.
  3. Check coordinates, origins, units and storeys.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Nothing visible: inspect zoom extents and coordinates/origin.
  • Properties missing: check exporter property-set settings.
  • Geometry differs: inspect schema, representation and recipient support.
  • Imported model is difficult to edit: it is not identical to the native authoring model.

IFC → supported BIM/CAD / viewing output

  1. Read the required data in compatible software and export the agreed receiving format.
  2. Check element counts, representative properties, placement and units at the recipient.

Authoring constraints, history and all proprietary properties may not be restored.

Exchange information, not geometry alone

Correct appearance can hide missing classifications or identifiers. Agree on required fields and inspect properties on representative elements.

Source for these steps:buildingSMART · Industry Foundation Classes (IFC) / buildingSMART · IFC Formats

Worked example: checks before handoff

Example: for equipment, test identifiers, classifications and required performance fields as well as positions before exporting the complete model.

Source for these steps:buildingSMART · Industry Foundation Classes (IFC) / buildingSMART · IFC Formats

Related-format differences

Related-format differences
Format / methodPurpose and preserved information
.ifcExchange built-environment geometry, properties and relationships
RVT / OBJRVT is a Revit master; OBJ mainly exchanges geometry rather than IFC BIM semantics.
IFC → supported BIM/CAD / viewing outputAuthoring constraints, history and all proprietary properties may not be restored.

Handling and security

Review disclosure of facility layout, locations, equipment properties and ownership/contact information.

Questions and answers

Does renaming it RVT restore a Revit model?

No; IFC exchange is different from the native authoring master.

Are all IFC versions interchangeable?

Schema and implementation support vary; agree on the exchange conditions.

Is matching appearance sufficient?

Also inspect required element types, identifiers and properties.

Format facts: name, steward and MIME type
Formal name
IFC BIM Exchange Data
Steward / specification
buildingSMART
MIME type
Consult the producer or delivery system. The extension alone does not establish a MIME type.

Primary and official sources

  • StandardIndustry Foundation Classes (IFC)

    The standard for exchanging BIM semantics, attributes and relationships.

    buildingSMART · Link checked:
  • StandardIFC Formats

    IFC file encodings.

    buildingSMART · Link checked: