How to convert IGES to 3MF
- Load the IGES fileThe reader collects surface entities from the D/P sections; annotation and structure entities are skipped.
- Tessellate and mergeEvery usable surface is triangulated at the chosen detail level and joined into one mesh.
- Write the 3MF packageThe writer builds the 3MF zip: [Content_Types].xml, a relationships file and the model XML holding the mesh with its unit declaration.
What happens when IGES is converted to 3MF
What a CAD file really stores
STEP and IGES are boundary representations: exact surfaces (planes, cylinders, splines) with trimming curves that delimit each face. There are no triangles anywhere in the file — any triangle you see was computed on the fly.
Tessellation is the whole conversion
The kernel converts each exact face into triangles by recursive subdivision until the chordal error stays under the detail level's deflection. A cylinder tessellated at Draft may be 32 segments; at Maximum it can exceed 512. The triangle count scales with surface curvature, not file size.
Only position and normal survive
The mesh handed to exporters carries vertex positions and normals. Nothing else in the source has a destination in a plain mesh format: feature history, assembly structure, materials, names and PMI annotations are dropped.
The unit survives — that is the point
STL and OBJ store bare numbers; 3MF's model XML declares unit="millimeter". For IGES data destined for a slicer this removes the classic gotcha where a part arrives ten times too large because someone assumed inches.
One part, one object
The merged mesh is written as a single 3MF object. 3MF supports multi-object builds with transforms, but a flattened legacy conversion produces exactly one item — consistent with how the source geometry arrives.
IGES vs 3MF
| IGES surfaces | 3MF package | |
|---|---|---|
| Feature | IGES source | 3MF output |
| Geometry | Exact surfaces as entities | Indexed triangle mesh |
| Container | 1980s text sections | Zip: XML model + relationship parts |
| Units | Loosely declared, often inches | Declared in the model XML — millimetres |
| Consumer | Legacy CAD tools | Slicers (Cura, PrusaSlicer), Windows 3D Builder |
| Structure | Entity list | One object in a build item |
Supported formats
| Format | Read | Write | Notes |
|---|---|---|---|
| STEP (.step .stp) | Yes | – | ISO 10303 B-rep, AP203 / AP214 / AP242 |
| IGES (.iges .igs) | Yes | – | Entity-based surfaces, up to 5.3 |
| BREP (.brep) | Yes | – | OpenCascade native B-rep |
| STL (.stl) | Yes | Yes | Binary and ASCII triangles, no units |
| OBJ (.obj) | Yes | Yes | v / vn / f records; .mtl references ignored |
| PLY (.ply) | Yes | Yes | Binary position and normal arrays |
| GLB / glTF (.glb .gltf) | Yes | Yes | glTF 2.0, binary or JSON with data URI |
| 3MF (.3mf) | Yes | Yes | OPC/ZIP package, declares millimetres |
| FBX (.fbx) | Yes | – | Binary and ASCII, static mesh only |
| DAE (.dae) | Yes | Yes | Collada scene graph is flattened |
| 3DS (.3ds) | Yes | – | Legacy chunk-based 3D Studio format |
| AMF (.amf) | Yes | – | XML, ZIP-compressed packages supported |
| USDZ (.usdz) | Yes | Yes | ZIP containing a USD stage |
Known limitations and why a conversion can fail
This is a one-way flattening
The IGES feature tree, sketches and constraints cannot be recovered from the mesh output. Keep the source file — the conversion cannot be reversed.
Hollow results mean open edges
If the source solid has faces the kernel cannot sew shut, the tessellated shell can come out with open boundaries. Slicers usually repair small gaps, but check the preview.
Detail level changes file size, not accuracy claims
Higher detail means more triangles and a closer fit to the true surface. It does not make the geometry 'more correct' — the underlying B-rep is exact either way.
Colours and multi-part builds are not written
3MF can carry per-object colour and a build plate layout. A legacy surface conversion produces one uncoloured object — the container's richer features need richer sources.
Frequently asked questions
Can I convert on this page itself?
No. This page is the reference for the IGES to 3MF path, and the conversion itself runs in the workspace that the button above opens, with both formats already selected. Your file is read in that browser tab and the download is written locally, so there is no upload stage in either place. Keeping the documentation and the engine on separate addresses lets file support and detail levels change behind one workspace without breaking the page you are reading.
Does 3MF keep the IGES unit?
The mesh is written in the numbers the tessellation produced (no rescale), and the package declares millimetres. If your IGES was authored in inches, scale it before or after — check the bounding box.
Why 3MF instead of STL for printing?
Declared units and a zip container that stores structure. Slicers read both; 3MF removes the unit guesswork.
Will Cura and PrusaSlicer open it?
Yes — both read 3MF natively, and Windows 3D Builder opens it too.
References
- OpenCascade documentation — B-rep, IGES and tessellation
- 3MF Consortium specification
- How this site is built and tested
Related converters
All converters
Last updated: