Add your IGS file
Drop one or more .igs files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Converting .igs CAD geometry to .gltf triangulates exact engineering surfaces into a mesh that printers and viewers understand. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Converting .igs CAD geometry to .gltf triangulates exact engineering surfaces into a mesh that printers and viewers understand. An .igs file contains IGES CAD data under the abbreviated extension that early file systems, limited to three characters, forced on the format. Nothing but the name differs from .iges: the same punch-card-style text encodes the same curves, surfaces, and drawing entities.
A .gltf file is the JSON form of Khronos glTF 2.0: it describes nodes, meshes, accessors, and buffer references in text, often pairing with external .bin buffers or embedding them as data: URIs. It is the editable, inspectable sibling of binary .glb. For this route the practical draw is human-readable scene description and same data model as GLB, so round-trips are straightforward — balanced against external buffer URIs make a lone .gltf file incomplete, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .igs, two spellings for one format regularly confuse file filters and format lists. Switching to .gltf buys you human-readable scene description, which is why it is the better fit for inspecting or hand-editing mesh package structure. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | IGES model (.igs) | glTF mesh (.gltf) |
|---|---|---|
| Format type | Vector — resolution-independent geometry instead of pixels | Vector — resolution-independent geometry instead of pixels |
| How it stores data | the same five-section, 80-column record structure as .iges, with a letter code in column 73 marking each section | uTF-8 JSON with required asset.version 2.0 and optional scenes, nodes, meshes, accessors, bufferViews, and buffers |
| Strongest at | reading decades-old supplier geometry that shipped with the short extension | inspecting or hand-editing mesh package structure |
| Weak spot | two spellings for one format regularly confuse file filters and format lists | external buffer URIs make a lone .gltf file incomplete |
| Metadata | the same Global-section fields as the longer spelling: sender, author, units, and timestamps, and little else | copyright and generator strings sit under asset; application-specific data is commonly stored in extras |
Drop one or more .igs files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .gltf in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if GLTF is selectable, the route is real and validated.
Press Convert. Open CASCADE compiled to WebAssembly triangulates the exact CAD geometry into a mesh inside your browser.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid GLTF file. Outputs keep the original filename with the .gltf extension.
Since igs is vector-oriented and gltf is vector-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .gltf itself requires.
Yes — the .igs file is processed inside your browser tab and never uploaded. Open CASCADE compiled to WebAssembly triangulates the exact CAD geometry into a mesh inside your browser. Close the tab and the file is gone from memory.
The same ecosystem that reads .glb generally reads .gltf, provided referenced buffers resolve. Browser viewers, Blender, and engine importers expect either embedded data URIs or co-located .bin files.
It depends on the content: uTF-8 JSON with required asset.version 2.0 and optional scenes, nodes, meshes, accessors, bufferViews, and buffers. Convert one representative file first and compare before batch-processing a large set.
In .igs, the same Global-section fields as the longer spelling: sender, author, units, and timestamps, and little else. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.