Convert DAE to 3DXML in your application
3D InterOp is a CAD interoperability SDK that lets your software read DAE files and write 3DXML, carrying the mesh data across without re-tessellating it.
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 3D XML
- Triangle mesh → triangle mesh
- C++ / C# APIs
DAE to 3DXML at a glance
Both formats store triangles, so the facets carry over without re-tessellation. The differences are in structure, appearance and metadata.
| COLLADA (source) | 3D XML (target) | |
|---|---|---|
| Full name | COLLADA Digital Asset Exchange | 3D XML |
| Standard / owner | Khronos Group, ISO/PAS 17506 | Dassault Systèmes |
| File extensions | .dae, .zae | .3dxml |
| Geometry | Triangle mesh | Tessellated geometry |
| Assemblies / structure | Yes: scene hierarchy | Yes |
| PMI | None | Graphical PMI |
| 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 3D XML.
-
Preserved
Mesh dataThe DAE facets are read and written to 3DXML without being re-tessellated.
-
Preserved
Product structureThe DAE product structure is written to 3DXML.
Why software vendors add DAE to 3DXML conversion
Lightweight review
3D XML carries tessellated geometry that opens much faster than the full CAD model, so design reviews and digital mockups stay responsive.
Sharing outside engineering
Marketing, training and sales teams rarely have CAD software. A 3D XML file gives them the shape in a format their tools can open.
Easier handling of large assemblies
Without exact surfaces and feature data, 3D XML files are easier to transfer and display, even for large assemblies.
Things to check before you ship
- Written 3DXML versions: 3D XML 4.3, as static tessellation.
- Only static tessellation is written, not XML tessellation.
- Supported DAE input: COLLADA 1.4.1, .dae and .zae.
- Test tessellation settings on your heaviest parts: finer meshes mean larger files.
- 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 a 3D XML (.3dxml) file?
3D XML is Dassault Systèmes’ lightweight XML-based format for sharing 3D product data. 3D InterOp reads and writes its tessellated representation, with product structure and graphical PMI.
Frequently asked questions
No re-tessellation is needed. 3D InterOp reads the DAE facets as visualization data and writes them to 3DXML.
Yes. 3D InterOp reads the DAE product structure and writes it to 3DXML.
3D InterOp writes 3D XML 4.3 with static tessellation. XML tessellation isn’t written.
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 3D XML 4.3, as static tessellation.
Yes. 3D InterOp reads and writes both formats, so 3DXML to DAE is supported too.
-
Building software that needs to convert DAE to 3DXML?
3D InterOp is an SDK that lets your application read COLLADA and write 3D XML alongside 30+ CAD and BIM formats.