STEP-XML

Technical explanation

What is STEP-XML?

STEP-XML belongs to the broader STEP (ISO 10303) family, which is used for exchanging product model data across engineering systems. Part 28 of the standard focuses specifically on using XML to represent schemas defined in EXPRESS and the product data that follows those schemas.

How is it different from a standard STP file?

A traditional STEP file usually refers to the ISO 10303-21 clear-text exchange format, commonly stored with .stp or .step extensions. STEP-XML is a different implementation method: it expresses STEP data in XML rather than in the classic Part 21 syntax. Both belong to STEP, but they are not the same encoding.

How does STEP-XML work?

ISO 10303-28 covers both schema-independent and schema-specific XML representations. In practice, that means STEP-XML can support a more generic XML structure that works across EXPRESS schemas, as well as XML structures tailored to a specific schema. The standard also defines mappings between these forms.

Common file extensions and structure

STEP-XML files commonly use the .stpx extension for uncompressed files and .stpxz for compressed files. The format uses XML's hierarchical nature to represent complex assemblies and product structures, and in some workflows the XML file can reference external CAD files rather than embedding all geometry directly. This referencing approach is especially relevant in environments where product structure and linked representations need to travel together while the underlying CAD data remains in its native format.

Applications and industry use cases

STEP-XML is useful in engineering workflows that need structured product-data exchange but also benefit from XML-based processing: integration pipelines, schema-aware validation, and application-to-application data exchange. NIST has noted XML's advantages as an exchange medium for STEP data.

In practice, STEP-XML adoption has been driven by aerospace and automotive industries, particularly around workflows involving Dassault Systemes' 3DEXPERIENCE platform. Common use cases include migrating data from legacy PDM/CAD systems to 3DEXPERIENCE, synchronizing design review and analysis data across collaboration environments, and maintaining digital thread continuity when multiple applications participate in a CMM or inspection workflow.

For software developers, STEP-XML is relevant when building CAD interoperability tools, data-processing services, digital thread workflows, or applications that need to ingest STEP data in a form that works naturally with XML tooling. It is also useful when product structure and linked external references matter as much as raw geometry.

Challenges or common pitfalls

A common source of confusion is assuming that STEP-XML is just another name for a standard .stp file. Both are STEP exchange methods, but they are defined by different parts of ISO 10303 and use different encodings. Software that reads Part 21 STEP files will not automatically read STEP-XML, and vice versa.

Another pitfall is underestimating the role of the underlying EXPRESS schema. STEP-XML changes the encoding, not the semantic complexity of the product data. Your application still needs schema-aware interpretation to make sense of what is in the file.

Teams should also watch for assembly portability issues. Because STEP-XML can reference external CAD files rather than embedding everything in one document, successful exchange depends on managing those linked files correctly. If the referenced files are missing, moved, or in an unsupported format, the assembly will not load completely. This is a practical concern that does not exist with self-contained Part 21 STEP files.

How Spatial helps

We support STEP-XML through 3D InterOp, our CAD interoperability SDK. STEP-XML reading is fully integrated into 3D InterOp alongside our existing STEP Part 21 support, so your application can handle both encodings through the same architecture.

3D InterOp reads STEP AP242 XML files, including their external references to CAD files and derivative representations. That external-reference handling is a practical requirement for STEP-XML workflows, because the format is often used as a structural container that links out to native CAD data, tessellated representations, or other documents rather than embedding everything inline.

When 3D InterOp reads the referenced CAD files, the same import pipeline applies: automatic healing (topology repair, geometry refinement, gap closure), native geometry generation for ACIS, CGM, and Parasolid kernels, and PMI extraction where available. The result is geometry your application can work with as if it were created natively, regardless of whether the source was a STEP-XML assembly reference or a standalone CAD file.

Our selective import API works with STEP-XML the same way it works with other formats. Your application can load product structure, tessellated geometry, exact B-rep geometry, or manufacturing information independently, rather than pulling in every referenced file and every representation at once. For large STEP-XML assemblies with many external references, this control over what gets loaded matters for both memory and performance.

Because 3D InterOp reads and writes more than 30 CAD, BIM, mesh, and visualization formats, STEP-XML handling fits into a larger pipeline. An application that already uses 3D InterOp for CATIA, NX, SOLIDWORKS, Creo, JT, or standard STEP files picks up STEP-XML support through the same SDK and the same abstract interface.

👉 Learn more: What is an STP file?

Over 300 companies have used 3D InterOp across more than 20 years.

You can request an evaluation here.