Building models usually reach the browser as an IFC file exported from BIM, or as CAD drawings delivered by the architect. NIST IR 8356 defines a digital twin as an electronic representation of a real-world entity that lets a user examine the entity's state and the transitions between states (Voas et al., 2025). BIM and CAD supply the geometry and data for that representation, and the web layer handles display and interaction. The division of work among the web-side technology layers is covered in What Web 3D Is.
The adoption sequence is to decide which data fields to keep, then handle units and coordinates, mesh reduction, materials, and naming, and finally accept the result against measurable differences. Analysis output such as wind and sunlight is a separate input, covered in Web-Based Building Digital Twins. This article is about the building model itself.
What BIM, CAD, and Web 3D Each Handle
IFC is an open data model maintained by buildingSMART International. The official repository currently publishes IFC 4.3.2.0 and notes that the release version is approved by ISO (buildingSMART International, IFC4.3.x-development). IFC describes a building as typed objects: an IfcWall is a vertical construction that bounds or subdivides space, and an IfcBuildingStorey carries an elevation and represents one floor. Object properties live in an IfcPropertySet, a container of properties identified by name that can be attached to a single object or to an object type (IfcPropertySet specification).
glTF 2.0 is the runtime 3D asset transmission format published by Khronos. Its stated goal is a compact, extensible, interoperable loading format between authoring tools and graphics applications (Khronos 3D Formats Working Group, 2021). The specification describes glTF as complementary to authoring formats and as the common output for delivery to end users. Models on the web are mostly GLB, the binary form of glTF.
CAD drawings are a different kind of data. DWG and DXF record 2D primitives as layers, blocks, text, and coordinates, with no object types comparable to IFC. The three kinds of data call for different work on the way into the browser, summarized below.
| Source | Contents | Work needed for the web |
|---|---|---|
| IFC | Typed building objects, spatial hierarchy, property sets | Extract geometry into meshes, pick the properties to keep, save a separate property table |
| DWG/DXF drawings | Layers, blocks, text, 2D coordinates | Extract elements by layer and block rules, rebuild 3D volumes |
| GLB | Triangle meshes, materials, node hierarchy | Load directly in the browser; file size and triangle count are the main limits |
What to Keep and What Stays Out of the Browser
Before conversion, decide on three categories of content separately.
- Geometry: exterior form, floor separation, and openings. For browsing a whole building, the exterior form and per-floor grouping are required.
- Materials: colors and textures. Construction material specifications are properties and do not need to become textures.
- Properties: select the fields the viewer will use, such as ID, name, floor, and use, and leave the rest in the source file. List the properties before conversion; properties added afterward often fail to map back to objects.
Fields that need to be queried go into a separate property table, while the GLB carries geometry only, and the two are linked by the same identifier. Besides glb, IfcConvert can also write json and xml, which hold property definitions and the object decomposition tree (IfcOpenShell, IfcConvert usage).
Conversion Checkpoints
- Source fileIFC or DWG; record version and units
- Units and coordinatesUnify to meters; record the offset
- Main tower before reductionabout 300,000 triangles
- Faces removedabout 280,000 facesWeld seams and merge coplanar faces, then simplify
- Main tower after reductionabout 20,000 trianglesSame silhouette, single GLB
- AcceptanceCoordinate delta, triangle count, download size, shape comparison
Triangle counts are from the display building of a wind-environment visualization project, the main tower, and are approximate. Counts at the other stages vary by model, so no range is given.
Units and Coordinates
An IfcProject carries an IfcUnitAssignment that sets the default units for the whole project (IfcUnitAssignment specification). glTF fixes all linear distances in meters, with +Y as up and a right-handed coordinate system (Khronos 3D Formats Working Group, 2021). Both units and axis orientation have to be aligned during conversion.
IFC also uses IfcMapConversion to move engineering local coordinates into a map coordinate system: scale by one common factor, rotate counterclockwise about the z axis, then translate by Eastings, Northings, and OrthogonalHeight. The description also states that the z axis of the local system is parallel to the z axis of the map system (IfcMapConversion specification). Map coordinates are large numbers, and placing such values directly in a browser scene easily causes precision problems. IfcConvert converts units to meters by default; when coordinates are too large, --center-model moves the model near the origin, --model-offset sets an explicit offset, and --model-rotation sets a rotation (IfcOpenShell, IfcConvert usage). Record the offset and rotation values so the browser model can later be aligned back to the map and the other layers.
CAD sources have the same coordinate problem. For a configurator project that received a client's SolidWorks exploded view, the CAD and web X and Z axes ran in opposite directions and distances changed from millimeters to world units. The development team used paired parts such as the left and right cranks to confirm the direction had not been flipped. The explosion sequence was parsed from the source animation segments as 52 steps, mapped onto a 31-segment timeline in the browser. Listing the unachievable parts before work began, for example placeholder steps with zero displacement, kept acceptance free of surprises. The assembled state was compared pixel by pixel against the version before the change, and 16 views showed a difference of 0 pixels (2026-10, screenshots taken before and after the change).
Mesh Reduction With the Silhouette Preserved
The triangle count a browser can load has a ceiling, and source files are usually far above it. The simplify function in glTF Transform is built on meshoptimizer and aims to keep visual quality with the fewest triangles. The documentation states that the algorithm is lossy: the ratio parameter is the target fraction, the error parameter is the error threshold, and the algorithm stops before reaching the target ratio once the error exceeds the threshold. Topology issues such as split vertices also limit reduction, so the documentation recommends running weld before simplify (glTF Transform, simplify).
The display building of a wind-environment visualization project is one example. An STL file was welded in Blender to close seams and merge coplanar faces, taking the main tower from about 304,000 triangles to about 20,000 with the silhouette unchanged, and the result was exported as a single GLB. That mesh is for display only and is not a simulation mesh. The two serve different purposes, with details in Web-Based Building Digital Twins.
Materials, Textures, Naming, and Hierarchy
When a GLB grows large, check textures first and geometry second; the measurement method is in GLB File Too Large: Check Textures First, Then Geometry. Naming and hierarchy have to be agreed before conversion. The IFC spatial hierarchy is site, building, storey. If the browser needs floor switching or floor-by-floor display, the GLB node hierarchy must be grouped by floor, and node names must map back to identifiers in the property table.
No IFC Available: Building the Whole Tower and Each Unit Interior From Floor Plans
Not every building has an IFC file. The source for the urban renewal unit-selection system was a set of architect-delivered floor plans in DWG format. GNU LibreDWG converts the plans to DXF, Python's ezdxf reads layers, blocks, and text, and Shapely tests intersection and containment between unit outlines and rooms. By rule, the pipeline extracts unit outlines, unit codes, parking spaces, windows, balconies, and interior elements, then assembles 3D volume data for the site's whole-building exterior, per-unit interiors, and floor plans. The assembly has built-in self-checks: every unit has a code, codes are unique within a floor, and unit and parking counts match the project settings. If any check fails, the pipeline stops where it is and produces no partial output. The finished system is shown in the Urbird urban renewal system case.
This route depends on consistent drawing conventions: layer, block, and unit-code naming stays the same from one revision to the next, so the extracted results stay stable.
- Identify the type of source fileIFC, DWG or DXF, PDF or scanned drawing
- An IFC file is availableExtract geometry, save properties separatelyConvert to GLB; align coordinates and units first
- DWG or DXF drawings are availableRebuild 3D volumes from layer and block rulesDrawing naming must be consistent
- Only PDF or scanned drawingsNo readable layers or coordinatesObtain the original drawing files first
Acceptance: Measurable Differences
After conversion, compare the source and the browser version item by item. The full procedure for intake and acceptance is in Intake, Reproduction, and Acceptance of Outsourced 3D Models, and three of its checks apply to building models.
- World coordinate delta: pick the same set of feature points in the source and the GLB, such as slab corners and column centers, and compare the world coordinates of each. Agree on the tolerance before conversion.
- Triangle count and download size: record triangle counts and GLB size before and after reduction, and measure load time on the target device.
- Shape comparison: overlay the source and the GLB from the same viewpoint to confirm reduction did not change the silhouette, especially openings and setbacks.
Relationship to Digital Twins
BIM and CAD supply static geometry and data. An operational digital twin also needs a continuous stream of sensor data, while an analytical one, such as wind and sunlight, overlays simulation results on the same building model. All three share one display geometry, so the model's coordinates and units must be fixed accurately in the first step.
Whole-Building Loading or Split Packages
Loading the whole building at once keeps operation simple and produces the largest download. Splitting packages by floor or zone loads only what is currently needed, at the cost of requiring node names and coordinates to stay consistent across packages. Section cuts, floor selection, and interior panoramas are covered in How a 3D Property Showroom Website Works. Overall technology choices and workflow are in the Complete Guide to 3D Web Design.
Cases Where Web Visualization Alone Falls Short
- Measurement at construction-drawing precision: reduction is lossy and the browser model is for viewing only, so measurements should go back to the original BIM or drawings.
- Files for regulatory review: review proceeds on the original delivery format, and the browser version can serve only as a supplementary explanation.
- Real-time equipment control: control systems need dedicated communication and permission design, and the browser model only displays status.
Information to Prepare Before Adoption
- Source files and versions: the IFC version and export settings, or the DWG revision.
- Coordinate system and units: the system and units the source uses, and whether map coordinates are present.
- List of properties to keep: the fields the viewer will use.
- Target devices and download ceiling: these set the reduction ratio and texture size.
Once the data is ready, discuss requirements with the development team. The team's 3D web design service covers model preparation through launch.
