xeokit
xeokit is a JavaScript BIM viewer SDK, maintained by xeolabs with Creoox AG support, that loads large AEC models in the browser using WebGL, double-precision coordinates, and plugins such as XKTLoaderPlugin for converted IFC geometry.
Published API docs describe xeokit as a JavaScript kit for viewing high-detail engineering and BIM models in the browser, with installation via npm i @xeokit/xeokit-sdk and a plugin model centered on Viewer plus loaders like XKTLoaderPlugin (xeokit-sdk documentation, accessed 2026-04-19).
The same documentation shows a deprecation plan: ES5 and CommonJS builds stop shipping in September 2026, while ES module builds remain the supported path for modern browsers and bundlers (xeokit-sdk documentation, accessed 2026-04-19).
Marketing copy on xeokit.io states the AGPL-3.0 open-source tier is free, lists community support, and positions a separate custom proprietary license sold by Creoox AG for teams that need closed-source distribution (xeokit.io pricing section, accessed 2026-04-19).
Format coverage spelled out in the public FAQ includes IFC (2x3 and 4.3), CityJSON, glTF, OBJ, 3DXML, LAS, LAZ, and XKT, with an example noting a roughly 49 MB Schependomlaan IFC shrinking to about 1.5 MB XKT and loading in roughly two to three seconds on a strong connection after conversion (xeokit.io FAQ, accessed 2026-04-19).
Specifications
Pricing
Platforms
Used for
Used by
Tasks
Pros and cons
Pros
- Focused on browser performance for very large AEC models rather than generic mesh viewers.
- Clear npm entry point and extensive hosted examples for `@xeokit/xeokit-sdk`.
- Documented migration away from legacy ES5 bundles toward ES modules only.
Cons
- AGPL-3.0 obligations can be strict for SaaS products unless you buy the commercial license from Creoox AG.
- Native IFC viewing relies on pre-conversion to XKT or other supported formats, which adds a pipeline step.
- September 2026 cutoff for legacy build artifacts may force upgrades on older bundler stacks.
Key features
WebGL viewer core: Hardware-accelerated rendering tuned for many small parts, documented alongside double-precision global coordinates for GIS-scale scenes.
Loader plugins: First-party plugins cover XKT, CityJSON, glTF, LAS/LAZ, OBJ, and other paths described in the SDK docs and landing-page FAQ.
IFC path via XKT: Typical flow converts IFC 2x3 or 4.3 into the compact XKT binary format, then loads it through
XKTLoaderPluginfor fast startup.BCF viewpoints: Landing materials call out saving and loading BCF viewpoints so web apps stay aligned with coordination workflows.
AGPL plus commercial option: Public pricing contrasts the free AGPL-3.0 SDK with paid custom licenses from Creoox AG for proprietary products.
Pricing
AGPL-3.0 open-source SDK
Contact sales
Described as free under AGPL-3.0 on xeokit.io with community support (accessed 2026-04-19). Confirm obligations with legal counsel.
Custom proprietary license
Contact sales
xeokit.io states Creoox AG sells custom licenses with negotiated fees; contact the vendor for current pricing (accessed 2026-04-19).
Frequently asked questions
How much does xeokit cost if we ship a closed-source SaaS viewer?
xeokit.io lists a free AGPL-3.0 open-source tier with the full SDK and community support, then asks teams that need proprietary licensing to contact Creoox AG for a custom quote (xeokit.io pricing section, accessed 2026-04-19). Read the AGPL summary on that page before you bundle the SDK inside a commercial product.
Does xeokit run on mobile browsers?
The xeokit.io feature list states the toolkit targets all major desktop and mobile browsers without plugins (xeokit.io, accessed 2026-04-19). You still need to host converted models and the viewer assets from your own infrastructure.
Which IFC versions and sidecar formats can xeokit display?
The public FAQ names IFC 2x3 and 4.3 alongside CityJSON, glTF, OBJ, 3DXML, LAS, LAZ, and XKT as formats the SDK can load (xeokit.io FAQ, accessed 2026-04-19). IFC usually arrives after conversion to XKT using the open conversion tools referenced in the same FAQ.
Can xeokit author or save IFC files after edits?
The FAQ explicitly says authoring or persisting IFC is out of scope because keeping full IFC documents in browser memory would be impractical; xeokit targets fast interaction with pre-converted geometry instead (xeokit.io FAQ, accessed 2026-04-19). Pair it with a server-side authoring stack when edits must round-trip to IFC.
What performance should we expect when converting large IFC projects?
The Schependomlaan example in the FAQ cites a roughly 49 MB IFC shrinking to about 1.5 MB XKT and loading in roughly two to three seconds on a good network after conversion (xeokit.io FAQ, accessed 2026-04-19). Your numbers will vary with model complexity and hosting latency.
Who maintains xeokit and where do we get support?
The SDK documentation credits creation by xeolabs with support from Creoox AG, and the pricing page routes commercial licensing questions to contact@creoox.com (xeokit-sdk documentation and xeokit.io, accessed 2026-04-19). Community support accompanies the AGPL tier.