IFC to Excel converter
Export every property, Pset and quantity in your IFC model to a clean .xlsx — free, instant, and without uploading anything.
Your file is processed locally in your browser. Nothing is uploaded.
Drop your IFC file here
.ifc and .ifczip · IFC2x3, IFC4, IFC4x3
No file at hand? Try a sample: ·
Get your BIM data where the work happens: a spreadsheet
An IFC model is a database wearing a building costume. Inside every wall, door, slab and duct there are dozens of properties — fire ratings, U-values, areas, volumes, classification codes, custom parameters your team added in Revit or ArchiCAD. The problem: the people who need that data (quantity surveyors, cost planners, facility managers, project auditors) usually work in Excel, not in BIM authoring tools. This converter closes that gap in one step: drop an .ifc file, get an .xlsx workbook with one sheet per IFC class and one column per property.
Everything runs locally in your browser. The IFC parser is WebAssembly, the extraction runs in a background thread, and the spreadsheet is assembled on your machine — your model is never uploaded. For confidential tender models or projects under NDA, that is not a nice-to-have; it is the difference between being allowed to use the tool and not.
How it works
- Drop your IFC file. .ifc or .ifczip, exported from any BIM tool. The model is parsed and scanned in seconds — you will see the schema version, the authoring software and the element count per class.
- Pick what to export. All classes with elements are selected by default. Untick what you do not need (say, goodbye IfcFastener), decide whether to include quantity sets, and choose a point or comma decimal separator.
- Download the .xlsx. A Summary sheet documents the file;
each class gets its own sheet with GlobalId, Name, Type, Storey and every flattened
property (
Pset_WallCommon.FireRatingstyle). Opens in Excel, LibreOffice and Google Sheets.
What AEC teams use this for
Quantity takeoff and cost planning. Export Qto_WallBaseQuantities, Qto_SlabBaseQuantities and friends straight into the estimating workbook instead of re-measuring or paying for takeoff plugins. Areas, volumes and lengths arrive as numbers you can sum and pivot immediately.
Model checking and delivery audits. BEP says every door needs a FireRating and an acoustic rating? Sort the IfcDoor sheet by those columns and the blanks reveal themselves in seconds — faster than clicking through elements one by one in a viewer, and the spreadsheet doubles as the audit record you attach to the delivery report.
Facility management handover. Owners rarely want a 400 MB federated model; they want an asset register. Export spaces, doors and MEP equipment with their properties and you have the seed of a COBie-style register without specialized software.
Sharing data with non-BIM stakeholders. Structural engineers checking beam schedules, contractors verifying element counts per storey, clients reviewing room lists — everyone can read a spreadsheet.
Built for real project files
Property extraction is engineered for the models you actually receive: the converter walks the IFC relation graph once (instead of querying element by element), so structural models with hundreds of thousands of entities convert in reasonable time — and because the heavy lifting happens in a background worker thread, the page never freezes while it works. Special characters in property names and values (accents, umlauts, CJK — anything encoded as STEP escapes) are decoded correctly, a detail many exporters get wrong. If you just want to look at the model instead, the free IFC viewer opens the same file in 3D.
Frequently asked questions
Is it safe to convert confidential IFC models here?
Yes. The converter runs entirely in your browser using WebAssembly — your IFC file is never uploaded to any server. There is no copy to store, leak or delete: close the tab and everything is gone. That makes it suitable for models covered by NDAs or tender confidentiality rules.
What data ends up in the Excel file?
Every exported element carries its GlobalId, Name, IFC class, type name and storey, followed by one column per property — property sets are flattened as Pset_Name.PropertyName (for example Pset_WallCommon.FireRating) and quantity sets as Qto columns. A Summary sheet lists the file metadata (schema, authoring software, author) and the element count per class.
Which IFC versions are supported?
IFC2x3, IFC4 and IFC4x3 — the schemas produced by Revit, ArchiCAD, Tekla Structures, Allplan and every other IFC-compliant tool. Compressed .ifczip files are decompressed on the fly.
Is there a file size limit?
No hard limit. Models up to roughly 300 MB work on a typical desktop machine; we show a heads-up above 150 MB. Because the extraction runs in a background thread, the page stays responsive even while processing models with hundreds of thousands of elements.
Can I choose which elements are exported?
Yes. After the model is scanned you get a checklist of every IFC class found (walls, doors, spaces, beams, pipes…) with its element count. Untick what you do not need, choose whether to include quantities, pick your decimal separator, and convert.
Does it work on mobile?
Yes, for small and medium models. Mobile browsers cap memory more aggressively (we warn above 80 MB), so very large files are better converted on a desktop.