Exporting to Alternate Formats — Export objects to alternate formats (STEP/IGES/ACIS) (intro, as available) - AutoCAD

SECTION 1

Historical Context & Motivation

The history of computer-aided design is, in many respects, a history of incompatible file formats. As CAD software proliferated during the 1970s and 1980s, engineering firms found themselves locked into proprietary ecosystems — a drawing created in one system could not be opened, edited, or even visualized in another without significant manual rework. This interoperability crisis motivated the development of neutral exchange formats, standardized data representations that could serve as a lingua franca between disparate CAD platforms. Understanding why these formats exist is essential for any engineer or computer scientist who works with geometric data across toolchains, simulation environments, or manufacturing pipelines.

1980 • IGES 1.0 Released

The Initial Graphics Exchange Specification (IGES) became the first ANSI-standard neutral file format, enabling 2D/3D wireframe and surface exchange between early CAD systems like CADAM and Unigraphics.

1989 • ACIS Kernel Introduced

Spatial Technology released the ACIS solid modeling kernel, providing a boundary-representation (B-rep) engine that AutoCAD would later adopt for its 3D solid geometry, with .sat/.sab as its native exchange format.

1994 • STEP ISO 10303 Published

The Standard for the Exchange of Product Model Data (STEP) was formalized as ISO 10303, offering a richer, schema-driven approach to encoding not just geometry but product manufacturing information (PMI), tolerances, and assembly structure.

2002 • AutoCAD Adds STEP/IGES Import/Export

Autodesk extended AutoCAD's interoperability capabilities to include STEP and IGES translators, enabling direct exchange with platforms like CATIA, SolidWorks, and Pro/ENGINEER without third-party conversion tools.

2020s • Cloud-Based & Multi-Format Workflows

Modern PLM and cloud-based CAD platforms rely heavily on STEP AP 242 for model-based definition (MBD) workflows, making neutral format fluency an increasingly critical skill in digital engineering.

The fundamental question these formats address is straightforward yet technically deep: how do you represent three-dimensional geometric and topological information in a way that is application-independent, mathematically precise, and lossless across translation boundaries? Each of the three formats — STEP, IGES, and ACIS — offers a different answer to this question, with trade-offs in expressiveness, fidelity, and adoption.

SECTION 2

Core Principles & Definitions

Before diving into AutoCAD's export commands, it is important to establish the foundational concepts that underpin all neutral format translation. Every CAD model is, at its core, a structured representation of geometry (shape), topology (connectivity), and metadata (attributes, layers, colors). The challenge of exporting lies in faithfully mapping AutoCAD's internal data structures — which use the ACIS kernel for 3D solids — into the target format's own representation schema. This mapping is governed by several key principles.

Boundary Representation (B-rep)

All three formats encode solid geometry using B-rep — a model is defined by its bounding faces, edges, and vertices, plus the underlying surface and curve equations (NURBS, analytic). AutoCAD's ACIS kernel natively stores solids in B-rep form, making export conceptually a translation rather than a conversion.

Schema & Application Protocol

STEP uses formal EXPRESS schemas and Application Protocols (APs) — e.g., AP 203 for configuration-controlled design, AP 214 for automotive — that define exactly which entities and relationships are valid. IGES uses entity-type codes. ACIS uses its own proprietary text/binary schema.

Geometric Fidelity vs. Metadata Loss

Neutral formats preserve geometric fidelity (surface equations, tolerances) well, but AutoCAD-specific features — dynamic blocks, parametric constraints, annotation scales — have no equivalent in STEP/IGES and are typically lost or flattened during export.

Tolerance & Precision

Every B-rep model carries a tolerance value defining how closely edges must meet surface boundaries. Mismatched tolerances between the source model and target system can produce gaps, overlaps, or degenerate faces — a common source of import failures.

ASCII vs. Binary Encoding

STEP (.stp) and IGES (.igs) are typically ASCII-encoded, making them human-readable and diff-able (useful for version control). ACIS supports both ASCII (.sat) and binary (.sab) formats, with binary offering faster I/O and smaller file sizes at the cost of readability.

