Convert IGES
to CAD

Technical Explanation

What is IGES?

IGES stands for Initial Graphics Exchange Specification. It was introduced to support data exchange between dissimilar CAD/CAM systems, and Autodesk still describes it as a neutral format for transferring 2D and 3D drawing data between different CAD systems.

See more about IGES: What is an IGES file?

What does "to CAD" mean?

"CAD" is not a single file format. In this context, converting IGES to CAD usually means converting IGES geometry into another CAD-oriented target such as STEP/STP, ACIS/SAT, DXF/DWG, or into native kernel geometry used internally by an engineering application. Spatial's glossary page for this keyword also treats "CAD" as a family of target formats rather than one extension.

That distinction matters because the target determines what the conversion is trying to preserve. A workflow targeting exact B-rep geometry for modeling is not the same as a workflow targeting lightweight visualization or downstream printing.

See more about CAD: CAD File Format

How does the conversion work?

At a high level, the converter reads the IGES entities from the source file, interprets the geometric and structural information they contain, and maps that data into the destination CAD representation. A successful conversion does more than parse the file: it must also create geometry that is valid enough for downstream operations such as modeling, Boolean operations, queries, meshing, or further export.

In many engineering applications, the most useful outcome is not merely "opening" the IGES file but generating native target geometry.

Why IGES conversion can be difficult

IGES was designed for broad exchange, but support can vary by entity, attribute, and feature set. NIST's validation materials explicitly refer to different levels of support for IGES constructs, attributes, entities, and entity forms, which is one reason real-world interoperability can vary from system to system.

There is also a practical limitation on round-tripping. Autodesk notes that some data will not be preserved in an export-to-IGES-and-back workflow, which is why IGES is useful for exchange but not equivalent to retaining a native CAD model with all original semantics intact.

Applications and Industry Use Cases

IGES-to-CAD conversion is common in multi-CAD engineering environments where a supplier, customer, or partner delivers an IGES file and the receiving team needs to use that model in its own CAD or downstream engineering system. Typical use cases include design reuse, model review, CAM preparation, CAE preprocessing, and migration from older neutral exchanges into more usable CAD-native workflows.

For software developers, this conversion matters when building import pipelines, translation services, viewers that must support exact geometry, or engineering platforms that need to turn exchanged data into editable or queryable model data.

Challenges or Common Pitfalls

A common mistake is to assume that IGES-to-CAD conversion is a simple one-to-one transfer. In reality, the source is a neutral exchange format and the target is often a different modeling kernel or data model, so differences in geometry interpretation, topology rules, and supported entities can all affect the result.

Another pitfall is expecting perfect round-trip fidelity. Autodesk explicitly warns that some data will not be preserved in a round trip to IGES and back, so teams should not assume the converted CAD result is identical to a native source model in every respect.

Model validity is also a recurring issue. The documentation highlights automated healing, stitching, and resurfacing because downstream workflows often fail on imported models with topological or geometric defects. That problem becomes especially visible when converted geometry must support Booleans, meshing, feature recognition, or other operations beyond simple viewing.

Finally, unit and tolerance mismatches can create subtle failures even when a file imports successfully. Spatial's CAD interoperability guide gives the concrete example of inch-authored data being read as millimeters, producing geometry that is formally valid but dimensionally wrong by a factor of 25.4.

How Spatial helps

Our 3D InterOp SDK reads IGES files and converts them into native geometry for ACIS, CGM, and Parasolid kernels. The converted data works as if it was created natively in the target application, so downstream operations like Booleans, queries, and meshing succeed on the imported model.

This matters for IGES specifically because of how the format stores geometry. IGES often converts simple analytic shapes — planes, cylinders, cones — into spline-based approximations. A cylinder that should be two planar faces and one cylindrical surface may arrive as three spline surfaces. 3D InterOp's geometry simplification step detects these cases and restores the analytic forms, which preserves the original design intent while reducing data weight and improving robustness for downstream operations.

Beyond simplification, 3D InterOp applies automatic healing during translation in three areas:

• Topology repair: removing duplicate and overlapping vertices, splitting edges with large discontinuities so they conform to the target kernel's continuity rules.
• Geometry refinement: reconstructing self-intersecting or irregular curves and surfaces, and trimming underlying surfaces to match the target kernel's requirements. This step does not alter the intended shape — it corrects issues introduced by differences between source and target representations.
• Fixing other invalid data such as loop errors.

For models that need further cleanup after translation, additional healing is available through the ACIS Healing APIs. That includes stitching (unifying coincident edges and vertices to restore topological completeness), gap tightening (recomputing intersections so adjacent faces meet within desired tolerances), and cleanup operations like removing small edges, eliminating sliver faces, and merging coplanar faces. These are especially useful when the imported geometry must feed into simulation or meshing workflows.

3D InterOp also extracts metadata beyond geometry: Product Manufacturing Information (PMI) in graphical and semantic form, color, layer, names, and other attributes. Its selective import API lets applications load only the data containers they need — product structure, tessellated geometry, exact geometry, or manufacturing information — rather than reading the entire file. For large-scale or automated pipelines, 3D InterOp supports concurrent import using multiple threads or processes.

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

You can request an evaluation here.