What does IGES stand for?
IGES stands for Initial Graphics Exchange Specification. It was created to address the CAD/CAM data-exchange problem and was formalized in an early specification published by the U.S. National Bureau of Standards in 1980. That work was coordinated under contract to the Air Force, Army, Navy, and NASA, with Boeing and General Electric playing major roles in the technical effort.
What kind of data does an IGES file contain?
An IGES file can carry more than simple line geometry. The original specification describes it as an exchange format for geometry, drafting, and structural information, and Autodesk's documentation notes that IGES is commonly used to exchange surface-oriented CAD data. In practice IGES is most often associated with curves and surfaces, but the broader specification also covers other engineering data classes.
How is an IGES file structured?
IGES uses a text-based structure inherited from older computing environments. The original specification defines the exchange file as ASCII characters on 80-column card images. Autodesk summarizes the format as having five sections:
| Section |
Code |
Role |
| Start |
S |
Human-readable prologue describing the file |
| Global |
G |
File-wide parameters such as units and author |
| Directory |
D |
Index of every entity in the file |
| Parameter Data |
P |
The actual entity data (geometry, drafting, structure) |
| Termination |
T |
End-of-file record with section counts |
This structure is one reason IGES files are human-readable in a text editor, even though they are not convenient to edit manually.
How is IGES different from newer exchange formats?
IGES was developed primarily for exchanging geometric CAD data. Later neutral standards, especially STEP, were designed to represent a broader range of product information across a product's lifecycle.
| |
IGES |
STEP |
| Primary scope |
Geometry, drafting, and structural data |
Full product data across the lifecycle |
| Typical use today |
Legacy and compatibility workflows |
Preferred for richer product-data exchange |
That is why IGES is still encountered in legacy and compatibility workflows, but many modern engineering pipelines prefer STEP when richer product-data exchange is required.
Applications and Industry Use Cases
IGES has been used across CAD/CAM workflows to transfer models between systems from different vendors. It is especially associated with legacy interoperability in industries such as aerospace, automotive, and machinery, where engineering organizations have long needed neutral exchange formats to move design data between suppliers, customers, and manufacturing systems.
For software developers, IGES remains relevant when supporting older customer data, supplier archives, surface-based geometry exchange, or import pipelines that must accept a wide range of neutral CAD files. Even when newer formats are preferred for new projects, IGES support is often still needed for backward compatibility.
Challenges or Common Pitfalls
A common mistake is to assume that IGES behaves like a native CAD format. It does not. IGES is an exchange format, so downstream quality depends on how well the receiving system interprets the source entities and reconstructs usable geometry. This can lead to incomplete translation, missing semantics, or geometry that needs cleanup before modeling or manufacturing use.
Another pitfall is to assume that all IGES files contain the same kind of data. Some are primarily surface-based, some include drafting-oriented content, and some reflect older conventions that modern applications handle only partially. Because IGES is mature and text-based it remains accessible, but that does not guarantee robust interoperability in every workflow.
How Spatial Helps
Spatial handles IGES through its CAD interoperability technology, so applications can turn imported neutral data into geometry they can actually work with.
3D InterOp reads and writes major CAD formats, including IGES, and exchanges exact B-rep geometry, tessellated data, and metadata across them. Because IGES files often arrive with gaps or surface defects, 3D InterOp also repairs and heals imported geometry so it can be queried, edited, and exported again.
That matters when IGES handling is not just about opening a file, but about reusing legacy or supplier data in a downstream engineering pipeline. 3D InterOp takes the imported surfaces and produces geometry that holds up through modeling, analysis, and manufacturing steps.