✦

KEY TAKEAWAY

Think of exporting to a neutral format like translating a novel from one language to another. The plot (geometry) and character relationships (topology) transfer well, but language-specific wordplay and cultural idioms (AutoCAD-specific features) may not survive the translation. A good translator — in this case, a well-configured export pipeline — minimizes such losses while preserving the essential meaning of the original work.

SECTION 3

Visual Explanation — The Export Pipeline

The export pipeline from AutoCAD DWG to neutral formats. The Translation Engine maps B-rep geometry and NURBS data to the target schema, while AutoCAD-specific constructs like dynamic blocks and parametric constraints are typically lost. Green circles indicate preserved data, red indicates lost data, and yellow indicates conditional transfer depending on the target format and Application Protocol.

The diagram above illustrates the conceptual pipeline that AutoCAD executes when you invoke an export command. The source DWG file contains a rich mix of geometry, annotation, and parametric data stored internally via the ACIS kernel (for 3D solids) and AutoCAD's native entity structures (for 2D and annotation objects). The translation engine performs several operations in sequence: it traverses the model's B-rep topology, converts any procedural or CSG-based geometry into evaluated B-rep form, maps surface equations to the target format's NURBS representation, checks edge-face tolerances, and writes the result in the appropriate ASCII or binary encoding. The degree of data preservation depends heavily on the chosen format — STEP AP 242, for instance, can carry tolerances and assembly relationships that IGES cannot.

SECTION 4

How It Works — Format Internals

STEP File Structure

A STEP file (typically with a .stp or .step extension) is structured as a sequence of numbered entity instances written in the STEP Physical File (SPF) format, which is defined by ISO 10303-21. The file begins with a HEADER section containing metadata (file name, originating system, schema identifier), followed by a DATA section where each entity is assigned a unique integer ID prefixed by #. Entities reference each other by ID, forming a directed acyclic graph (DAG) of geometric and topological relationships. For example, a CLOSED_SHELL entity references a list of ADVANCED_FACE entities, each of which references an FACE_OUTER_BOUND and a surface definition (e.g., B_SPLINE_SURFACE_WITH_KNOTS).

ℹ

STEP Entity Example

A minimal STEP excerpt for a planar face might look like: #10 = CARTESIAN_POINT('', (0.0, 0.0, 0.0)); #11 = DIRECTION('', (0.0, 0.0, 1.0)); #12 = AXIS2_PLACEMENT_3D('', #10, #11, #13); #14 = PLANE('', #12); Each entity is a typed record with positional arguments — a structure familiar to anyone who has parsed S-expressions or protocol buffers.

IGES File Structure

An IGES file is organized into five fixed-width sections: Start (S), Global (G), Directory Entry (D), Parameter Data (P), and Terminate (T). Each line is exactly 80 characters wide (a legacy of punch-card formatting), and entities are identified by integer type codes — for instance, type 128 is a Rational B-Spline Surface, and type 126 is a Rational B-Spline Curve. The Directory Entry section contains two lines per entity specifying its type, color, line weight, and pointer to the Parameter Data section. This rigid columnar format makes IGES files straightforward to parse programmatically, though the fixed-width constraint can lead to truncated precision for high-accuracy models.

ACIS SAT File Structure

The ACIS .sat (Save As Text) format is more compact than STEP or IGES because it directly serializes the ACIS kernel's internal B-rep data structures. A SAT file begins with a header specifying the ACIS version number and units, followed by entity records that mirror the kernel's topological hierarchy: body → lump → shell → face → loop → coedge → edge → vertex. Because AutoCAD's 3D solids are natively stored in ACIS form, exporting to SAT is essentially a serialization operation with near-zero translation loss. This makes ACIS the format of choice when the receiving application also uses the ACIS kernel (e.g., certain versions of SpaceClaim, BricsCAD, or Fusion 360 for legacy import).

SECTION 5

Detailed Format Comparison

