# Threads Missing from a STEP File? Geometry, PMI and Shop Handoffs

Understand why thread callouts can disappear in STEP handoffs, how modeled and cosmetic threads differ, what AP242 PMI can carry, and what to send a machine shop.

This guide covers general CAD workflows. CADProps supports STEP, IGES, SolidWorks parts and ZIP assemblies, STL, OBJ, 3MF and static GLB/GLTF. Validated conversions are downloadable. Partial assemblies carry warnings; properties cover loaded geometry only.

A STEP model can show a perfectly round hole while telling the receiver almost nothing about the thread that belongs there. That is not necessarily a damaged file. It is often a mismatch between **visible geometry**, **CAD feature semantics**, and the information that was actually exported.

This distinction matters in machining. A cylindrical bore with a nominal diameter is not enough to infer whether the requirement is M8 × 1.25, M8 × 1, 5/16-18 UNC, a pipe thread, a helicoil preparation, or simply an unthreaded hole. Pitch, class, handedness, thread depth and inspection requirements are manufacturing intent, not facts that should be guessed from a cylinder.

CADProps therefore treats thread information conservatively. The current STEP workflow can inspect geometry and supported simple hole features, but it does **not** infer a thread standard or pitch from a plain cylindrical face. If the thread requirement is important, verify the specification supplied with the model.

## Why a thread can disappear while the hole remains

Native CAD systems do not all represent threads the same way. Autodesk Fusion, for example, explicitly distinguishes **cosmetic** threads from **modeled** threads in its Thread feature. A cosmetic thread carries design information without creating the complete helical solid geometry; a modeled thread changes the geometry itself. See Autodesk's [Thread reference](https://help.autodesk.com/cloudhelp/ENU/Fusion-Model/files/GUID-C37E8172-DE94-4EB0-AFE3-9D3172328441.htm).

That difference explains a common exchange surprise:

1. the source CAD model knows that a hole is threaded;
2. the shaded model may display a thread symbol or annotation;
3. the exported STEP contains the cylindrical hole geometry;
4. the receiving application loads the shape correctly;
5. the thread designation is absent because the semantic or annotation data was not included, not supported, or not interpreted.

The reverse can also happen. A modeled helical thread may be part of the exported shape, but the receiver still may not know the intended standard, fit class or inspection callout. Geometry alone is not a reliable substitute for a thread specification.

## STEP is capable of carrying more than plain geometry

It is too broad to say that “STEP cannot contain tolerances or manufacturing information.” Modern STEP AP242 workflows can carry Product and Manufacturing Information (PMI). NIST's [STEP File Analyzer and Viewer](https://www.nist.gov/services-resources/software/step-file-analyzer-and-viewer) describes both graphical and semantic PMI, including machine-interpretable dimensional and tolerance information.

The practical issue is **interoperability**, not only format capability. The exporter has to write the relevant information, the selected STEP application protocol and edition must support it, and the receiving software must read it correctly.

