STL vs STEP: Which Revision and Editing Information Matter?

STEP and STL usually serve different handoff stages. A suitable STEP exchange can carry engineering geometry for another CAD workflow; STL carries a faceted derivative. Keep the agreed design revision and distinguish editable imported bodies from the original application's feature history.

Who needs to edit what?

A recipient changing a hole position needs a different source from a recipient slicing an approved mesh. Establish whether the handoff requires the native application's sketches and constraints, editable imported geometry, or only a reviewed triangle surface. A filename alone does not establish revision authority.

Authority and retained information

STEP is neither a guarantee of the complete parametric master nor an inherently uneditable file. Retained entities, assembly handling, units and editing operations depend on the schema, exporter and receiver. A project may agree that a particular STEP revision controls; another may keep native CAD authoritative. Record that agreement before accepting downstream changes.

One source-to-derivative case

Hypothetical requirement: a bracket has a named 40 mm hole-centre spacing. Verify that dimension from its CAD references before meshing. If a receiving CAD application offers direct body edits, changing the imported holes still does not prove it recovered the original sketch constraints.

Export the approved revision with documented tessellation settings. The STL can approximate the holes with facets while retaining overall bounds. Two clicked triangle points do not establish the exact analytic centre spacing; matching width does not prove the holes are unchanged. For a dimensional revision, return to the agreed source rather than treating a mesh patch as an undocumented master change.

Keep the source and delivery revisions linked, with export settings and a named reference feature. If the recipient modifies the imported body, require a revised authority decision and generate a new reviewed derivative. An old STL should not remain silently attached to a changed source design.

Approve the receiving path

1. Identify the authoritative revision, required bodies and intended editing operations.
2. Open the exchange in the receiving CAD application; record its version, unit handling and any absent entities.
3. If the receiver accepts STEP for printing, ask how it tessellates and review the resulting mesh or preview. Import support is application-specific.
4. Compare the actual saved derivative's critical geometry, dimensions and mesh findings, then review the final sliced layers.

Stop when a required body is absent, a unit differs or an intended edit cannot be represented by the receiver. Counts and bounds are useful screening observations, not proof of equivalent engineering geometry or physical fit.

Use the implementation owners

After a source application exports STL, open the saved derivative in STL Viewer to inspect visible features and overall bounds locally. InspectMesh does not open the STEP source.

InspectMesh does not parse or convert STEP. Use the CAD-to-STL export checklist for application steps and the chord-height and angle guide for tessellation decisions. Keep those operations separate from this choice of revision authority. Record the receiving check and compare STL with 3MF if the remaining decision concerns print geometry rather than CAD editing.

Technical context reviewed 27 October 2026: NIST's historical introduction to ISO 10303 STEP. It explains product-data exchange, not current importer compatibility or a promise that every schema preserves native history. No named external CAD import was executed for this example.