A comprehensive open-source toolkit for parsing, viewing, querying, editing, validating, and exporting AEC data formats like IFC, IDS, and BCF. It targets developers needing robust, client-side BIM data manipulation in the browser, server, or desktop, offering significant performance gains and a modular architecture.

How It Works

The core utilizes a Rust backend compiled to WebAssembly for high-performance parsing and geometry processing, achieving up to 5x speed improvements over web-ifc. A WebGPU renderer handles 3D visualization, while a rich ecosystem of 36 npm packages allows developers to integrate specific functionalities granularly. This client-first approach minimizes server load and enhances user experience.

Quick Start & Requirements

• Primary install/run: Use npx create-ifc-lite my-viewer --template react, then cd my-viewer && npm install && npm run dev.
• Prerequisites: For development, a Rust toolchain (rustup, wasm-pack) is required. For running, a modern browser with WebGPU support is needed.
• Links: Live demo: ifclite.com, More info: ifclite.dev.

Highlighted Details

• Geometry processing is up to 5x faster than web-ifc (median ~2.2x).
• Full schema coverage for IFC4 (776 entities) and IFC4X3 (876 entities).
• Supports advanced features like IDS validation, BCF clash detection, property editing with undo, and AI tooling via Model Context Protocol.
• Offers a powerful CLI for scripting, CI pipelines, and model operations without writing application code.

Maintenance & Community

Active development is evident through numerous npm packages and Rust crates. Community engagement is facilitated via GitHub Discussions and Issues. Changelogs are available under Releases.

Licensing & Compatibility

• License: MPL-2.0 (Mozilla Public License 2.0).
• Compatibility: Source files modified under MPL must remain MPL. Permissive for use and redistribution, but requires derived works of modified source files to be open-sourced under MPL.

Limitations & Caveats

While versatile, handling extremely large files (500MB+) may necessitate specific setups like the desktop build. The modular nature requires careful selection of packages, potentially increasing initial integration complexity.