IFC File Analyzer
Get a fast, complete picture of what an IFC file actually contains before you open it in anything heavier.
Drop your IFC here
or
Large models work best on a desktop browser. Files above roughly 500.0 MB may exceed browser memory.
How it works
- 1Select an IFC file. It is read from your disk by your browser and goes no further.
- 2The header, spatial structure and every entity are read locally in a background thread.
- 3You get the schema, project details, counts, discipline clues and the full hierarchy.
- 4Download the whole analysis as JSON if you need to keep or share it.
About IFC File Analyzer
When an IFC lands in your inbox, the first question is rarely about geometry. It is what am I actually looking at? Which schema, from which tool, covering which building, structured how.
Opening a large model in an authoring application to answer that costs minutes and a licence seat. Reading the header and counting entities costs seconds, and answers most of it.
The spatial structure is worth particular attention. IFC expects everything to hang beneath IfcProject, IfcSite, IfcBuilding and IfcBuildingStorey. When that hierarchy is missing or shallow, filtering by level stops working downstream, and the problem is far cheaper to catch here than after the model is federated.
Everything reported is a description of the file. It is not a quality score and not a compliance statement. If you want checks with an opinion attached, use the IFC Model Health Checker.
Questions
- Is my IFC file uploaded anywhere?
- No. The file is read by your own browser using a WebAssembly IFC parser. The model is never sent to FreeBIMTools or anywhere else, and there is no upload endpoint for it.
- How do I tell which IFC version a file uses?
- The schema is reported at the top of the overview, usually IFC2X3 or IFC4. It comes from the FILE_SCHEMA entry in the file header. This matters because some receiving tools accept only one of them, and property set names differ between versions.
- What does the authoring application tell me?
- It is the tool that wrote the file, taken from the IFC header. When an exchange goes wrong it is often the first useful clue, because export quirks tend to be specific to one exporter and version.
- Why does it say no spatial hierarchy was found?
- A well-formed IFC nests everything under IfcProject, then IfcSite, IfcBuilding and IfcBuildingStorey. Some exports flatten or omit that structure. It is worth knowing, because most downstream tools rely on the hierarchy to place and filter elements.
- Are the discipline clues reliable?
- They are hints, not a classification. They come from which IFC classes are present, so a model containing ducts is flagged as mechanical. A file can carry several disciplines, and a poorly classified export may show none.
- Can it read a Revit .rvt file?
- No, and no browser tool honestly can. RVT is a proprietary format that needs Revit itself. Export an IFC from Revit and this tool will read it.
Was this useful, or is something missing? There is no rating widget here, because a thumbs up with nowhere to go is not feedback. Tell us what IFC File Analyzer should do, and describe the job rather than the feature.