BIM data to Excel exporter
Pull every attribute, Pset and quantity out of your model into a clean .xlsx — one worksheet per class, built inside your browser, with nothing uploaded.
Runs on your device — the model is never uploaded.
Drop your IFC file here
.ifc and .ifczip · IFC2x3, IFC4, IFC4x3
No file at hand? Try a sample: ·
- to spreadsheet 118,317 elements out of a 67 MB file
- 10.6 s
- page framerate while a 937,000-entity file exports
- 144 fps
- bytes sent anywhere — the model stays on your machine
- 0
Measured by this site's automated QA suite on real project models — every figure is recorded before it is published.
The model holds the data. The decisions happen in spreadsheets.
Ask a quantity surveyor, a cost planner or an FM handover lead where they actually work, and the answer is rarely a BIM authoring seat — it is Excel. Meanwhile the BIM model sits there holding exactly what they need: fire ratings on every door, volumes on every slab, classification codes, custom parameters the design team filled in months ago. The gap between those two worlds is usually bridged by expensive plugins or by someone retyping values by hand. This exporter closes it directly: one .ifc in, one .xlsx out, with the model's classes split into worksheets and its properties spread into columns.
And it does so without the model going anywhere. Parsing happens inside your browser, powered by WebAssembly, and the finished workbook is assembled on your own machine. For live tenders and NDA projects, that is not a convenience feature — it is what makes using an online tool permissible at all.
How it works
- Drop the model. A .ifc or .ifczip from any authoring tool. Within moments you get the scan result: schema version plus a class-by-class element inventory.
- Shape the export. Every class starts selected; untick the ones that would only add noise to the workbook, and decide whether quantity sets ride along. A takeoff needs the Qto columns — a door-schedule audit may not.
- Open the .xlsx. Each class occupies its own worksheet with elements as rows and attributes, Psets and quantities as columns, while the summary sheet documents counts per class. Excel, LibreOffice and Google Sheets all read it as-is.
Where this fits in a coordination workflow
BIM quantity takeoff in Excel. Rather than measuring off drawings or budgeting for a takeoff add-in, pull Qto columns straight into the estimating workbook. Slab volumes, wall areas and member lengths arrive as numbers a pivot table can chew on immediately — and every figure is traceable back to a GlobalId if a total looks off.
Data-drop audits before a milestone. When the BEP demands that all doors carry a fire rating or all spaces carry a classification code, a spreadsheet finds the gaps faster than any click-through review: sort the relevant column and the empty cells line up at the top. The same sheet then becomes the evidence you attach to the delivery note — checked, dated, done.
Handover without handing over a model. Building owners seldom want IFC files; they want an asset list they can load into their FM system. Exporting spaces, doors and equipment with their properties gives the operations team a register they can work with on day one — no BIM software licence required at their end.
Answers for people who will never install a viewer. A contractor querying element counts per level, a client reviewing the room programme, a structural checker scanning beam sections: send the sheet, not the model, and the conversation moves forward the same day.
Sized for real federation-scale files
Extraction was built against the kind of files coordination actually produces, not demo cubes. In our benchmark, a 67 MB model containing 937,000 entities yielded 118,317 elements across a 10-sheet, 29.3 MB workbook in 10.6 seconds — and because the entire job runs in a Web Worker off the main thread, the page held 144 fps throughout instead of freezing. Escaped international characters in property values are decoded properly along the way, a detail that matters the moment your project speaks German, Spanish or Japanese. Want to see the elements behind the rows? The free BIM viewer opens the very same file in 3D, right in this browser.
Frequently asked questions
Can I run confidential project models through this exporter?
Yes — that is the core design constraint of the tool. The IFC is parsed by WebAssembly inside your own browser tab and the workbook is assembled there too, so no copy of the model ever reaches a server. Close the tab and nothing persists anywhere. Tender packages and NDA-bound models are exactly the use case.
What lands in the workbook?
Every element the model contains, with its attributes, its property sets and its quantities laid out as columns. Classes are split across worksheets — the walls get a sheet, the doors get a sheet, and so on — and a summary sheet up front records how many elements of each class the model holds, so you can sanity-check the export at a glance.
Are the quantities usable for takeoff, or do I have to re-measure?
If the authoring model carries quantity sets, they come through as plain numeric columns — areas, volumes, lengths, counts — ready for SUM, pivot tables and your estimating templates. The exporter reports what the model states; garbage in, garbage out still applies, which is precisely why having the figures in a spreadsheet makes auditing them so much faster.
Can I trim the export down to the classes I care about?
Yes. Once the model has been scanned you see every IFC class it contains, each with its element count, and you deselect whatever is noise for your task. Quantity sets can likewise be switched on or off, so a lean attribute-only export and a full takeoff dump are both two clicks away.
Which IFC flavours does it accept?
IFC2x3, IFC4 and IFC4x3 all work, no matter which authoring platform wrote the file — Revit, ArchiCAD, Tekla, Allplan or anything else that speaks IFC. Zipped .ifczip deliverables are unpacked on the fly before extraction.
How big a model can the browser handle?
There is no hard cutoff. Desktops comfortably process files up to roughly 300 MB; a heads-up appears once you pass 150 MB. Phones and tablets have tighter memory budgets, so the warning arrives at 80 MB combined there — leave the really big federated exports to a desktop machine.