Supported formats

Neutral Kernel Native
  • IFC
  • IGES
  • JT
  • OBJ
  • STEP
  • STL
  • VRML
  • 3DS
  • Collada
  • DXF
  • FBX
  • glTF
  • X3D
  • ACIS
  • BRep
  • Parasolid
  • Rhino
  • Solidworks

Details

Format File extensions Read/Write BRep Mesh Notes
3DS .3ds R check_icon
ACIS
(R2.0 and newer)
.sat, .sab RW check_icon Recommended for data exchange with Autodesk products and ACIS-based applications
BRep .brep RW check_icon Recommended for data exchange with OCC-based applications
Collada R check_icon
DXF .dxf W check_icon
FBX
(2012 and newer)
.fbx RW check_icon Recommended for data exchange with Unity and Autodesk Maya
glTF W check_icon Recommended for data exchange with three.js
IFC
2x3, 4
.ifc R check_icon AEC/BIM applications
IGES
(all)
.igs, .iges RW check_icon
JT
v8.0-v10.x
.jt RW check_icon check_icon Recommended for data exchange with NX
OBJ .obj RW check_icon
Parasolid
(up to v32)
.x_t, .x_b,
.xmt_txt,
.xmt_bin,
.xmp_txt,
.xmp_bin
RW check_icon Recommended for data exchange with SolidWorks, SolidEdge, NX and other Parasolid-based applications
Rhino
(up to v6)
.3dm RW check_icon check_icon Recommended for data exchange with Rhinoceros and Grasshopper
Solidworks
(2004 and newer)
.sldpart, .sldasm R check_icon
STEP
AP203, 214, 242
.stp, .step RW check_icon check_icon Recommended for data exchange with CATIA and when ACIS/Parasolid/Rhino do not apply
STL
(text and binary)
.stl RW check_icon Often used in 3D printing or scanning. The least data-rich format.
VRML
v1/1995, v2/1997
.wrl RW check_icon
X3D .x3d W check_icon

For further details on capabilities and supported scope of each format refer to CAD Exchanger SDK documentation

Parts and assemblies

  • Depending on format capabilities, CAD Exchanger supports both parts and assemblies.
  • Files with external references (in STEP, JT, Solidworks and other applicable formats) are supported.

B-Rep and meshes

  • All types of geometries are supported – analytical, NURBS and procedural.
  • Triangulations, polylines and point clouds are supported.

Converting between B-Rep and meshes

  • When converting B-Rep (precise geometry) to mesh-only formats (e.g. IGES to STL) the mesh generator is applied to each B-Rep body. Depending on target format capabilities it can be either single or multiple meshes per B-Rep (the multi-LOD, or Level of Details concept).
  • When converting B-Rep & mesh formats to mesh-only formats (e.g. JT to OBJ), a specific LOD in the source file is used.
  • When converting mesh-only to B-Rep & mesh formats (e.g. VRML to JT), only the mesh is used.
  • Converting a mesh-only to B-Rep-only format (such as STL to Parasolid) effectively has a very low value and thus is not recommended. When enforced, the conversion creates a B-Rep body consisting of faces per each original mesh triangle. Such a B-Rep can merely be used for visualization purposes but not for modeling. Refer to details.

Meta-data

  • Depending on format capabilities, CAD Exchanger supports names, persistent id’s, user-defined properties, colors, materials and textures.

PMI (Product and Manufacturing Information)

  • Whenever applicable, PMI is supported at all three levels: as graphical PMI, semantic PMI and associations with B-Rep elements (such as face or edge).