Convert JT to XCGM in your application
3D InterOp is a CAD interoperability SDK that lets your software read JT files and write XCGM, carrying across the exact geometry the JT file contains.
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 XCGM
- Mixed geometry → exact geometry
- C++ / C# APIs
JT to XCGM at a glance
JT can mix exact solids and facets; XCGM stores exact geometry. Exact elements are written as exact geometry, and elements stored only as facets stay faceted.
| JT (source) | XCGM (target) | |
|---|---|---|
| Full name | Jupiter Tessellation | CGM native file |
| Standard / owner | Siemens, ISO 14306 | Dassault Systèmes / Spatial (CGM Modeler) |
| File extensions | .jt | .xcgm |
| Geometry | Tessellated and/or exact B-Rep | Exact B-Rep |
| Assemblies / structure | Yes | Yes |
| PMI | Semantic and graphical | Semantic (read) |
| 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 XCGM.
-
Preserved
Exact geometryExact B-Rep read from JT is written to XCGM as exact geometry.
-
Changes
Faceted partsParts the JT file stores only as facets are written as facets.
-
Not carried
PMI3D InterOp doesn’t write PMI to XCGM, so the PMI read from JT isn’t written. Keep STEP AP242 as an output when PMI matters.
Why software vendors add JT to XCGM conversion
Hand models to kernel-based applications
Many CAD, CAM and CAE applications are built on the XCGM kernel. Writing XCGM gives them exact geometry they can load without another translation step.
Downstream modeling and analysis
An exact XCGM B-Rep can still be edited, meshed or machined by downstream tools, which a tessellated export would not allow.
Exchange within one ecosystem
Partners whose tools share the XCGM kernel often prefer to exchange XCGM files directly.
Things to check before you ship
- Written XCGM versions: R2012 to 2025 1.0.
- PMI and miscellaneous data aren’t written to XCGM.
- Supported JT input: JT 8.x to 10.3 and 10.5 to 10.11.
- 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 an XCGM (.xcgm) file?
XCGM is the native file format of the CGM geometric kernel, used by CGM Modeler and Dassault Systèmes applications. It stores exact B-Rep geometry.
Frequently asked questions
The exact B-Rep that 3D InterOp reads from JT is written to XCGM; parts stored only as facets stay faceted.
3D InterOp doesn’t write PMI to XCGM, so the PMI read from JT isn’t written. When PMI matters, offer STEP AP242 as an output.
No. PMI and miscellaneous data aren’t written to XCGM.
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 R2012 to 2025 1.0.
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 XCGM?
3D InterOp is an SDK that lets your application read JT and write XCGM alongside 30+ CAD and BIM formats.