Convert 3DXML to DAE in your application
3D InterOp is a CAD interoperability SDK that lets your software read 3DXML files and write DAE, 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 3D XML · Writes COLLADA
- Triangle mesh → triangle mesh
- C++ / C# APIs
3DXML to DAE at a glance
Both formats store triangles, so the facets carry over without re-tessellation. The differences are in structure, appearance and metadata.
| 3D XML (source) | COLLADA (target) | |
|---|---|---|
| Full name | 3D XML | COLLADA Digital Asset Exchange |
| Standard / owner | Dassault Systèmes | Khronos Group, ISO/PAS 17506 |
| File extensions | .3dxml | .dae, .zae |
| Geometry | Tessellated geometry | Triangle mesh |
| Assemblies / structure | Yes | Yes: scene hierarchy |
| PMI | Graphical PMI | None |
| 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 3D XML to COLLADA.
-
Preserved
Mesh dataThe 3DXML facets are read and written to DAE without being re-tessellated.
-
Not carried
PMIDAE has no place for PMI, so the PMI read from 3DXML isn’t written.
Why software vendors add 3DXML to DAE conversion
Lightweight review
COLLADA 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 COLLADA file gives them the shape in a format their tools can open.
Easier handling of large assemblies
Without exact surfaces and feature data, COLLADA files are easier to transfer and display, even for large assemblies.
Things to check before you ship
- Written DAE versions: COLLADA 1.4.1 (.dae).
- The DAE writer is available through the UConnect interface only.
- Supported 3DXML input: 3D XML 4.0 to 4.3 (tessellated data only).
- B-Rep stored in authoring-mode 3D XML files isn’t imported: only the tessellation is read.
- 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 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.
-
Target 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.
Frequently asked questions
No re-tessellation is needed. 3D InterOp reads the 3DXML facets as visualization data and writes them to DAE.
DAE has no place for PMI, so the PMI read from 3DXML isn’t written. Your application can still access it after import, or offer STEP AP242 as an output.
The DAE writer is available through the 3D InterOp UConnect interface.
No. B-Rep stored in authoring-mode 3D XML files isn’t imported: 3D InterOp reads the tessellation only.
3D InterOp reads 3D XML 4.0 to 4.3 (tessellated data only), as visualization data.
3D InterOp writes COLLADA 1.4.1 (.dae).
Yes. 3D InterOp reads and writes both formats, so DAE to 3DXML is supported too.
-
Building software that needs to convert 3DXML to DAE?
3D InterOp is an SDK that lets your application read 3D XML and write COLLADA alongside 30+ CAD and BIM formats.