Feature support matrix comparing STEP, IGES, and ACIS across eight key capability dimensions. STEP provides the most comprehensive coverage, particularly for assembly structure and PMI data. IGES excels at 2D drawing views due to its historical roots, while ACIS provides the highest-fidelity solid geometry transfer for applications sharing the same kernel.

The matrix above reveals a clear strategic positioning for each format. STEP is the most feature-complete and is the de facto standard for modern manufacturing interoperability — if you are unsure which format to use, STEP AP 214 or AP 242 is almost always the safest choice. IGES remains relevant in legacy environments and for exchanging 2D drawing data or trimmed NURBS surfaces, particularly with older CNC toolpath generators. ACIS is the optimal choice when both the source and target application share the ACIS kernel, as the translation is essentially a lossless serialization/deserialization cycle. From a computer science perspective, you can think of STEP as a richly-typed serialization format (analogous to Protocol Buffers with a formal schema), IGES as a flat, record-oriented format (analogous to fixed-width CSV), and ACIS as a native object serialization (analogous to Java's Serializable interface).

SECTION 6

Worked Example — Exporting a 3D Solid to STEP

Let us walk through the complete process of exporting a 3D solid model from AutoCAD to STEP format, which is the most commonly requested export scenario in professional practice. We will also cover ACIS and IGES export variations in the notes.

Export a Mechanical Part as STEP AP 214

1
Step 1 — Verify Model Geometry

Before exporting, ensure your model contains valid 3D solids or surfaces. At the AutoCAD command line, type MASSPROP and select your solid to verify it is a closed, valid B-rep body. If MASSPROP returns mass properties, the solid is well-formed. For surface models, use SURFSCULPT to attempt conversion to a solid if possible, or verify surface continuity.

Solid is valid — volume, centroid, and moments of inertia are reported.
2
Step 2 — Isolate Export Geometry

Turn off or freeze layers containing 2D annotations, dimensions, hatches, and construction geometry that should not appear in the export. Alternatively, copy the 3D solids to a clean drawing. Remember that only 3D solids, 3D surfaces, and regions will translate meaningfully to STEP; lines, arcs, and 2D polylines in model space become wireframe entities (STEP type GEOMETRIC_CURVE_SET).

Only relevant 3D geometry is visible; annotation layers are frozen.
3
Step 3 — Invoke the STEPOUT Command

At the command line, type STEPOUT (or navigate to the Application Menu → Export → Other Formats and select STEP from the file type dropdown). AutoCAD will prompt you to select objects. Select the solids and surfaces to export, then press Enter. A file dialog will appear — choose a filename and location. Note that the system variable FACETRES does NOT affect STEP output (it only controls mesh/tessellation), because STEP exports exact B-rep data, not tessellated approximations.

File saved as part_assembly.stp — exported 3 solid bodies.
4
Step 4 — Validate the Output

Open the exported .stp file in a text editor to inspect the header. Verify the schema identifier (e.g., FILE_SCHEMA(('AUTOMOTIVE_DESIGN')) for AP 214). For a more thorough check, import the file into the target application (SolidWorks, CATIA, FreeCAD) and compare the face/edge count. Alternatively, use a free STEP viewer like CAD Exchanger or the open-source stepcode library to parse and validate the file against the EXPRESS schema.

Schema is AP 214; entity count matches expected topology — 24 faces, 54 edges, 32 vertices.
5
Step 5 — ACIS and IGES Variants

For ACIS export, use the ACISOUT command — this writes a .sat file directly from the kernel with no translation layer. For IGES export, use IGESOUT — note that AutoCAD's IGES exporter may convert solids to trimmed NURBS surface sets (losing the solid topological structure), so verify the result in the target application. The system variable IGESOUTVER (if available in your version) controls the IGES specification version.

ACIS: part_assembly.sat written. IGES: part_assembly.igs written with 24 trimmed surface entities (IGES type 144).

💡

Pro Tip

If you need to script batch exports (e.g., exporting 50 parts overnight), you can use AutoLISP or the .NET API. In AutoLISP, (command "STEPOUT" selection_set "" filename) can be wrapped in a loop. For the .NET API, the Autodesk.AutoCAD.DatabaseServices.Database.SaveAs() method combined with format-specific translators provides programmatic control over export parameters.

SECTION 7

Strengths, Limitations, and Trade-offs

Criterion	STEP	IGES	ACIS
Geometric Fidelity	Excellent — exact B-rep with NURBS, analytics, and tolerances preserved	Good — NURBS surfaces preserved, but solids may decompose into surface sets	Excellent — native kernel serialization, near-lossless for AutoCAD solids
Interoperability	Broadest — supported by virtually all modern CAD/CAM/CAE systems	Wide — legacy standard still supported, but declining in new implementations	Narrow — only useful when target system uses the ACIS kernel
File Size	Moderate — ASCII SPF is verbose; compressed STEP (ISO 10303-28 XML) is smaller	Large — 80-char line format with redundant whitespace	Small — compact serialization; binary .sab even smaller
Metadata Richness	Highest — PMI, tolerances, assembly trees, material properties via AP 242	Low — limited to colors, layers, and line weights	Moderate — supports attributes but no formal PMI schema
Active Development	Yes — AP 242 Ed. 2+ adds 3D tessellated geometry, composite materials	No — last major revision was IGES 5.3 in 1996; effectively frozen	Yes — Spatial Corp continues kernel updates, but format is proprietary

Comparative analysis of STEP, IGES, and ACIS export formats across five key criteria.

✦

KEY TAKEAWAY

Choosing an export format is analogous to choosing a network protocol in software engineering. STEP is like HTTP/2 — versatile, well-standardized, and the default choice for most scenarios. IGES is like FTP — still functional for specific use cases but largely superseded. ACIS is like shared memory IPC — extremely efficient but only works when both processes share the same runtime. When in doubt, export to STEP; it maximizes the probability that your geometry will import correctly into any downstream system.

SECTION 8

Connection to Advanced Workflows

The introductory export workflow covered in this lesson is the foundation for several advanced interoperability techniques that arise in professional engineering and computational geometry research. Understanding where this foundational skill leads will help you appreciate its significance in broader CAD/CAM/CAE pipelines.

Introductory Concept	Advanced Extension
Manual single-file export via STEPOUT	Automated batch export pipelines using AutoLISP, .NET API, or Python (pyautocad) for CI/CD integration in digital engineering
Exporting individual solids	STEP AP 242 model-based definition (MBD) with embedded GD&T, assembly constraints, and validation properties — replacing 2D drawings entirely
Visual file validation in target app	Programmatic STEP validation using open-source tools like STEPcode, Open CASCADE's XDE, or NIST's STEP File Analyzer for conformance testing against AP schemas
Choosing between STEP/IGES/ACIS	Format-agnostic geometry kernels (e.g., Open CASCADE, Parasolid) that can ingest multiple neutral formats and provide a unified API for geometric queries, Boolean operations, and mesh generation
Exporting static geometry snapshots	Round-trip engineering with parametric re-mastering: importing STEP into Fusion 360 or FreeCAD, recognizing features, modifying parameters, and re-exporting — enabling iterative design across heterogeneous toolchains

From introductory export skills to advanced interoperability workflows.

For computer science students, the most immediately relevant advanced topic is programmatic STEP file parsing and generation. The EXPRESS data modeling language used by STEP is itself an interesting formal system — it supports inheritance, constraints, and aggregate types, making it structurally similar to an object-oriented schema definition language. Libraries like stepcode (C++), PythonOCC (Python bindings for Open CASCADE), and jsdoc-stepfile (JavaScript) allow you to read, write, and manipulate STEP files programmatically — opening the door to custom translators, geometric analysis pipelines, and integration with simulation frameworks.

SECTION 9

Practice Problems

Question 1: CONCEPTUAL

Explain why exporting a 3D solid from AutoCAD to IGES might result in the loss of the solid's topological structure, even though the geometry (surface shapes) is preserved. What is the fundamental difference between a solid B-rep and a collection of trimmed surfaces?

Show answer

A solid B-rep encodes not just the surface geometry but also the topological relationships between faces — specifically, which faces are adjacent, how edges connect faces, and the orientation (normal direction) that defines inside versus outside. IGES was designed primarily for surface and wireframe exchange and does not have a robust entity type for closed solid topology. When AutoCAD exports a solid to IGES, it decomposes the solid into a set of individually trimmed NURBS surfaces (entity type 144). These surfaces may look identical to the original solid when rendered, but they lack the topological 'glue' (shell/lump/body hierarchy) that tells the receiving system the surfaces form a watertight volume. This means the importing application cannot compute mass properties, perform Boolean operations, or verify the model is manifold without first attempting to 'knit' the surfaces back into a solid — a process that can fail if tolerances do not match.

Question 2: BASIC CALCULATION

A STEP file exported from AutoCAD contains 48 ADVANCED_FACE entities, 96 EDGE_CURVE entities, and 50 VERTEX_POINT entities. Using Euler's formula for closed polyhedral surfaces (V − E + F = 2 for a single genus-0 solid), verify whether this entity count is consistent with a single, simple (no holes or handles) closed solid body.

Show answer

Euler's formula for a closed, orientable, genus-0 polyhedron states V − E + F = 2, where V is the number of vertices, E is the number of edges, and F is the number of faces. Substituting the given values: 50 − 96 + 48 = 2. Since the result equals 2, the entity count is consistent with a single simple closed solid body of genus 0 (no through-holes or handles). In practice, STEP B-rep models use edge curves rather than simple polygon edges, so this Euler check is a necessary but not sufficient condition — it verifies topological consistency at the combinatorial level but does not guarantee geometric validity (e.g., self-intersecting surfaces). If the solid had one through-hole (genus 1), the expected Euler characteristic would be 0, so the fact that we get 2 confirms the absence of topological handles.

Question 3: INTERMEDIATE

You have a drawing containing 3D solids on the 'MECHANICAL' layer, 3D surfaces on the 'FREEFORM' layer, 2D dimensions on the 'ANNOTATIONS' layer, and construction lines on the 'CONSTRUCTION' layer. You need to export only the solids and surfaces to STEP for import into SolidWorks. Describe the complete procedure, including layer management, object selection, command invocation, and post-export validation steps.

Show answer

First, freeze or turn off the ANNOTATIONS and CONSTRUCTION layers to exclude non-geometric entities from the selection set — while STEPOUT allows object selection, ensuring only relevant layers are visible reduces the risk of accidentally including unwanted geometry. Second, invoke the STEPOUT command at the command line. When prompted to select objects, use a crossing window to select all visible geometry, or use a filtered selection with QSELECT to select only 3DSOLID and SURFACE entity types on the MECHANICAL and FREEFORM layers. Press Enter to confirm the selection. In the Save As dialog, choose a filename and ensure the file type is set to STEP (*.stp). After export, open the .stp file in a text editor and verify the HEADER section shows the correct schema (likely AUTOMOTIVE_DESIGN for AP 214). Then import the file into SolidWorks using File → Open → Files of Type: STEP. In SolidWorks' import diagnostics, check the face count and run Import Diagnostics to identify any gaps or faulty faces. Compare the mass properties between AutoCAD's MASSPROP output and SolidWorks' mass properties to verify volumetric fidelity — differences greater than 0.1% typically indicate translation errors.

Question 4: APPLIED

A manufacturing partner requires geometry in IGES format for their legacy CNC programming system, but they report that your exported IGES file produces 'open surface' warnings during import. You suspect the issue is related to edge tolerance mismatch. Describe a systematic debugging approach, including specific AutoCAD commands and IGES entity types to inspect.

Show answer

The 'open surface' warning almost certainly means that adjacent trimmed surfaces in the IGES file do not share edges within the receiving system's tolerance — a common issue when AutoCAD's modeling tolerance (typically 1 × 10⁻¹⁰ units) is much tighter than the CNC system's import tolerance. Begin debugging by inspecting the original model in AutoCAD: use the CHECKSOLIDS command (or AUDIT) to identify any pre-existing geometric issues like self-intersections, zero-area faces, or degenerate edges. Run MASSPROP to confirm the solid is closed. Next, open the exported .igs file in a text editor and locate the Global section (G), which contains the model-space minimum resolution (parameter 16). Compare this value to the CNC system's tolerance specification. If there is a large mismatch, re-export from AutoCAD after adjusting the solid's tolerance using the SURFTAB1/SURFTAB2 variables or by restructuring the geometry with larger blend radii. You can also try exporting via STEP instead, since STEP's B-rep structure explicitly encodes edge-face associations with tolerance metadata, which many systems handle more robustly than IGES's disconnected surface representation. If IGES is strictly required, consider using a third-party translator like CAD Exchanger that offers tolerance-healing during the export process.

Question 5: CRITICAL THINKING

STEP's EXPRESS schema language and its Physical File format (ISO 10303-21) can be viewed as a domain-specific data serialization framework. Compare and contrast the STEP/EXPRESS ecosystem with a modern general-purpose serialization stack (e.g., Protocol Buffers + gRPC, or JSON Schema + REST). What are the trade-offs in expressiveness, extensibility, tooling maturity, and adoption? Under what circumstances might a software engineer prefer to define a custom serialization format over using STEP for geometric data exchange?

Show answer

STEP's EXPRESS language is a strongly typed, formally specified schema language that supports inheritance, constraints (WHERE rules), and complex aggregate types (SET, LIST, BAG, ARRAY) — making it significantly more expressive than Protocol Buffers' schema language (which lacks constraints and inheritance beyond oneof). However, this expressiveness comes at the cost of tooling maturity and ecosystem breadth: Protocol Buffers has first-class support in dozens of languages with high-performance code generators, whereas EXPRESS parsers are niche tools maintained by small communities. JSON Schema occupies a middle ground with broad adoption but limited type-system power. STEP's Physical File format (SPF) is ASCII-based and human-readable like JSON, but its entity-reference model (using #ID pointers) is more akin to a relational database than a hierarchical document — making it natural for expressing graphs of topological relationships but harder to work with using standard JSON/XML tools. A software engineer might prefer a custom format when the geometric data is highly specific (e.g., only triangular meshes for game assets, where STL or glTF suffices), when real-time streaming is required (STEP's file-based design does not support incremental parsing well), or when the team's expertise is in web technologies and the overhead of learning EXPRESS/STEP tooling outweighs the interoperability benefits. In regulated industries (aerospace, automotive), however, STEP's ISO standardization and long-term archival guarantees (AP 203 is specifically designed for 'configuration controlled 3D design') make it irreplaceable.

SUMMARY

Lesson Summary

Summary

This lesson introduced the three primary neutral exchange formats available for exporting 3D geometry from AutoCAD: STEP (ISO 10303), IGES (ANSI Y14.26M), and ACIS (.sat/.sab). All three formats encode geometry using boundary representation (B-rep) — faces bounded by edges and vertices, with underlying surface equations defined by NURBS or analytic forms. The export process involves mapping AutoCAD's internal ACIS kernel data structures into the target format's schema, preserving geometric fidelity while inevitably losing AutoCAD-specific features like dynamic blocks and parametric constraints.

For most interoperability scenarios, STEP is the recommended format due to its ISO standardization, broad adoption, and rich metadata support (especially AP 214 and AP 242 for assembly structures and PMI). The key AutoCAD commands are STEPOUT, IGESOUT, and ACISOUT. Always validate exported files by inspecting the header, checking entity counts against Euler's formula (V − E + F = 2) for topological consistency, and importing into the target application to verify mass properties. From a computer science perspective, these formats represent fascinating case studies in domain-specific data serialization, with STEP's EXPRESS schema language offering a formally specified type system that predates and in some ways exceeds the expressiveness of modern alternatives like Protocol Buffers or JSON Schema.