Skip to content
FreeBIMTools

IFC to Excel

Turn a model into a spreadsheet: choose the categories you care about, pick your columns, and download.

Files stay on your device

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

  1. 1Select an IFC file. It is read from your disk by your browser and goes no further.
  2. 2The categories actually present in the model are listed with their element counts.
  3. 3Choose the categories, then simple or full property columns.
  4. 4Download as Excel or CSV. The whole selection is included, not just the preview.

About IFC to Excel

Almost every downstream BIM task is a spreadsheet task. Quantities, checking lists, handover schedules and client reports all end up in Excel, and the slow step is getting the model data out in a shape a spreadsheet can use.

Choosing categories first matters more than it sounds. Exporting an entire model produces a file nobody can work with, because most IFC entities are geometry and relationships rather than things you would schedule. Picking IfcDoor and IfcWindow gives a door and window schedule. Selecting everything gives a data dump.

Simple covers identity and location, which is what most schedules need. Advanced flattens every property set into columns, which is the right choice when you are auditing what data actually exists rather than producing a tidy deliverable.

Two practical details that cause most conversion complaints elsewhere: the CSV carries a UTF-8 byte order mark so German characters survive the trip into Excel, and the delimiter is switchable, because Excel on a European locale will not split on commas.

Questions

Is my IFC file uploaded anywhere?
No. The file is read by your own browser using a WebAssembly IFC parser, and the spreadsheet is generated on your machine. The model is never sent to FreeBIMTools, and there is no upload endpoint for it.
What is the difference between simple and advanced columns?
Simple gives you GlobalId, IFC type, name, object type and storey, which is what most schedules need. Advanced adds every property and quantity found on the selected elements as its own column, which can be hundreds of columns on a rich model.
My umlauts arrive as strange characters in Excel. Why?
That is Excel guessing the encoding. Our CSV includes a UTF-8 byte order mark specifically so Excel reads ä, ö, ü and ß correctly, and the Excel download avoids the problem entirely. If you are re-saving the file through another tool in between, check that it preserves UTF-8.
Every row lands in one cell. What do I change?
Switch the CSV delimiter to semicolon. Excel on a German and most European locales expects a semicolon as the list separator and will not split on commas. The Excel download does not have this problem.
Why are some property columns empty?
A column appears if any selected element carries that property. Elements that do not carry it are blank, which is accurate: the gap is in the model, not in the conversion. That is often the most useful thing in the spreadsheet.
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 convert 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 to Excel should do, and describe the job rather than the feature.