An industry guideline from prostep ivip makes the thread case especially clear. Its 2025 JT content-harmonization guidance, which also discusses STEP AP242, recommends semantic PMI for thread information rather than unnecessarily detailed helical geometry, while noting that some translators may fall back to graphical PMI. See the [JT Content Harmonization Guideline](https://www.prostep.org/fileadmin/prod-pay-download-8c1d/JT_Content_Harmonization_Guideline_2025-12-18_FINAL.pdf).

The useful lesson is not “always model threads” or “never model threads.” It is: **decide which information the downstream process needs and verify that the chosen exchange path preserves it.**

## What can be trusted from a plain cylindrical hole?

A clean B-Rep hole can support useful geometric checks. If the STEP file contains an analytic cylindrical face, a compatible geometry engine can read its radius directly. That can establish the nominal cylinder diameter more reliably than measuring pixels from a screenshot.

But a cylinder does not establish:

- thread family or standard;
- pitch;
- internal thread class;
- right- or left-hand direction;
- full or partial thread depth;
- allowance, plating compensation or insert requirement;
- tapping process;
- thread gauge or inspection requirement.

The [STEP hole recognition guide](https://www.cadprops.com/guides/step-hole-recognition/index.md) explains the narrower geometry CADProps currently recognizes: simple full cylindrical through holes and flat-bottom blind holes that pass conservative single-solid checks. A recognized hole is still not automatically a threaded hole.

## A better way to send threaded parts for quotation

If the recipient is a machine shop and you have not agreed on a model-based AP242 PMI workflow, send the geometry together with an authoritative thread specification.

A practical package usually contains:

| Item | What it should answer |
|---|---|
| STEP model | What is the nominal 3D shape? |
| Drawing or agreed PMI deliverable | Which holes are threaded, and to what specification? |
| Revision identifier | Which model and specification belong together? |
| Material / finish specification | What stock and post-processing assumptions affect the quote? |
| Quantity | What production context is being priced? |

For a drawing-based handoff, a callout such as `M8 × 1.25 - 6H, 12 mm MIN FULL THREAD` is meaningful in a way that a rendered helix alone is not. The exact callout syntax and required detail depend on the governing drawing standard and your organization; do not copy that example blindly into a released drawing.

The broader [STEP file for CNC quote checklist](https://www.cadprops.com/guides/prepare-step-file-for-cnc-quote/index.md) covers the rest of the RFQ package.

## Should you model the helical thread in 3D?

Sometimes—but not simply to make the STEP file “look complete.”

Detailed helical threads increase geometric complexity and file size. They can make tessellation, collision checks and downstream operations heavier. For many ordinary fastener holes, a semantic designation or drawing callout communicates manufacturing intent more efficiently.

Modeled threads are useful when the actual geometry is functionally important to the downstream task: for example, clearance/interference analysis, additive manufacturing where the thread will be printed, a nonstandard thread form, or a process that explicitly requires the true shape.

Even then, pair the geometry with the intended specification. A beautiful helix does not certify pitch tolerance or fit.

## Check the handoff before sending it

A fast verification sequence is more valuable than assuming the export worked:

1. Reopen the exported STEP in a reader that is not the source CAD application.
2. Confirm the expected part, revision and units.
3. Check overall dimensions in the [STEP viewer](https://www.cadprops.com/tools/step-viewer/index.md).
4. Inspect the threaded-hole locations and nominal cylinder diameters.
5. Confirm whether thread annotations or semantic PMI are actually present in the receiving workflow.
6. Compare the STEP against the controlling drawing or model-based definition.
7. Send both artifacts together when the STEP alone does not carry the complete manufacturing requirement.

NIST's STEP tools are particularly useful when you need to determine whether a STEP file contains semantic or graphical PMI rather than merely assuming it does.

## Do not reverse-engineer a thread callout from a diameter

This is the failure mode to avoid. A measured hole diameter may be compatible with several thread preparations, tap-drill choices or non-threaded fits. The CAD geometry may also represent a simplified cosmetic hole rather than the final minor diameter.

If the thread callout is missing, ask for the source specification. Do not let an automatic recognizer silently turn “cylindrical hole, Ø6.8 mm” into “M8 × 1.25.” That kind of inference can look clever in software and still be wrong on the shop floor.

The correct automation boundary is straightforward: extract what is explicit, flag what is missing, and make uncertainty visible. That principle applies to threads, tolerances, materials and every other manufacturing attribute that cannot be proven from shape alone.

## Related reading

- [Annotate a CAD Model Online and Share Review Notes](https://www.cadprops.com/guides/annotate-cad-model-online/index.md)
- [Autodesk Fusion AutoTimeline: Why CAD Feature Recognition Matters Again](https://www.cadprops.com/guides/autodesk-fusion-autotimeline-feature-recognition/index.md)
- [STEP File Scale Wrong by 25.4? Fix Inch and mm Units](https://www.cadprops.com/guides/cad-model-wrong-scale-25-4/index.md)
- [Prepare a STEP File for a CNC Quote: A Shop-Ready RFQ Checklist](https://www.cadprops.com/guides/prepare-step-file-for-cnc-quote/index.md)
- [Share CAD Files with Suppliers: STEP Handoff Checklist](https://www.cadprops.com/guides/share-cad-files-with-suppliers/index.md)
- [STEP AP242 Edition 4 in 2026: What It Means for CAD Handoffs](https://www.cadprops.com/guides/step-ap242-edition-4-2026/index.md)
- [STEP Hole Recognition: Detect Through and Blind Holes](https://www.cadprops.com/guides/step-hole-recognition/index.md)

Original article: https://www.cadprops.com/guides/threads-missing-from-step-file/

HTML page: https://www.cadprops.com/guides/threads-missing-from-step-file/