What is an IAM file?
IAM stands for Inventor Assembly. An .iam file records the components of a product, the assembly relationships that tie them together, and the position of each instance. It also stores properties such as color, suppression and visibility for each component, as well as the iProperties and Model States defined at assembly level.
Because the geometry lives in the referenced part files, an IAM file on its own is only a structure. To open the complete product, every referenced .ipt and sub-assembly .iam file must be available, typically in the project folder structure used by Inventor.
How is an Inventor assembly organized?
| Element | Description |
| Assembly (.iam) | Top-level file that holds the product structure and component placements |
| Sub-assemblies (.iam) | Nested assemblies referenced from a parent assembly |
| Parts (.ipt) | Component files that contain the exact geometry, including sheet metal bodies |
| Instance properties | Color, transparency, suppression and names for each placed component |
| Assembly metadata | iProperties from the Custom, Project and Status tabs, and Model States |
What Is IAM Used For? Applications and Industry Use Cases
IAM files hold complete products designed in Autodesk Inventor, from machines and industrial equipment to tooling and consumer goods. They are shared with suppliers, manufacturing partners and analysis teams who need the whole product, not only individual parts.
For software developers, reading IAM files lets modeling, simulation, manufacturing and visualization applications bring a full Inventor assembly in as one structured model. Stable persistent names on instances make it easier to keep simulation setups or other application data linked to the right components when the design changes.
Challenges or Common Pitfalls
Missing references are the most common issue. If some .ipt or sub-assembly files are not delivered with the IAM file, or are stored in unexpected folders, the translated assembly is incomplete.
Inventor assemblies can also rely on behavior that only Inventor fully resolves. Flexible assemblies, positions driven by constraints, component patterns and content from environments such as Tube & Piping, Cable & Harness or Weldments may not translate as expected, and some Model States must be re-saved in Inventor before they can be read.
Finally, persistent identifiers are not guaranteed to stay the same when an assembly is edited in a different Inventor version, so workflows that depend on them should be tested with the versions customers use.
How Spatial Helps
Our 3D InterOp SDK reads Autodesk Inventor assemblies from Inventor 11 onward, up to recent releases such as Inventor 2026, and translates them into CGM Modeler, 3D ACIS Modeler or Parasolid. It extracts the full assembly tree, with instances in the same order as in Inventor, and reads the exact B-rep geometry of the referenced parts, including sheet metal bodies and 2D sketches.
3D InterOp also imports instance color, transparency, suppression and persistent names, which stay stable when components are added, removed, moved, renamed or re-transformed. Part- and assembly-level iProperties and Model States are available as well.
Inventor files are imported only; writing them is not supported. Inventor assemblies are also supported by the Hidden Body Removal capability of our Data Prep technology.