Convert STEP to XML

A PLM, ERP, web application, or archive system may require XML instead of a .step or .stp file. The conversion is only useful when the destination system's required XML schema is known, because XML has no single standard representation for CAD models.

What STEP is

STEP is the ISO 10303 product-data exchange standard, used by CAD, CAM, CAE, PLM, and manufacturing systems. Common files use .step or .stp and are usually ISO 10303-21 text files containing exact boundary-representation geometry, topology, product structure, units, placements, and, depending on the application protocol, colors, materials, tolerances, PMI, or other attributes.

CATIA, Siemens NX, SolidWorks, Creo, Inventor, Fusion, FreeCAD, and Open CASCADE-based applications can import or export STEP. STEP is an exchange format rather than a native parametric format, so feature history, sketches, constraints, and application-specific design data may already be absent before conversion.

What XML is

XML represents structured data with elements, attributes, namespaces, and text. An XSD can define permitted elements, data types, relationships, and required values, which makes XML suitable for metadata exchange, system integration, document repositories, PLM, ERP, and web services.

There is no universal CAD XML format. The receiving system may require an AP242 XML implementation, Siemens PLMXML, a vendor-specific schema, or a custom XML document containing only identifiers, properties, and assembly relationships. XML that is well formed but does not follow the required schema will usually be unusable.

How to convert STEP to XML

1. Obtain the destination specification. Ask the receiving system for its XSD, namespace, schema version, required units, coordinate conventions, identifier rules, and geometry requirements. Confirm whether it needs exact B-rep geometry, tessellated meshes, assembly structure, PMI, or metadata only.

2. Choose a schema-aware translator. For AP242 XML or another ISO 10303-based workflow, use a commercial STEP processor that explicitly supports that output implementation, such as STEP Tools ST-Developer, and configure the required application protocol and schema version. For PLMXML, use the PLM system's supported export, such as the configured PLMXML functions in Siemens Teamcenter or a compatible Siemens CAD/PLM product. Availability and supported fields depend on the licensed modules and release.

Open or import the model with File → Open or File → Import, select the STEP file, then select the documented XML export command. Set the schema version, units, assembly and product-property options, and any geometry representation required by the recipient. Validate the resulting file against the supplied XSD and test it in the destination application.

3. Generate custom XML when full CAD exchange is not required. FreeCAD can import STEP for inspection and can expose object names, placements, bounding boxes, labels, and custom properties through its Python API. A script using Python's xml.etree.ElementTree can serialize those values into a custom XML structure. This exports metadata, not a standards-compliant or lossless replacement for the STEP model.

For automated geometry processing, an Open CASCADE-based application or SDK can read STEP with its STEPCAF/XDE functionality and serialize selected topology, transformations, colors, attributes, or meshes into a defined schema. The serializer must be designed for that schema; changing the extension or enclosing STEP text in an XML element is not a conversion.

Online conversion options

Generic online converters commonly support STEP to STL, OBJ, 3MF, or other mesh formats, but they generally do not produce AP242 XML, PLMXML, or a recipient-specific CAD schema. Use an online service only when its documentation names the exact required XML schema, states how geometry and assemblies are represented, and provides validation or a test import. Do not upload confidential, export-controlled, or proprietary CAD data without checking retention, ownership, processing location, and security terms.

Quality and compatibility limits

Conversion can lose parametric feature history, constraints, PMI, manufacturing tolerances, exact topology, colors, materials, or assembly relationships when the target schema cannot represent them. A custom metadata XML normally preserves identifiers and properties only; retain the original STEP file as the authoritative geometry source.

Validate the XML syntactically and against its XSD, then test representative models in the receiving system. Include nested assemblies, multiple solids, non-millimeter units, mirrored components, colors, missing references, and non-ASCII names if those conditions occur in production files. Compare geometry, units, placements, part counts, and identifiers after import.