Question 1

Is my IFC file uploaded anywhere?

Accepted Answer

No. Files are parsed entirely in your browser via web-ifc, a WebAssembly build of the open-source IFC parser. Nothing leaves your machine. The app works completely offline once loaded.

Question 2

Can I use it with confidential models under NDA?

Accepted Answer

Yes. Because all processing happens in your browser and no data is ever transmitted to any server, you can safely use it with confidential project models under NDA. There is no service agreement to review with your client — no data changes hands.

Question 3

Can I share the validation results with my team or client?

Accepted Answer

Yes. After running validation, click Share Report to copy a link that encodes the full Health Score and issue list directly in the URL — no file upload, no server, no account required. You can also export results as JSON, CSV, or a Validation Certificate. The IFC file itself never leaves your browser.

Question 4

Does it work on Mac?

Accepted Answer

Yes, fully. IFC Viewer Online works on any modern browser — Chrome, Edge, Firefox, and Safari on both Mac and Windows. No plugin, no installation, no operating system restriction.

Question 5

What happens if my IFC file is very large?

Accepted Answer

The app handles files up to 2 GB. Performance depends on your device — files under 200 MB load well on most modern hardware. Once parsed, geometry is cached in OPFS so every subsequent load of the same file is instant, even offline.

Question 6

How does the validation work?

Accepted Answer

The validator runs 44 built-in rules in a background Web Worker so the UI stays responsive. Rules cover GUID duplicates, spatial hierarchy, orphan elements, naming conventions, missing type assignments, ISO 19650 property sets, LOD completeness, clash detection, proxy overuse, coordinate offset, storey-elevation integrity, unit consistency, and more. You can also run a buildingSMART IDS specification against the model. Every model receives a Health Score from 0 to 100. Results stream in as each rule completes.

Question 7

Can I fix errors and re-export a corrected IFC?

Accepted Answer

Yes. All edits (GUID fixes, renames, property value changes) are held as non-destructive diffs with full undo/redo. Clicking Export IFC applies all diffs to the original binary in a Web Worker and downloads the corrected file — no server involved.

Question 8

What IFC versions are supported?

Accepted Answer

IFC2x3, IFC4, IFC4x1, and IFC4x3. The viewer uses the open-source web-ifc parser — the same engine used by most modern BIM tools and @thatopen/components. Outdated schemas are automatically flagged by the validator.

Question 9

What measurement tools are available?

Accepted Answer

You can measure lengths between any two points, areas of surfaces, volumes of enclosed elements, and individual edge lengths — all directly in the 3D viewport. Measurements persist as labelled annotations and can be exported alongside your model.

Question 10

Can I load multiple IFC files at once?

Accepted Answer

Yes. Load as many IFC files as your device memory allows. Each model has independent visibility, transforms, validation, quantity takeoff, and export. Use the Scene panel to manage, reorder, or remove models at any time.

Question 11

Does it work offline?

Accepted Answer

Yes, once the page is loaded. The WebAssembly parser and WebGL renderer run entirely in the browser. Parsed geometry is cached in OPFS so repeat loads are instant even without a network connection.

Question 12

What are the file size limits?

Accepted Answer

There is no enforced limit — performance depends on your device. Files up to ~200 MB typically load well on modern hardware. The OPFS geometry cache means you only pay the parse cost once per file.

Question 13

Is it free? Can I use it for commercial projects?

Accepted Answer

Yes, completely free. The source code is MIT-licensed. You can use the live app or fork the repository for your own projects, including commercial ones.