Convert DAE to IFC in your application
3D InterOp is a CAD interoperability SDK that lets your software read DAE files and write IFC, writing the DAE facets as faceted geometry, since DAE stores triangles rather than solids.
Spatial does not offer an online converter or a desktop conversion app. 3D InterOp is a component that software vendors embed in their own products.
- Reads COLLADA · Writes IFC
- Triangle mesh → faceted model
- C++ / C# APIs
DAE to IFC at a glance
COLLADA stores triangles; IFC can hold facets alongside exact solids, so the mesh is written as faceted geometry.
| COLLADA (source) | IFC (target) | |
|---|---|---|
| Full name | COLLADA Digital Asset Exchange | Industry Foundation Classes |
| Standard / owner | Khronos Group, ISO/PAS 17506 | buildingSMART, ISO 16739 |
| File extensions | .dae, .zae | .ifc, .ifczip |
| Geometry | Triangle mesh | Exact B-Rep and tessellated geometry |
| Assemblies / structure | Yes: scene hierarchy | Yes: spatial and element hierarchy |
| 3D InterOp support | Read and write | Read and write |
What's preserved, what changes
Here is what your application can expect to carry across from COLLADA to IFC.
-
Preserved
Product structureThe DAE product structure is written to IFC.
-
Changes
Faceted geometryDAE stores triangles, so the IFC file holds faceted bodies, not solids. 3D InterOp doesn’t rebuild exact B-Rep from a mesh.
Why software vendors add DAE to IFC conversion
Open BIM deliverables
Many projects specify IFC deliverables. Writing it lets your users meet those requirements from your software.
Coordination and clash detection
Coordination tools gather models from every discipline in IFC. Your users can contribute without a round trip through another tool.
Facility and asset data
Owners and operators often receive building data as IFC for asset management after handover.
Things to check before you ship
- Written IFC versions: IFC2x3 to IFC4x3 ADD2 (.ifc).
- Exact B-Rep needs IFC4 or later; IFC2x3 files only get tessellation.
- DAE has no BIM semantics: check which IFC class your application assigns to each object.
- Supported DAE input: COLLADA 1.4.1, .dae and .zae.
- Validate a sample of translated files in the target system your users actually work with.
Working with Spatial was a real milestone for us: Thanks to the powerful 3DInterOp library, we were able to successfully bring our complex CAD-based solutions to the cloud while remaining flexible to meet individual customer requirements. For us, Spatial is not just a technology partner, but a true enabler of our product strategy.
Dr. Arno Michelis, Founder, Simus Systems
Read the Case StudyAbout the formats
-
Source format
What is a DAE (COLLADA) file?
COLLADA (.dae) is an XML-based open format from the Khronos Group for exchanging 3D scenes: meshes, materials, cameras and lights. It is common in visualization and AR/VR pipelines.
-
Target format
What is an IFC (.ifc) file?
IFC is the open, vendor-neutral standard for exchanging building information models, maintained by buildingSMART and published as ISO 16739. It carries building elements with their geometry, properties and relationships.
Frequently asked questions
No. DAE stores triangles, and 3D InterOp writes them to IFC as faceted geometry. It doesn’t rebuild exact B-Rep from a mesh.
Yes. 3D InterOp reads the DAE product structure and writes it to IFC.
Write IFC4 or later to keep exact B-Rep: IFC2x3 files only get tessellation. 3D InterOp writes IFC2x3 to IFC4x3 ADD2.
DAE has no BIM semantics, so your application decides which IFC class each object is written as.
Yes. 3D InterOp reads the visual material properties of COLLADA files, from .dae and .zae.
3D InterOp reads COLLADA 1.4.1, .dae and .zae, as visualization data.
3D InterOp writes IFC2x3 to IFC4x3 ADD2 (.ifc).
-
Building software that needs to convert DAE to IFC?
3D InterOp is an SDK that lets your application read COLLADA and write IFC alongside 30+ CAD and BIM formats.