Convert STEP to JT

Convert a STEP model to JT when a Siemens PLM workflow, JT viewer, digital mock-up, or large-assembly review requires a lightweight 3D deliverable. JT can reduce display data substantially, but it may discard native feature history and replace precise CAD geometry with tessellation.

What the STEP format is

STEP is the ISO 10303 neutral standard for exchanging product-model data between CAD systems. A .step or .stp file can contain precise boundary-representation solids and surfaces, assemblies, component transforms, colors, layers, names, and—depending on its application protocol and source system—PMI such as dimensions and tolerances.

Siemens NX, CATIA, Creo, SOLIDWORKS, Autodesk Inventor, Fusion, Solid Edge, and other mechanical CAD systems import and export STEP. STEP is commonly used to transfer a model between incompatible CAD platforms or to retain neutral geometry alongside a native design file. It generally does not preserve the sender’s native parametric feature history, sketches, or constraints.

What the JT format is

JT is a lightweight 3D visualization and product-data format standardized as ISO 14306 and associated especially with Siemens PLM software. A JT file can contain tessellated display geometry, assembly hierarchy, metadata, colors, levels of detail, and PMI. Depending on the exporter and settings, it can also contain precise B-rep geometry; JT is not limited to polygon meshes.

JT supports progressive loading and level-of-detail representations, making large parts and assemblies faster to transmit and review than fully detailed CAD models. Siemens NX, Teamcenter, Tecnomatix, JT2Go, and other JT-capable applications can consume JT, but support for exact geometry, PMI, attributes, and editing varies by product and version. JT is an open ISO-standardized format, not an open-source format.

How to convert a STEP file to JT

Siemens NX

1. Open NX and select File → Open; choose the .step or .stp file. Use the assembly import options appropriate to the source structure.
2. Check units, component placement, missing references, surface defects, colors, and the assembly tree before exporting.
3. Use the JT export command, commonly available through File → Export → JT or the corresponding version-specific translator command.
4. Set chordal deviation or tessellation accuracy, angular tolerance, levels of detail, assembly structure, PMI, and any exact-geometry options exposed by the installed translator. Smaller deviation values retain more visible detail but increase processing time and file size.
5. Save the result as model.jt and inspect it in NX, JT2Go, or the target PLM application. Verify small holes, fillets, threads, colors, hierarchy, PMI, and part visibility.

NX is the most predictable option when the destination is Teamcenter or another Siemens workflow. JT export availability and settings depend on the NX release, translator configuration, and license.

CAD Exchanger

1. Install CAD Exchanger Desktop from the vendor’s official site and verify that the current edition and license support both STEP import and JT export.
2. Open the STEP file with File → Open, then inspect the assembly tree and select the complete model or required components.
3. Choose the JT export or save command, select the output path, and configure tessellation, units, assembly structure, and available metadata options.
4. Save the file and validate it in the application that will use it. CAD Exchanger’s supported formats and export controls can vary by product edition and release.

CAD Exchanger Cloud may provide browser-based STEP-to-JT conversion when the current service plan includes JT export. Uploading a model sends geometry to a third-party service, so confirm contractual, export-control, and confidentiality requirements before using an online converter.

Other conversion options

Datakit CrossManager and CoreTechnologie 3D Evolution are commercial desktop translators that support STEP and JT in applicable editions. Confirm the exact input, output, assembly, PMI, and B-rep capabilities with the vendor before purchasing; format support is often license-dependent.

Online conversion services are suitable for non-confidential models and quick interoperability tests, but they may impose file-size limits, remove metadata, flatten assemblies, or expose geometry to a third party. Do not use a generic file converter unless its published format list explicitly includes both STEP input and JT output.

Quality and compatibility limits

• A STEP source can contain mathematically exact analytic or NURBS surfaces, while a visualization-oriented JT export may contain only polygonal tessellation. Retain the original STEP file when downstream users need precise measurement, feature editing, or CAD reconstruction.
• Use finer tessellation or a smaller chordal deviation for holes, fillets, threads, thin walls, and sharp edges. Coarse settings can make cylinders faceted, obscure narrow gaps, or alter the apparent shape.
• Do not assume that STEP PMI, dimensions, tolerances, colors, layers, attributes, assembly constraints, or component names will transfer. Results depend on the STEP application protocol, source exporter, converter, JT options, and receiving software.
• Check units after import and export. A conversion or import setting that interprets millimeters as inches, or vice versa, can scale the entire assembly.
• Preserve assembly structure when the target workflow requires selectable components; some exporters can instead produce a flattened JT or omit suppressed and lightweight source components.
• Validate the output in the exact viewer, PLM system, or manufacturing application that will consume it. A JT viewer displaying the model does not prove that its PMI, metadata, exact geometry, or hierarchy is usable downstream.
• Keep the source STEP file and export settings with the JT deliverable so the model can be regenerated at another resolution or after source data changes.