How to delete elements from an IFC without breaking the file
Lightening a model, stripping the furniture nobody needs, cleaning duplicates after a merge or delivering only the contracted scope. All of that is deleting elements from an IFC — and it is where a file gets ruined most easily if done bluntly.
Open my IFC — free See the IFC editor
Why deleting in an IFC is not deleting a line
An IFC is a graph: each element points at its geometry, its materials, its history and the relationships that place it in the building or the alignment. Delete the element's line and everything it references, and you take down things shared by the whole file.
The two classic wrecks:
- Dragging IfcOwnerHistory along. Every entity in the file shares it; if it leaves with the first deleted element, the rest point at nothing.
- Deleting the whole spatial relationship. An IfcRelContainedInSpatialStructure groups every element of a storey or stretch: removing it to drop one column orphans the rest of the floor.
A correct deletion does two things: it counts references — removing only what nobody else uses — and, in IfcRel* entities, it takes the element out of the list while keeping the relationship as long as it still has members.
Step by step
- Open the IFC at geomaifc.com/app. It is processed on your machine, not uploaded.
- Choose what goes: by IFC type, by filter (text, property, chainage range), by GUID list or by selecting in the 3D view, window selection included.
- Preview. The viewer highlights exactly the affected elements — this is the moment to notice the filter caught too much.
- Apply in the session and browse the model without them: table, filters and 3D all update so you can really check.
- Download the IFC. Your original file is never touched.
If you only want to not see them while keeping them in the file, don't delete: isolate or hide in the viewer. Deleting is for what leaves the deliverable.
When to delete and when not to
- Yes: furniture, vegetation and context that multiply weight without helping coordination.
- Yes: duplicates after merging two models from the same source.
- Yes: trimming the model to the contracted scope before delivering.
- No: to "fix" a clash. That belongs in the authoring model; deleting the element in the IFC only hides the problem until the next issue.
- No: as a way to filter for a one-off review — hiding or isolating is enough there.
Frequently asked questions
- Can I see what will be deleted before applying?
- Yes, there is a 3D preview and the deletion is applied in the session first.
- Is my original file modified?
- No: it only changes if you download the result and replace it yourself.
- What if two elements share a GUID?
- All matches are collected, not just the last one — otherwise the Pset was deleted and the element stayed in the model.
- Is it free?
- Opening and reviewing, yes. Deleting is in the paid plans. See plans.
Clean up my IFC now Add properties to an IFC