Your formats. A connected workflow.
Choose the components for the files your project uses. xeokit Data Engine prepares supported engineering formats; xeokit SDK loads supported web-ready models for browser viewing.
Verified 18 September 2026
The xeoVision framework uses selected xeokit Data Engine processors for IFC, Revit RVT/RFA, STEP, Navisworks and AVEVA files. Supported point-cloud and web-ready 3D formats use xeokit SDK loaders. The matrix below separates these paths and identifies available and announced processors.
Which file formats does xeoVision open?
Engineering formats pass through a xeokit Data Engine processor, which extracts geometry and model information into open outputs. Web-ready 3D formats need no processing step. To see a prepared model, open one in the browser-based BIM viewer.
xeokit Data Engine processors
| Processor | Source formats | Status |
|---|---|---|
| xeoIFC | IFC 2x3, IFC 4, IFC 4.3 | Available |
| xeoRVT | Autodesk Revit RVT, RFA | Available |
| xeoSTEP | STEP, STP | Available |
| xeoNWD | Autodesk Navisworks NWD | Available |
| xeoRVM | AVEVA E3D, PDMS | Available |
| xeoIMODEL | Bentley iTwin iModel (.bim) | Announced — not yet available |
5 processors are available today. xeoIMODEL is announced and not yet available.
Select processors against the source formats and versions you receive. Check geometry, properties and required relationships with representative files before agreeing the workflow; the filename extension alone does not establish the result for a particular project.
Loaded directly by the xeokit SDK
-
Point clouds
LAS · LAZReality capture alongside the design models.
-
Web 3D
GLB · glTF · XKTOptimized assets prepared for browser visualization.
-
Mesh geometry
OBJ · STLComponents and scanned meshes from common tools.
-
Geospatial
CityJSON · 3DXMLCity models and structured product data.
What does xeokit Data Engine output?
Processing writes open formats, not a proprietary container. Your own systems can read the results without going back through xeoVision.
- JSON
- Object properties and metadata.
- GLB
- Geometry in a widely supported 3D format.
- XKT
- xeokit's compressed format for fast browser loading.
Do you need Revit installed to open an RVT file?
No. xeoRVT reads Autodesk Revit RVT and RFA files directly and produces GLB, JSON and XKT. The processing step does not require a Revit installation, an Autodesk Platform Services subscription, or an intermediate IFC export. This describes viewing and processing files you supply — it is not a statement about Revit authoring rights.
How Revit processing worksWhere does file processing run?
You choose. xeokit Data Engine runs as a managed service, on dedicated infrastructure, inside your own environment, or as a standalone command-line binary in your own pipeline.
-
Managed service
Run on the service operated by Creoox AG. Nothing to install.
-
Dedicated infrastructure
A dedicated environment for your organization, in the region you choose.
-
Your own servers
Deploy inside your own infrastructure and keep project data within your boundary.
-
Standalone binary
Run xeokit Data Engine as a command-line binary in your own pipeline.
The standalone binary runs on Windows AMD64, Linux AMD64 and Linux ARM64. Plan processing, hosting and data storage together.
Not sure your format is covered?
Bring a file and a question. We will tell you what xeokit Data Engine does with it — and what it does not.