Model Conversion
On this page
An illustration of IFC element types, including beams, columns, plates and members.

Introduction

There are various ways to load models into a xeokit scene. The most common approach is to pre-convert the models into the native XKT format and then load the XKT file. The potential benefits of this approach include:

  • faster model loading;
  • heap size optimization;
  • smaller model files.

Results depend on the source model and conversion settings.

Listed below are several pipelines we can use to convert AEC files to XKT. Each pipeline involves running the files through a chain of one or more CLI tools in your local environment. The Community pipelines use exclusively open-source tools, while the Enterprise pipelines include proprietary tools for which a commercial license is required.

From your model to a xeokit scene
Three alternative routes to the same scene. The model shown is West Riverside Hospital in a xeokit viewer.

Enterprise Conversion

A high-performance pipeline converts large files into .xkt with two CLI tools, using intermediate .glb and .json files. The format-specific converter is proprietary; xeokit-convert is open source under AGPL-3.0, with a custom commercial license also available, as for the xeokit SDK. Contact us about custom licensing.

The xeokit Data Engine includes xeoIFC for IFC, xeoRVT for Revit and xeoSTEP for STEP. The intermediate GLB contains geometry; the JSON contains model metadata. xeokit-convert combines them into XKT, which is loaded with XKTLoaderPlugin.

Want to try it yourself? Simply drag and drop your supported model files into xeoVision to view them directly in your browser.

Enterprise conversion
  1. Source → converter
    IFC xeoIFC
    RVT / RFA xeoRVT
    STEP / STP xeoSTEP
  2. Intermediate files
    .glb Geometry
    .json Metadata
  3. Convert to XKT
    xeokit-convert Output: .xkt
  4. Load & view
    XKTLoaderPlugin → xeokit scene
Choose the converter for your source format. Geometry and metadata are combined into XKT, then loaded into the viewer.

Current xeoIFC documentation also describes direct XKT output, as an alternative to the two-stage workflow above.

This image above presents an IFC model converted by xeoIFC, read more about this model here.

Ready to try xeokit Data Engine?

Explore how easily you can convert BIM and CAD data into xeokit scenes. Fill out the form to request evaluation access and start exploring its capabilities.

Community Conversion

For some file formats, we have a free and open-source solution that enables you to convert them into .xkt. Check the xeokit-convert project for supported formats and conversion options.

Community multi-format conversion
  1. Source model
    glTF / GLB
    LAS / LAZ
    CityJSON
  2. Convert to XKT
    xeokit-convert Output: .xkt
  3. Load & view
    XKTLoaderPlugin → xeokit scene
Convert a supported source file to XKT with an open-source tool, then load it with XKTLoaderPlugin.

For IFC, we also have two community pipelines:

Two community pipelines for IFC

1. Direct IFC conversion

  1. Source model
    IFC .ifc
  2. Convert to XKT
    xeokit-convert Uses web-ifc → .xkt
  3. Load & view
    XKTLoaderPlugin → xeokit scene

2. Legacy geometry and metadata pipeline

  1. Source model
    IFC .ifc
  2. Extract separately
    IfcConvert Geometry → .glb
    xeokit-metadata Deprecated BIMspot · hierarchy → .json
  3. Convert to XKT
    xeokit-convert Output: .xkt
  4. Load & view
    XKTLoaderPlugin → xeokit scene
Both paths produce XKT. The second is a legacy pipeline: its third-party xeokit-metadata dependency is deprecated and no longer maintained.

The first converts IFC directly with xeokit-convert, using web-ifc. This has documented geometry and property-set limitations, so check the results with your models.

The second is a legacy pipeline using IfcConvert to convert geometry into a .glb file and xeokit-metadata to extract the model hierarchy into JSON. After that, both outputs are converted into .xkt using xeokit-convert.

Deprecated dependency: xeokit-metadata is no longer maintained. It is a third-party BIMspot repository, outside the xeokit organization. This pipeline is retained for reference.

See also the model conversion examples and test models.

Without Conversion — Direct Loading

The simplest way to load a model is directly through loader plugins. This way, you don't need to set up a conversion pipeline. This approach may be enough for some use cases, for example small models.

Existing SDK loader plugins include:

Direct loading
IFC
WebIFCLoaderPlugin
IFCOpenShellLoaderPluginAdditional data-source setup
XeoIFCLoaderPluginSeparately supplied xeoIFC integration
glTF / GLB
GLTFLoaderPlugin
LAS / LAZ
LASLoaderPlugin
CityJSON
CityJSONLoaderPlugin
dotBIM (.bim)
DotBIMLoaderPlugin
STL
STLLoaderPlugin
OBJ
OBJLoaderPlugin
3DXML
XML3DLoaderPlugin
xeokit sceneLoaded directly from the source format
Each loader prepares its source format directly for the xeokit scene. No intermediate XKT file is needed.

IFC integrations have different setup, dependencies and licensing. See the linked documentation when choosing a loader.

Find our loader plugins in the xeokit SDK source.

This example above shows Duplex model loaded with IfcOpenShellLoaderPlugin, you can find this example here.

For step-by-step examples and implementation tips, see these guides from the xeokit blog:

xeokit

Subscribe to our newsletter

New features, real-world builds and the occasional deep dive. No spam.

Loading the form…

Write to contact@creoox.com.