# JT vs STEP: Lightweight Collaboration or Neutral CAD Exchange?

Compare JT and STEP for visualization, precise geometry, supplier collaboration, product structure and cross-CAD exchange, including what CADProps reads from a JT file.

JT and STEP overlap in engineering exchange, but they are optimized for different jobs. JT is strongly associated with product visualization, digital mock-up and collaboration, especially around large product structures. STEP is the more common neutral CAD handoff when the priority is exchanging precise model geometry across unrelated authoring systems.

The important complication is that a JT file can contain different representations. It may carry lightweight tessellation, product structure and other data, and some JT profiles can also include precise B-Rep geometry. A `.jt` extension therefore does not guarantee the same geometric content in every file.

CADProps reads the **triangle (tessellated) geometry** in a JT file. Exact JT B-Rep, the full JT PMI and product-structure semantics are not read, so JT properties are approximate and STEP exported from a JT is a mesh STEP.

## JT and STEP at a glance

| Question | JT | STEP |
|---|---|---|
| Common role | Visualization, collaboration, digital mock-up and product-data distribution | Neutral CAD/product-model exchange |
| Geometry representation | Can include tessellation and, depending on the file/profile, precise B-Rep | Commonly used for precise B-Rep exchange; [AP242](https://www.cadprops.com/guides/step-ap203-ap214-ap242/index.md) can carry more product data |
| Large assembly review | A major JT use case | Supported, but visualization efficiency is not STEP's only design goal |
| Mixed-vendor CAD handoff | Useful when the receiving JT workflow is known | Usually the safer default for broad CAD interoperability |
| PMI / product structure | JT can carry these in suitable profiles | STEP AP242 can carry semantic PMI/product information when exporter and importer support it |
| Native feature history | Not a portable authoring-history substitute | Not a portable authoring-history substitute |

Siemens describes JT as an openly published ISO-standard format used for 3D visualization, data exchange, supplier collaboration and long-term retention. See the [Siemens JT overview](https://www.siemens.com/en-us/products/plm-components/jt/). NIST's STEP resources show the broader standards-based product-model exchange role of STEP. See the [NIST STEP File Analyzer and Viewer](https://www.nist.gov/services-resources/software/step-file-analyzer-and-viewer).

## Choose JT when review and collaboration are the main job

JT is attractive when teams need to distribute product geometry for review without sending every native CAD master. In enterprise workflows it can support large product structures, visualization and collaboration while keeping the source authoring systems separate.

That does not mean every JT is “just a mesh.” The format can carry more than tessellation, including precise geometry in suitable representations. It also does not mean every JT contains precise solids. The sender's export profile matters.

If the task is design review, supplier visualization or PLM-oriented collaboration and both sides have a proven JT workflow, keeping JT can be more appropriate than converting everything to STEP.

## Choose STEP when neutral CAD geometry is the priority

STEP is usually the simpler default when the receiving engineer needs precise geometry in a different CAD/CAM application and you cannot assume a JT-specific workflow.

Examples include:

- a supplier using an unknown CAD system;
- a machine shop importing geometry into CAM;
- a customer who asks for a neutral model rather than a visualization deliverable;
- an internal handoff across several authoring systems where STEP has already been standardized.

STEP still needs validation. Export/import settings, application-protocol support, units and geometry translation can affect the result. A neutral format reduces vendor dependence; it does not remove the need to check the actual file.

## Why two JT files can behave very differently

The same `.jt` extension can be used for files whose practical contents differ. One export may emphasize lightweight tessellation for visualization. Another may include precise B-Rep geometry and richer product information.

Siemens' JT2Go viewer illustrates the wider JT ecosystem, including product structure and PMI capabilities. See [JT2Go](https://www.siemens.com/en-us/products/plm-components/jt/jt2go/). A generic geometry workflow should not claim those semantics unless it explicitly supports them.

For CADProps, the current support boundary is intentionally narrower:

| JT content | Current CADProps expectation |
|---|---|
| Readable triangle (tessellated) geometry | Shown with approximate properties; exports are mesh files |
| Exact JT B-Rep or Parasolid XT inside the JT | Not read |
| All JT versions and profiles | Not guaranteed |
| Full PMI semantics | Do not assume they are reproduced |
| Complete PLM/product metadata | Do not assume it is reproduced |
| Native source-CAD feature history | Not recreated |

If a JT opens in a specialist viewer but not in CADProps, first determine what representation the file contains before calling the file corrupt.

## JT-to-STEP conversion: when it helps

When the JT arrived from a collaboration system but the next application expects a neutral CAD solid, ask the source for a STEP export. A STEP that CADProps writes from a JT is a mesh STEP: useful for review and overall size, not a solid for CAM or redesign.

Use the [JT viewer](https://www.cadprops.com/tools/jt-viewer/index.md) to inspect the source first. Confirm that the expected model loaded, then compare any STEP with the source context.

At minimum, verify:

1. units and overall dimensions;
2. expected solids and major components;
3. orientation and component placement;
4. critical holes, pockets or mating surfaces;
5. volume where closed-solid volume is relevant;
6. the part/revision identity associated with the handoff.

Do not translate a tessellation-only JT to STEP and assume exact CAD geometry has somehow been recovered. A mesh and a B-Rep are different representations.

## Product structure and geometry are separate questions

An assembly can be geometrically correct while losing names, hierarchy or metadata that matter to the receiving workflow. Conversely, a product structure can display correctly even when the precise B-Rep needed for machining is absent.

Before choosing JT or STEP, ask what the recipient actually needs:

- only visual review;
- assembly navigation;
- accurate measurements;
- precise solid geometry for CAM or redesign;
- PMI/GD&T;
- long-term archive data;
- a lightweight model for many reviewers.

The format decision should follow that requirement rather than a blanket rule that one format is “better.”

## Which is better for supplier handoff?

If a supplier uses a JT-capable collaboration/PLM workflow and the contract defines the JT content, JT can be an excellent review deliverable. It is especially useful when large assemblies must be distributed efficiently to many participants.

If suppliers use mixed CAD/CAM systems and the main requirement is reusable precise geometry, STEP is usually easier to standardize. For many small and medium manufacturing handoffs, that portability matters more than JT-specific collaboration features.

Either way, send revision context with the geometry. A supplier needs to know which released part or assembly the model represents and which drawing/specification controls tolerances and manufacturing requirements. The [supplier CAD handoff guide](https://www.cadprops.com/guides/share-cad-files-with-suppliers/index.md) covers those accompanying checks.

## Do not infer precision from the extension

A `.jt` filename does not tell you whether precise B-Rep is present. A `.step` filename does not prove that every desired attribute survived export. Validation should inspect the actual model received.

For a JT source in CADProps, treat volume as an estimate from triangles and any STEP export as a mesh. For a STEP source, verify units, bodies/components and known dimensions in the receiving workflow.

If the job depends on native parametric editing, neither neutral deliverable should replace the original authoring files.

## What this site accepts from a JT file

CADProps reads the triangle levels of detail stored in a JT file and shows parts and assemblies from them. Dimensions, area and volume are approximate. Exact JT B-Rep, PMI, PLM product structure and the original feature tree are not read. Files without readable triangle geometry cannot be shown. Do not rename another format to `.jt` to force a read.

Use the [JT viewer](https://www.cadprops.com/tools/jt-viewer/index.md). After signing in, Convert offers mesh STEP, STL, OBJ, 3MF, glTF and GLB. Mass still requires a density you confirm. The [JT format hub](https://www.cadprops.com/jt/index.md) collects the viewer and these checks.

## Quick decision rule

Use **JT** when:

- visualization and collaboration are primary;
- large product structures need efficient review;
- the organization already has a defined JT profile/workflow;
- the receiver needs JT-specific product context and has software that explicitly supports it.

Use **STEP** when:

- the receiver uses an unknown or different CAD system;
- precise neutral geometry is the core deliverable;
- the file is going into a broad supplier or CAM chain;
- STEP is already the organization's validated interoperability standard.

When converting between them, use the [CAD conversion checklist](https://www.cadprops.com/guides/cad-conversion-checklist/index.md) and verify the representation you actually received rather than assuming that matching file extensions imply matching engineering content.

## Separate the available representation from the recipient's requirement

Before converting a supplied JT, ask its author which representation was exported and which one the recipient needs. A collaboration preview may be entirely adequate for an appearance review while being unsuitable for the requested solid-based CAM handoff.

After conversion, reopen the actual STEP output rather than comparing only thumbnails. If the geometry is present but required PMI or hierarchy is absent, record that as an unmet handoff requirement even when dimensions agree. Request a source-CAD STEP export when the recipient needs exact solids, PMI or product structure.

## Sources

- [Siemens — JT file format](https://www.siemens.com/en-us/products/plm-components/jt/)
- [NIST STEP File Analyzer and Viewer](https://www.nist.gov/services-resources/software/step-file-analyzer-and-viewer)
- [Siemens — JT2Go JT file viewer](https://www.siemens.com/en-us/products/plm-components/jt/jt2go/)

## Related reading

- [3MF vs STEP: Additive Manufacturing Package or Exact CAD Exchange?](https://www.cadprops.com/guides/3mf-vs-step/index.md)
- [CAD File Conversion Checklist: Units, Solids & Accuracy](https://www.cadprops.com/guides/cad-conversion-checklist/index.md)
- [Does a STEP File Contain a BOM? Structure, Names and Quantities](https://www.cadprops.com/guides/does-step-file-contain-bom/index.md)
- [Does a STEP File Contain Material? What You Can Trust](https://www.cadprops.com/guides/does-step-file-contain-material/index.md)
- [JT File (.jt): What It Is and How to Open It Online](https://www.cadprops.com/guides/open-jt-file-online/index.md)
- [Share CAD Files with Suppliers: STEP Handoff Checklist](https://www.cadprops.com/guides/share-cad-files-with-suppliers/index.md)
- [STEP AP203 vs AP214 vs AP242: Which Protocol to Export](https://www.cadprops.com/guides/step-ap203-ap214-ap242/index.md)

Original article: https://www.cadprops.com/guides/jt-vs-step/

HTML page: https://www.cadprops.com/guides/jt-vs-step/