Convert IAM to 3DXML in your application
3D InterOp is a CAD interoperability SDK that lets your software read IAM files and write 3DXML, generating the 3DXML mesh from the geometry it reads, with tessellation settings your application controls.
Spatial does not offer an online converter or a desktop conversion app. 3D InterOp is a component that software vendors embed in their own products.
- Reads Inventor assembly · Writes 3D XML
- Exact geometry → triangle mesh
- C++ / C# APIs
IAM to 3DXML at a glance
Inventor assembly stores exact geometry; 3D XML stores triangles. The translation is a tessellation, and the settings you choose decide how close the mesh stays to the original.
| Inventor assembly (source) | 3D XML (target) | |
|---|---|---|
| Full name | Autodesk Inventor Assembly | 3D XML |
| Standard / owner | Autodesk | Dassault Systèmes |
| File extensions | .iam | .3dxml |
| Geometry | Exact B-Rep (in the referenced parts) | Tessellated geometry |
| Assemblies / structure | Yes | Yes |
| PMI | Not imported by 3D InterOp | Graphical PMI |
| 3D InterOp support | Read only | Read and write |
What's preserved, what changes
Here is what your application can expect to carry across from Inventor assembly to 3D XML.
-
Preserved
Product structureThe IAM product structure is written to 3DXML.
-
Changes
Geometry is tessellatedThe exact Inventor assembly B-Rep is replaced by a triangle mesh, generated by 3D InterOp from the exact geometry it reads. Accuracy depends on the tessellation settings your application uses.
Why software vendors add IAM to 3DXML conversion
Lightweight review
3D XML carries tessellated geometry that opens much faster than the full CAD model, so design reviews and digital mockups stay responsive.
Sharing outside engineering
Marketing, training and sales teams rarely have CAD software. A 3D XML file gives them the shape in a format their tools can open.
Easier handling of large assemblies
Without exact surfaces and feature data, 3D XML files are easier to transfer and display, even for large assemblies.
Things to check before you ship
- Written 3DXML versions: 3D XML 4.3, as static tessellation.
- Only static tessellation is written, not XML tessellation.
- Supported IAM input: Inventor V11 to 2027.
- Test tessellation settings on your heaviest parts: finer meshes mean larger files.
- Validate a sample of translated files in the target system your users actually work with.
Working with Spatial was a real milestone for us: Thanks to the powerful 3DInterOp library, we were able to successfully bring our complex CAD-based solutions to the cloud while remaining flexible to meet individual customer requirements. For us, Spatial is not just a technology partner, but a true enabler of our product strategy.
Dr. Arno Michelis, Founder, Simus Systems
Read the Case StudyAbout the formats
-
Source format
What is an IAM (.iam) file?
An IAM file is an Autodesk Inventor assembly. It stores the product structure and constraints, and references the IPT part files.
-
Target format
What is a 3D XML (.3dxml) file?
3D XML is Dassault Systèmes’ lightweight XML-based format for sharing 3D product data. 3D InterOp reads and writes its tessellated representation, with product structure and graphical PMI.
Frequently asked questions
3D InterOp tessellates the geometry it reads from IAM when it writes 3DXML. Your application sets the tolerances, so it controls the trade-off between accuracy and file size.
Yes. 3D InterOp reads the IAM product structure and writes it to 3DXML.
3D InterOp writes 3D XML 4.3 with static tessellation. XML tessellation isn’t written.
3D InterOp reads Inventor V11 to 2027.
3D InterOp writes 3D XML 4.3, as static tessellation.
No. 3D InterOp reads IAM but doesn’t write it. To send data back to Inventor users, write a neutral format they can import, such as STEP.
-
Building software that needs to convert IAM to 3DXML?
3D InterOp is an SDK that lets your application read Inventor assembly and write 3D XML alongside 30+ CAD and BIM formats.