Add your STEP file
Drop one or more .step 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 .step 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 .step CAD geometry to .gltf triangulates exact engineering surfaces into a mesh that printers and viewers understand. A .step file stores an exact 3D product model under ISO 10303, the international standard known as STEP (Standard for the Exchange of Product model data). Unlike mesh formats it records precise boundary-representation geometry, so a cylinder stays a true cylinder rather than a bundle of triangles, which makes it the lingua franca for moving parts between CAD packages from different vendors.
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 .step, verbose text files that grow large and import slowly on complex assemblies. 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 | STEP 3D model (.step) | glTF mesh (.gltf) |
|---|---|---|
| Format type | Vector — resolution-independent geometry instead of pixels | Vector — resolution-independent geometry instead of pixels |
| How it stores data | plain-text Part 21 files open with the literal header ISO-10303-21; and contain a HEADER section followed by numbered entity instances in a DATA section | uTF-8 JSON with required asset.version 2.0 and optional scenes, nodes, meshes, accessors, bufferViews, and buffers |
| Strongest at | moving solid models between different CAD systems, such as SolidWorks to Fusion 360 or CATIA to NX | inspecting or hand-editing mesh package structure |
| Weak spot | verbose text files that grow large and import slowly on complex assemblies | external buffer URIs make a lone .gltf file incomplete |
| Metadata | the Part 21 header records author, organization, originating system, and timestamps, and product entities carry part names and descriptions through the exchange | copyright and generator strings sit under asset; application-specific data is commonly stored in extras |
Drop one or more .step 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 step 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 .step 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 .step, the Part 21 header records author, organization, originating system, and timestamps, and product entities carry part names and descriptions through the exchange. 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.