Overview#
STEP (Standard for the Exchange of Product model data, ISO 10303) is the closest thing mechanical CAD has to a universal language. Nearly every CAD, CAM, CAE and viewer program can read it. A STEP file stores exact boundary-representation solids and surfaces, the structure of assemblies, names, colors and, in some protocols, product manufacturing information (PMI) and tolerances. It does not store your feature history, sketches, parameters or constraints.
If you remember nothing else from this section: when the receiving party does not use Fusion, send STEP unless they ask for something else, and keep your own native design as the master.
This page covers what is inside a STEP file, how the application protocols differ, how to export a clean one, how to evaluate an incoming one, and the failure modes you will see in the wild.
Where to find it#
| Task | Location |
|---|---|
| Export STEP | File > Export, Type: **STEP Files (.stp, .step) |
| Open STEP | Data Panel Upload, or File > Open > Open from my computer |
| Insert STEP into an open design | Open the file as a design and use Insert into Current Design / copy-paste, or insert the uploaded cloud document as a component |
| Verify result | Inspect > Measure, Inspect > Section Analysis, Inspect > Properties (body physical properties) |
Menu paths may differ by release; verify in your version.
Step by step#
Sending a clean STEP#
- Clean the model. Delete or hide scratch bodies, reference solids, decals and sketches you do not want to transmit. Check the browser for stray bodies at the root.
- Check body health. Use the browser icons and Properties to confirm that bodies are solids, not unstitched surface sets. Surface bodies in a STEP are legal but may confuse a receiver who expected solids.
- Place the origin sensibly. Origin position and orientation travel in the file. Align the part so the origin sits at a datum the receiver will recognize.
- Name components meaningfully. Component names become part names in the receiver's browser. Names such as
Component1:1are noise. - Decide on assembly structure. A multi-component design exports as an assembly. If the receiver wants a single solid (for printing or analysis), combine bodies first or ask them to merge on their end. Save a "flattened" copy of your design for this.
- Resolve references. If the design uses external references, ensure they are all up to date and included.
- Export. File > Export, STEP.
- Round-trip test. Open the STEP in a new Fusion design, compare mass properties (volume, surface area, center of mass) with the original, and check that the part count matches.
- Name and send. Include revision and unit in the name or accompanying message.
Receiving and evaluating an incoming STEP#
- Upload the file into an "Imports" folder.
- Open it and look at the browser: how many components, how many bodies, are they solids?
- Check units with a known dimension.
- Use Inspect > Properties to see if volumes are plausible. A negative or zero volume suggests inverted or open shells.
- Look for tiny edges and sliver faces using Inspect > Zebra Analysis, section views or by zooming in on suspicious areas.
- If the model is intended for further modeling, consider creating a copy and healing it: Stitch surfaces, Delete Face to remove problem features, or Replace Face to patch gaps.
- If the file is meant for machining, move to the Manufacture workspace and set up a setup on the imported body. You do not need history for CAM.
Options reference#
| Concept | What it means | Practical note |
|---|---|---|
| AP203 | Original configuration-controlled 3D design protocol; geometry and assembly structure | Oldest; still accepted by most systems; limited color support in strict form |
| AP214 | Automotive design protocol; adds colors, layers, geometric tolerances | Very widely used in practice; common default of CAD exporters |
| AP242 | Modern merger of 203 and 214; supports semantic PMI, tessellated geometry, kinematics | Required by newer MBD workflows; support in tools varies |
| Solids vs surfaces | STEP can describe closed solids or open surface sheets | Solids are preferred for manufacturing |
| Assemblies | Hierarchical structure with transforms | Exported as a product structure; some importers flatten it |
| Colors and layers | Style data attached to faces or bodies | Usually survive AP214/AP242; may not survive AP203 |
| PMI (annotations) | Dimensions, GD&T, notes as semantic or presentation data | Fusion's support is limited; verify in your version |
| Units | Length unit declared in the header | Reliable; check anyway |
| Tolerance on geometry | Gaps below the exporter's modeling tolerance may close or open on import | Source of "invalid solid" warnings |
Which protocol Fusion writes and whether it offers a choice can differ between releases. Do not assume you can pick the protocol; if the receiver demands a specific one, ask what their tool actually fails on, and verify in your version what Fusion writes.
What STEP does well#
- Exact geometry. Cylinders remain cylinders; NURBS surfaces retain their control data. A downstream CAM system can machine true arcs.
- Assemblies. Component hierarchy and placements are preserved in typical exports.
- Interoperability. There is almost no commercial CAD system that cannot read it.
- Longevity. STEP files from decades ago still open, which is why STEP (and the related AP214/242) is common for archival.
What STEP does poorly#
- Feature history and parameters. Gone. The receiver gets dumb solids. They can still edit by direct modeling but cannot change your original sketch dimensions.
- Mates, joints and motion. Not generally carried by the common protocols. AP242 can describe kinematics in principle, but practical support is uneven.
- Sheet metal intelligence. Bend tables, rules and flat pattern definitions are lost. Send a DXF of the flat pattern separately.
- Threads and cosmetic data. Cosmetic threads in Fusion may export as plain holes. Modeled threads become real helical geometry, heavy and slow. Decide intentionally.
- Rendering data. Appearances beyond simple color do not travel.
Common failure modes#
| Symptom | Likely cause | What to try |
|---|---|---|
| Import produces surfaces, not solids | Source shells were not closed or stitched within tolerance | Run Stitch with a larger tolerance; check for gaps |
| Missing faces | Faces failed to translate | Ask the sender to export again from the native file, or to heal before export |
| Wrong units | Unit header mismatch or sender error | Rescale or reimport; verify with a known dimension |
| Tiny parts invisible | Part is 1000x smaller than expected (meters vs millimeters) | Check the unit and scale |
| Assembly flattened | Importer chose to merge | Re-import with assembly option if provided; verify in your version |
| Very slow to open | Too many faces, such as converted meshes or threaded fasteners | Suppress detail on the sending side, or request simplified geometry |
| Colors missing | AP203 or exporter option off | Re-export with colors; try AP214 |
| Duplicated parts | Instances exported as separate bodies | Fine for geometry, bad for BOM; consider requesting instanced assembly |
Tips and pitfalls#
Tip: Agree on conventions with your counterpart before the first exchange: units, origin, orientation, protocol, and whether the file should be one solid or an assembly. Write these down in the purchase order or project README.
Tip: Compare mass properties before and after the round trip. Volume agreeing to four or five significant figures is strong evidence the geometry survived.
Tip: When a receiver complains the file is "broken", ask which software and version they used and how they opened it. Many "broken" STEP files are fine and have been opened with a viewer that does not support the protocol.
Warning: A STEP file from a mesh conversion (for example, from a scanner or an STL-to-STEP service) can contain tens of thousands of triangular planar faces. It is technically a valid STEP but behaves like a mesh and bogs down CAD. Do not mistake it for a clean solid.
Warning: Do not send STEP when the receiver needs to edit the design parametrically. You are sending the end result, not the recipe. If editable history matters, consider sending native F3D if they use Fusion, or agree on an alternative workflow.
Warning: STEP does not protect intellectual property. Anyone with the file can measure and reuse geometry. Share carefully, and remove internal details you do not wish to disclose by exporting a simplified outer shell.
Tip: For very large assemblies, export subassemblies as separate STEP files. Large single files stress translators on both ends and fail more often.
Practice exercise#
- Build a small assembly in Fusion with three components, each a different color, one with a modeled thread.
- Export STEP. Note the file size.
- Replace the modeled thread with a cosmetic or plain hole, and export again. Note the change in size and import speed.
- Re-open each STEP. Verify the colors, the component count and the names.
- In the original and the re-imported design, read Properties (volume and center of mass). Record the numbers and their differences.
- Write a three-line "exchange specification" you could send to a supplier: units, protocol, structure.
Expected result: you have empirical evidence of what your STEP exports carry, and a template for specifying exchanges.
Related#
- Export workflow (export-workflow)
- Data loss and large files (data-loss-and-large-files)
- Working with other CAD users (working-with-other-cad-users)