8 Common IFC Validation Errors (and How to Fix Them)

IFC (Industry Foundation Classes) is the universal exchange format for BIM data — but IFC files break in surprisingly common ways. A model that opens perfectly in Revit might fail to import into Navisworks. A file that displays correctly in one viewer might show only half its elements in another. A model that works fine on screen might refuse to appear at all when exported to GIS.

Most of these problems come from a small set of validation issues that are easy to detect and often easy to fix — if you know what to look for. This guide walks through the 8 most common IFC validation errors, why they happen, and exactly how to resolve them at the source.

If you'd like to check a specific file against these issues right now, our free Cloud IFC Validator runs all 8 checks in seconds — no signup required.

1. File Won't Parse (Corrupt or Truncated)

Symptom: The IFC file loads for a moment then throws an error like "unexpected end of file" or "invalid token at line X". Some viewers show a blank scene, others crash silently.

Cause: Almost always an incomplete write — the export process was interrupted (application crash, disk full, network drop during cloud sync), or the file was corrupted in transit (email attachment mangled by security scanning, ZIP truncated during download).

Fix: Re-export from source. Verify file size matches what you expected (a 200-element model shouldn't be 3 KB). If the file was emailed, try again as a ZIP or via a file-sharing service like WeTransfer that preserves binary integrity. If a specific line number is referenced, opening the file in a text editor to check the last few lines often reveals whether the STEP header (ENDSEC;END-ISO-10303-21;) is intact.

2. Wrong Schema Version

Symptom: The file opens but many elements are missing, or specific tools reject the file citing "unsupported schema".

Cause: IFC has several major versions in active use: IFC2X3 (widely supported, older), IFC4 (current mainstream), and IFC4X3 (newer, adds infrastructure). Some downstream tools only support certain versions. Exporting as IFC4X3 when the recipient expects IFC2X3 causes silent failures.

Fix: Check what schema your project requires before exporting. In Revit, choose File → Export → IFC and pick the correct version from the "IFC Version" dropdown. In ArchiCAD, use File → Save as → IFC and select the schema explicitly. When in doubt, IFC2X3 has the broadest compatibility but lacks some modern features.

3. Missing IfcProject Entity

Symptom: Every viewer reports "invalid file" or "no project found". Some tools crash outright.

Cause: Every valid IFC file must contain exactly one IfcProject entity that acts as the root of the spatial hierarchy. Without it, the file is technically invalid per the IFC schema. This usually happens with hand-edited files or exports from misconfigured tools.

Fix: Re-export from your BIM authoring tool — the IfcProject is created automatically during a proper export. If the file was hand-edited, restore from a backup version before the edit.

4. Broken Spatial Hierarchy (Missing Site, Building, or Storey)

Symptom: Elements exist in the file but aren't organised by floor. The 3D viewer works but the spatial tree is empty or shows only orphan elements. Filtering by storey returns nothing.

Cause: IFC expects a specific structure: IfcProject → IfcSite → IfcBuilding → IfcBuildingStorey → Elements. Elements should be linked to a storey via IfcRelContainedInSpatialStructure. When this chain breaks (usually because elements were exported without their spatial context), viewers show geometry but no navigation structure.

Fix: In Revit, ensure all elements are on a defined level before exporting. In ArchiCAD, check that all stories are enabled in the export settings. Use Structure Browser or similar to verify the hierarchy is complete before export.

5. Missing GlobalIds

Symptom: Custom attributes attached to elements disappear after a model re-import. Links from external systems (project management, GIS, custom BIM tools) suddenly point to nothing.

Cause: Every IFC element should have a stable GlobalId — a 22-character identifier that persists across exports and re-exports. Some exports produce elements without GlobalIds, or regenerate GlobalIds on every export (breaking references from any external system that tracked those IDs).

Fix: In Revit, ensure "Use Type Guid for IfcType" and related options are set in the IFC export configuration. In ArchiCAD, keep the "Preserve GUIDs" option enabled. If a downstream tool tracks elements by GlobalId (like Bimvue's custom attributes), avoid workflows that regenerate GUIDs — such as round-tripping through certain converters.

6. Duplicate GlobalIds

Symptom: Some elements silently disappear when the model is imported into another tool. Element counts don't match between viewers. Custom attributes appear on the wrong element.

Cause: Two or more elements share the same GlobalId. This usually happens after a bad merge of two models, an export bug in the authoring tool, or a hand-edit that duplicated an entity block. Most tools handle duplicates by keeping only the first occurrence — which means silent data loss.

Fix: If duplicates come from a merge, redo the merge with a tool that regenerates GUIDs for conflicting entities. If they come from an export bug, update your BIM authoring tool to the latest version. A dedicated IFC editor can renumber duplicates manually if needed — but this should be a last resort, since it breaks any external system that tracked the old GUIDs.

7. Missing Georeferencing

Symptom: The model shows correctly in 3D viewers but cannot be placed on a map. Attempts to export to GIS (ArcGIS, QGIS) produce a feature at coordinates (0, 0). Model federation across sites fails to align buildings correctly.

Cause: The file lacks either IfcMapConversion (the IFC4+ standard way to declare real-world coordinates) or lat/lon values on the IfcSite entity. Without either, the model has no way to say where in the world it is.

Fix: In Revit, use Manage → Location → Site to set project coordinates before exporting, and enable "Site Location" in the IFC export settings. In ArchiCAD, set the project location under Options → Project Preferences → Project Location. For projects requiring precise georeferencing (survey control, GIS integration, infrastructure), configure the survey point and use IFC4 with IfcMapConversion for millimetre-accurate positioning.

8. Zero or Unrealistic Entity Counts

Symptom: The file opens without errors, but element counts don't match expectations. A model that should have 500 walls shows 3. A structural model has zero beams. A federated file appears empty in some tools.

Cause: The export excluded categories that should have been included — either through explicit filter settings or a category that the authoring tool doesn't map to IFC by default. Common examples: MEP elements missing from an architectural export, structural framing missing from a coordination model, rebar (IfcReinforcingBar) excluded because of file-size concerns.

Fix: Compare the entity counts in the IFC file against your source model's element counts. In Revit's IFC export settings (IFC Options), verify all needed categories are checked. In coordination workflows, agree on an entity inclusion checklist with all parties before exporting.

Preventing These Errors at Export Time

Most IFC validation errors are far cheaper to prevent than to fix later. A five-minute checklist before every export catches 80% of these issues:

Verify schema version matches the receiving project's requirement
Check spatial hierarchy is intact — all elements assigned to a storey
Enable "Preserve GUIDs" or equivalent setting
Set project location if the model will feed into GIS or federated coordination
Review IFC export categories — are the right entity types included?
Compare source vs export counts for at least walls, doors, and levels
Validate before sending — run the exported file through a validator to catch anything you missed

Run All 8 Checks in Seconds

All 8 checks described above are automated in our free Cloud IFC Validator. Drop your IFC file, get a report in a few seconds. No signup, no install, and your file is deleted from our servers immediately after the check runs.

The validator won't fix your file for you, but it will tell you exactly which of these 8 issues (if any) are present and give plain-English guidance for each. Use it as a quick health check before sending an IFC to a client, importing to a new tool, or federating with other trades.

When to Escalate

Some IFC problems go beyond simple validation. If you're seeing:

Geometry that displays incorrectly (missing faces, inverted normals, wrong scale)
Property sets that convert incorrectly between tools
Coordinate mismatches between models from different disciplines

…you may need a full model coordination review rather than just validation. These are workflow issues, not file issues — usually solved by aligning BIM execution plans across teams before models are exchanged, not by fixing files after the fact.

Related reading: