Is my IFC file uploaded anywhere?

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.

Can I use it with confidential models under NDA?

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.

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

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.

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.

What happens if my IFC file is very large?

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.

How does the validation work?

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.

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

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.

What IFC versions are supported?

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.

What measurement tools are available?

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.

Can I load multiple IFC files at once?

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.

Does it work offline?

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.

What are the file size limits?

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.

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

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.

Back to the BIM & IFC blog

Standards · 2026-03-15 · 9 min

ISO 19650 Compliance for IFC Deliveries: A Practical Checklist

ISO 19650 specifies information requirements for BIM deliveries. Here is what that means for your IFC files — from filename conventions to embedded project metadata — and how to verify compliance before submission.

ISO 19650 Compliance for IFC Deliveries: A Practical Checklist — IFC Viewer Online article cover

ISO 19650 is the international standard for managing information over the whole life cycle of a built asset using BIM. Part 2 covers information management during capital delivery phases — which is where most IFC delivery requirements originate.

Part 1: File Naming Convention

ISO 19650-2 §6.3 specifies a filename structure built from fields separated by hyphens: [Project] - [Originator] - [Volume/System] - [Level/Location] - [Type] - [Role] - [Classification] - [Number].[Extension].

Part 2: IfcProject Metadata

ISO 19650-2 §9.2 requires that IfcProject contain: LongName (the official project name), Description (a brief project description), and ObjectType (the project type and phase). These three fields are the minimum — and they're missing in the majority of IFC files in practice.

Part 3: File Header Traceability

The IFC STEP file header FILE_NAME record has author and organization fields. ISO 19650-2 §9.1 requires these to be populated for traceability. Most tools leave them as empty strings by default.

ISO 19650 Compliance Checklist

Filename follows the convention specified in the PIR.
IfcProject.LongName = official project name as it appears in contracts.
IfcProject.Description = brief project description.
IfcProject.ObjectType = project type and current phase.
FILE_NAME author field = originator's full name.
FILE_NAME organization field = originator's company name.
All physical elements have IfcRelAssociatesClassification.
Classification system matches the one agreed in the PIR.
Health Score ≥ 80 (structural quality prerequisite for formal delivery).

Turning the Checklist Into an Agreement

A checklist only changes behaviour once it is somebody's obligation. The wording that puts these items into a BIM Execution Plan is in BEP clauses that actually prevent bad IFC deliveries; the table the receiver applies at the gate is in IFC acceptance criteria; and what travels alongside the file is in what to hand over with an IFC model.

ISO 19650 Compliance for IFC Deliveries: A Practical Checklist