Convert JT to DAE in your application
3D InterOp is a CAD interoperability SDK that lets your software read JT files and write DAE, generating the DAE mesh from the geometry it reads, with tessellation settings your application controls.
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 JT · Writes COLLADA
- Mixed geometry → triangle mesh
- C++ / C# APIs
JT to DAE at a glance
JT can mix exact solids and facets; COLLADA stores triangles only, so the whole model is tessellated when it is written.
| JT (source) | COLLADA (target) | |
|---|---|---|
| Full name | Jupiter Tessellation | COLLADA Digital Asset Exchange |
| Standard / owner | Siemens, ISO 14306 | Khronos Group, ISO/PAS 17506 |
| File extensions | .jt | .dae, .zae |
| Geometry | Tessellated and/or exact B-Rep | Triangle mesh |
| Assemblies / structure | Yes | Yes: scene hierarchy |
| PMI | Semantic and graphical | None |
| 3D InterOp support | Read only | Read and write |
What's preserved, what changes
Here is what your application can expect to carry across from JT to COLLADA.
-
Changes
Geometry is tessellatedThe exact JT B-Rep is replaced by a triangle mesh, generated by 3D InterOp from the exact geometry it reads. Accuracy depends on the tessellation settings your application uses.
-
Not carried
PMIDAE has no place for PMI, so the PMI read from JT isn’t written.
Why software vendors add JT 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 JT input: JT 8.x to 10.3 and 10.5 to 10.11.
- 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 JT (.jt) file?
JT is Siemens’ lightweight format for visualizing and sharing 3D product data, published as ISO 14306. A JT file can hold tessellated levels of detail, exact B-Rep, product structure and 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
3D InterOp tessellates the geometry it reads from JT when it writes DAE. Your application sets the tolerances, so it controls the trade-off between accuracy and file size.
DAE has no place for PMI, so the PMI read from JT 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.
Yes. 3D InterOp imports several levels of detail and the visual materials of JT files.
3D InterOp reads JT 8.x to 10.3 and 10.5 to 10.11.
3D InterOp writes COLLADA 1.4.1 (.dae).
No. 3D InterOp reads JT but doesn’t write it. To send data back, write a neutral format such as STEP.
-
Building software that needs to convert JT to DAE?
3D InterOp is an SDK that lets your application read JT and write COLLADA alongside 30+ CAD and BIM formats.