“The IFC I was sent won’t open.” “It opened but the screen is blank.” “The windows are all gone.” “The properties are empty.” Problems like these are routine in IFC exchange — but most of them are not corrupt files. They are known mismatches in units, coordinates and export settings. Once you can read the symptom, the fix is usually a settings change or a check in a different tool.
- Most IFC trouble is not corruption — it's units, coordinates or export settings.
- First identify the symptom, then check whether a different viewer shows the same thing (tool-vs-file isolation).
- “Blank / far away / 1000×” is almost always coordinates or units. “Missing elements / empty properties” is almost always export settings.
Start by guessing from the symptom
Before digging in, narrowing down by symptom is faster. Use the table below to get a hunch, then jump to the relevant section.
| Symptom | Common cause | First thing to try |
|---|---|---|
| Won’t open / freezes / times out | File too large / heavy geometry | Open in a lighter viewer, split, check element count |
| Opened but blank / nothing shows | Geometry not read / off-screen | Press “Fit / Zoom to fit”, check in another viewer |
| Specific elements missing (windows, doors) | Missing hosting relationship or geometry | Check export scope and element types |
| Properties / quantities empty | Property sets not exported | Turn on “export properties” |
| Dimensions 1000× / tiny | Declared unit vs actual data mismatch | Check export units, verify in another tool |
| Position off / floats far away | Coordinate system / origin / survey coords | See the coordinates article |
| Garbled text | Non-UTF-8 encoding | Check export character encoding / language |
| Wrong storey / element on another floor | Spatial-structure assignment | Check the Site / Building / Storey tree |
Won’t open, heavy, times out
Large IFC files (tens to hundreds of MB, hundreds of thousands of elements) can fail to load or hang in some tools. IFC represents 3D shapes as many small triangles, so the more elements, the heavier both the processing and the display.
- Suspect element count / file size first. If it’s extreme, you need a tool built for that scale.
- Try a lighter (e.g. browser-based) viewer. The how to open an IFC for free guide lists options.
- Ask for it split. Rather than one file with architecture + structure + MEP, receiving them separately is lighter (you can still overlay them on the receiving side).
- Don’t include what you don’t need. Exporting every piece of furniture and small part bloats the file. Ask for just the scope your task needs.
Opened but blank / nothing shows
Loading finished but the viewer is blank — this is mainly two things.
① The geometry isn't drawn
The shape data failed to load. Blank in another viewer too → suspect the export; blank in only one → suspect that tool.
② It's outside the view
The model sits far from the origin (survey coordinates), outside the initial camera. Press “Fit / Zoom to fit” first.
② is surprisingly common: what looks “broken” is often just far away. Most viewers’ “fit / zoom to extents” finds it instantly. If that still shows nothing, ① is more likely — move on to checking in a different tool. The position issue is covered in detail in the coordinates article.
Specific elements missing (windows, doors)
“The walls are there but all the windows and doors are gone.” This is usually less about the elements themselves and more about the relationships between them being dropped on export. A window or door carries a relationship — which wall and which opening it fits into. If that relationship or the host information is missing, the receiving side can lose track of where it goes and not show it.
The fix is generally on the export side. Review the export tool’s element-type scope (are doors and windows included?) and relationship settings, and re-export. Depending on the receiving tool, some can still pick up and show the raw geometry even when the relationship is missing.
Properties / quantities empty
The 3D shows fine, but clicking an element reveals no properties, and quantities are blank — this is rarely a geometry problem. Almost always, the property sets weren’t included in the export.
- Turn on property export. Most tools have an “export property sets” option; with it off you get a geometry-only IFC.
- Prefer the standard property sets. When a flood of vendor-internal properties is mixed in, the ones that matter (Pset_WallCommon, quantities, etc.) get buried and hard to find.
- Check classification / quantity settings too. Quantities (area, volume, etc.) sometimes need an “export base quantities” option enabled.
Export pitfalls in general are collected in IFC export tips.
Dimensions 1000× or tiny
A wall 2.7 mm tall, or a building blown up to a kilometre — this is a unit mismatch. An IFC declares its length unit (metre, millimetre, etc.) inside the file, but when that declaration doesn’t match the actual coordinate values, the whole model scales by 1000× or 1/1000.
Diagnosing it is simple: compare a wall height or slab thickness against your sense of real dimensions. If a wall is a few mm or a few km, it’s a unit mismatch. The fix is to check the export unit setting and cross-check against another tool that opens the same file. Some tools also let you specify or correct the unit on import.
Garbled text
When element names or property values come through garbled — like “æ–‡å—化㔠— it’s a character-encoding problem. IFC assumes UTF-8, but if the exporting side writes another encoding, the receiving side can’t read it correctly. The fix is to align the export tool’s character encoding / language to UTF-8. It shows up most on projects that use non-ASCII element names.
Wrong storey / element on another floor
“A third-floor wall shows on the second floor,” or “an element isn’t attached to any floor” — this is a spatial-structure (Site → Building → Storey) assignment problem. IFC records which storey each element belongs to via the spatial structure; if that relationship is missing, or a storey’s reference elevation is off, elements attach to the wrong floor or float.
Check the spatial structure
In the viewer's tree, confirm Site / Building / Storey are ordered correctly and each storey contains its elements.
Check storey elevations
Whether each storey's reference height matches the real floor level — an offset misplaces elements and heights.
Fix on the export side
The reliable fix is to correct the spatial structure / storey assignment in the export tool and re-export.
A diagnostic routine when you’re stuck
When the symptom isn’t obvious, work through it in this order.
Open in a different viewer
If the symptom changes it's tool-dependent; if not it's the file (export). Do this first.
Press fit-to-view
Most “blank” cases are just far away. Fit brings the model back on screen.
Compare dimensions to reality
Are wall height / slab thickness sane? Wrong magnitude → units; wrong position → coordinates.
Revisit export settings
Missing properties/elements: fix the export tool's settings (properties, scope, units) and re-export.
Prevention is the best cure
Getting it right at export time is ultimately faster than fixing it on receipt. Open the file yourself once before sending, be deliberate about units / properties / scope — that one step prevents most handover accidents. Export tips are in IFC export tips, and position drift in the coordinates article.
Summary
- Most IFC trouble is not corruption — it’s units, coordinates or export settings.
- Your first move is to open it in a different viewer (tool-dependent vs file-dependent).
- Blank → fit-to-view first, wrong scale → units, wrong position → coordinates, missing elements/properties → export settings.
- The root fix is usually on the export side. Prevention (checking before you send) pays off most.
An IFC that won’t open isn’t necessarily broken. Each symptom maps to a known kind of cause, so with a hunch and a bit of isolation you can usually resolve it calmly. The basics are in what is IFC.