Free online 3DM to STP converter

A Rhino model may need conversion when a supplier, manufacturing system, or mechanical CAD application accepts STEP but not Rhino's native format. Exporting to .stp or .step also provides a broadly supported copy for inspection, downstream editing, and manufacturing exchange.

What the 3DM format is

.3dm is the native file format of McNeel Rhinoceros. It stores NURBS curves, surfaces, polysurfaces, solids, meshes, layers, object attributes, views, lights, annotations, and some material and rendering data. Rhino, Rhino for Mac, and software built with the openNURBS toolkit can create or read 3DM files.

3DM files are common in industrial design, jewelry, architecture, product development, and engineering workflows. A file can contain precise CAD geometry alongside meshes, construction objects, Grasshopper-related data, annotations, and display settings; these categories do not all have direct STEP equivalents.

What the STP format is

.stp and .step are filename extensions for ISO 10303 STEP. STEP normally represents mechanical geometry as boundary-representation solids, shells, and surfaces. Depending on the application protocol and exporter, it can also carry assemblies, part names, colors, layers, and other product information.

STEP is suitable when the recipient must open, measure, inspect, modify, or manufacture the model in another mechanical CAD system. It generally preserves precise NURBS and analytic surfaces better than mesh formats, but it does not preserve Rhino construction history, Grasshopper definitions, named views, rendering settings, or every annotation.

How to convert the file

Rhino desktop is the preferred option when the source contains Rhino NURBS geometry, multiple parts, or assemblies.

1. Open the .3dm file in Rhino.
2. Check the document units through File → Properties → Units. Confirm the intended unit system before export, then verify the scale after import because receiving software can apply its own unit settings.
3. Inspect the geometry. Use ShowEdges to find naked edges, SelBadObjects to select invalid objects, and Join to combine compatible surfaces. Repair open or invalid polysurfaces before exporting if the recipient needs closed solids.
4. Select the objects to transfer. Exporting only the required parts avoids sending construction geometry, meshes, lights, or other unwanted objects.
5. Choose File → Export Selected, or use File → Save As when exporting the complete document. Select STEP (*.stp; *.step) and specify the output filename.
6. In the export options, select the STEP application protocol supported by the recipient. AP242 or AP214 can preserve more product and appearance information than older schemes when the target system supports them; use AP203 for a legacy workflow that requires it. Available schemes and options vary by Rhino version.
7. Open the result in the target CAD system and check the unit system, part and body count, solid status, critical dimensions, holes, fillets, and mating interfaces.

Rhino's STEP exporter is generally the safest choice for a file containing Rhino-specific NURBS geometry. A STEP file contains exchanged geometry, not an editable Rhino feature tree, so it will not reproduce parametric operations or Grasshopper logic.

CAD Exchanger Desktop or Cloud can also read supported 3DM files and write STEP files. In the desktop application, open or import the 3DM file, choose STEP as the export format, select available protocol or tessellation settings, and export. In CAD Exchanger Cloud, upload the file, choose STEP, run the conversion, and download the result. Check the current product's 3DM support, file-size limits, and available STEP settings before using it because service capabilities change.

Use a local desktop converter for confidential designs, controlled technical data, large assemblies, or files that require repeated repair and validation. Uploading such files to an online service exposes them to that service's storage and processing policies.

Quality and compatibility limits

STEP does not preserve the complete Rhino document. Layers, object names, colors, and assembly relationships may transfer, but construction history, dimensions, text, named views, Grasshopper data, lights, render materials, viewport settings, and custom attributes may be lost or translated differently.

Mesh objects are not equivalent to STEP boundary-representation solids. An exporter may omit them, write them as non-solid geometry, or require a separate mesh-to-surface workflow. Converting a dense mesh into NURBS can produce a large, inaccurate, or difficult-to-edit STEP file; export the original Rhino solids or joined polysurfaces whenever possible.

A closed Rhino polysurface can still arrive as separate faces or an invalid body because of tolerance, trimmed-surface, or topology issues. Run the receiving CAD application's geometry check, sew or heal surfaces there when appropriate, and compare critical measurements with the 3DM source. If the result is defective, repair naked edges and invalid objects in Rhino and export again rather than relying on automatic mesh reconstruction.