Article / CAD
CAD3D Printing

STL, 3MF, GLB or STEP — choose the file for the job

Separate editable design, print preparation and browser visualization so the recipient gets the right file without unintended design disclosure.

Published: · ING-MC LAB
Source design branches to CAD exchange, additive manufacturing and browser visualization formats.
Original handoff diagram. Conversion paths depend on the authoring and receiving applications.

“Send me the 3D file” is incomplete. Is the recipient reviewing an animation, printing a bracket or changing a mounting hole? Those jobs need different information. Decide what the recipient must do before choosing an extension.

Keep the source design separate

The native design may contain feature history, constraints, sketches and editable parameters. A mesh export describes a surface approximation; it does not automatically preserve that history. However, losing history does not make the visible shape confidential: someone can still inspect or reconstruct dimensions from geometry.

Keep your master design and its dependencies as the authoritative editable source. Name derivative exports by revision and purpose rather than treating every extension as an interchangeable master.

Compare the deliverables

Format Typical purpose Check before delivery
STL Surface mesh for broad slicer compatibility Agreed units, closed surface and tessellation
3MF Additive-manufacturing model/package Units, objects, supported extensions and slicer-specific settings
GLB Browser/runtime visualization Materials, hierarchy, scale, semantic nodes and animations
STEP CAD exchange Imported solids/surfaces and receiving application’s support
.ingmc3d ING-MC scene composition Matching asset IDs/versions and runtime support

STL does not supply an explicit unit convention, so agree on the interpretation. The 3MF specifications define a richer package and unit model; a slicer’s project can also carry application-specific settings. Do not assume another slicer preserves every setting just because it opens the geometry.

The glTF/GLB specification supports scene nodes, materials and optional animation data. A GLB can contain animations; that does not mean a particular export does. The LAB’s machine cycles also depend on runtime JavaScript and generated visual elements.

Validate units with a known dimension

Open the export in the receiving workflow and measure a known reference. A 100 mm feature becoming 100 m reveals a convention problem before it ruins the full scene. Check orientation too: a source authored Z-up may need a reviewed transform in a Y-up viewer, not an arbitrary rotation baked into every child node.

For printing, inspect manifoldness, thin walls and the intended print orientation. A visually attractive model may contain open surfaces or details too small to print. A GLB model of a machine is not automatically a printable or manufacturable assembly.

For a robot viewer, preserve the joints and semantic mounting frames. Flattening everything into one mesh may retain appearance while destroying articulated behavior and annotation references.

A scene file is not necessarily a self-contained package

An .ingmc3d scene records composition and references the asset registry. It does not embed every referenced GLB. The receiving runtime needs the matching asset/version and compatible features. See the scene-file guide before handing off a scene as if it were a complete application.

Likewise, an exported web page may need local scripts, textures and metadata even when its model is a single GLB. Test with the dependencies actually included in the delivery, not with files available only on the author’s computer.

Browser geometry is accessible to the browser user

Any geometry delivered for client-side rendering can be recovered, whether it is GLB, JSON, a compressed binary or embedded in HTML. Compression and hiding a download button are not access controls. A public derivative can omit internal details and sensitive dimensions, but it must be reviewed before release.

If disclosure is unacceptable, use still images, video or an appropriately designed server-rendered experience rather than shipping the detailed model. Package access and licensing are separate decisions: possessing a file does not grant permission to redistribute it.

Deliver a short manifest with revision, units, axes, dependencies, usage rights and verification steps. That small document prevents more errors than simply adding another file format.

Scene composition references an asset registry and separate geometry files.
Article

What an .ingmc3d scene contains

What a scene file stores, how it references 3D assets, and what you need to share it with another Studio user.