Convert JT to 3DXML in your application
3D InterOp is a CAD interoperability SDK that lets your software read JT files and write 3DXML, generating the 3DXML 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 3D XML
- Mixed geometry → triangle mesh
- C++ / C# APIs
JT to 3DXML at a glance
JT can mix exact solids and facets; 3D XML stores triangles only, so the whole model is tessellated when it is written.
| JT (source) | 3D XML (target) | |
|---|---|---|
| Full name | Jupiter Tessellation | 3D XML |
| Standard / owner | Siemens, ISO 14306 | Dassault Systèmes |
| File extensions | .jt | .3dxml |
| Geometry | Tessellated and/or exact B-Rep | Tessellated geometry |
| Assemblies / structure | Yes | Yes |
| PMI | Semantic and graphical | Graphical PMI |
| 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 3D XML.
-
Preserved
Product structureThe JT product structure is written to 3DXML.
-
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.
Why software vendors add JT 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 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 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
3D InterOp tessellates the geometry it reads from JT when it writes 3DXML. Your application sets the tolerances, so it controls the trade-off between accuracy and file size.
The 3D XML writer can write graphical PMI such as views, captures and text.
Yes. 3D InterOp reads the JT 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 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 3D XML 4.3, as static tessellation.
-
Building software that needs to convert JT to 3DXML?
3D InterOp is an SDK that lets your application read JT and write 3D XML alongside 30+ CAD and BIM formats.