Home > Supported File Formats > STEP to COLLADA

How to convert STEP (.step,.stp) to COLLADA (.dae)?

PolyTrans|CAD+DCC performs mathematically precise CAD, DCC/Animation, GIS and BIM 3D file conversions into all key downstream 3D packages and file formats. Okino software is used and trusted throughout the world by many tens of thousands of 3D professionals in mission & production critical environments, backed by respectable personal support directly from our core development team.

STEP

STEP is the defacto 'go-to' MCAD translation file format when you do not have access to the original CAD part and assembly files. It is a long standing 'industry standard' that can be used to move MCAD/CAD file assets into many downstream 3D programs and file formats. Okino's PolyTrans|CAD provides for a defacto 3D STEP file conversion solution used by the world's primary & professional engineering, aerospace, military, corporate, animation/multi-media and VR/AR industries. STEP uses the .stp and .step file extensions.

STEP files are readable ASCII files which encode CAD parts and assembly information. Most respectable MCAD modellers will actively and correctly support the STEP AP203 and AP214 file formats. STEP was originally developed to supercede the IGES file format but has mostly supplemented but not replaced IGES. You would either want to export a "STEP AP214" file or an "IGES BREP solids" file depending on the MCAD modeller.

A much deeper overview plus explanation of STEP, and how it can be best used + understood, is outlined in this Okino WEB page.

Most people initially come to Okino asking for a STEP importer but it should only be used in specific situations as outlined in our "CAD Data Sourcing Suggestons and Rules".

COLLADA

COLLADA (DAE) is a XML-based readable file format of the 2007/2008 era which had an original goal of allowing efficient cross conversion of 3D asset data between all of the major 3D DCC/Animation systems of that era. Many 3D software programs came to implement COLLADA but with varying levels of comformity and data reliability. COLLADA is more generally known as a polygonal mesh file format and not a MCAD/CAD/AEC/GIS format. Today people would usually use FBX over COLLADA, depending on the quality of the associated (and dated?) import/export converters.

Okino created one of the key implementations of the COLLADA file format in its import and export converters. However, it saw little need for them except for exporting into Cinema-4D from 2008 to 2012, as the primary gateway into Google Earth, and as our still-preferred method to move 3D assets into Blender (rather than FBX). COLLADA does have its place in these current and prior times.

Okino has a unique take on the COLLADA file format as Okino was at the very center of the DCC/Animation conversion world. In 2007 Rémi Arnaud and Mark Barnes argued that yet-another 3D file format was required and hence Sony funded their efforts to define COLLADA for the cross conversion of assets between (initially) 3ds Max and Maya. However, what they conveniently ignored was that Okino already had the defacto cross conversion system in place, for the prior decade, based on its BDF (binary data translation file format) for 3ds Max, Maya, Cinema-4D, Softimage, LightWave and others. In the mid 2000's there was a "not invented here" mindset and hence everyone wanted to stamp/force their own 3D file format on the industry: FBX (Autodesk), COLLADA (Sony), 3dxml (Dassault Systems), XAML-3D (Microsoft), U3D (Adobe and Intel), etc. There was little need or reason to have "yet-another" set of new 3D file formats. All, except FBX, would basically come and go as of 2007/2008. The implosion of the DCC/Animation industry of 2005-2007 and the 2008/2009 recession further hampered the long term adoption or need for COLLADA over Autodesk's FBX.

COLLADA is/was a very fine file format but it was really not needed at the time of its introduction in 2007. It only introduced yet-more confusion to the 3D graphics market as to which 3D file format to use to transfer 3D assets between packages. Developers generally implemented v1.4 of the COLLADA file specification then lost interest thereafter.

However, as a saving grace for COLLADA, all of the 3D software packages which had implemented a good COLLADA exporter became instant gateways to move their 3D assets into the then-new glTF file format of the mid 2010s, until such time that these same packages could add in their own glTF exporters.

More information about STEP

STEP import converter's overview

COLLADA export converter's overview