Convert OBJ to 3DM

Rhino and Grasshopper workflows often require a .3dm file for editing, collaboration, or archiving, while 3D scanners, asset libraries, and modeling tools commonly deliver .obj meshes. Converting the file places that mesh in a Rhino document, but does not automatically create editable CAD surfaces.

What the OBJ format is

OBJ is a text-based 3D format that stores polygon vertices, face definitions, texture coordinates, and vertex normals. Materials are commonly described in a separate .mtl file, which can reference external texture images; the OBJ itself may contain only geometry.

Blender, Maya, 3ds Max, Cinema 4D, ZBrush, game engines, 3D scanners, visualization applications, and online asset libraries use OBJ for mesh exchange. OBJ normally contains polygon geometry rather than parametric solids, NURBS surfaces, dimensions, construction history, or native CAD features.

What the 3DM format is

3DM is Rhino’s native document format, based on the openNURBS toolkit. A 3DM file can contain NURBS curves and surfaces, solids, polygon meshes, layers, annotations, materials, render settings, and other Rhino document data.

Saving an imported OBJ as 3DM preserves the model as a mesh. It does not restore CAD topology, modeling history, parametric features, rigging, animation, or other information that OBJ does not contain.

Convert with Rhino

1. Put the .obj, its matching .mtl, and all referenced texture images in one folder. Keep the original filenames and relative paths intact.
2. In Rhino, choose File → Import and select the OBJ file.
3. Review the OBJ import options. Preserve vertex normals for intended shading and texture coordinates for UV-mapped materials. Select the correct import units or scale factor; OBJ files do not reliably carry standardized unit metadata.
4. Inspect the mesh after import. Use SelBadObjects to select invalid objects, Check for diagnostic information, and UnifyMeshNormals when face directions are inconsistent. Recheck the model after repairing it.
5. Choose File → Save As, select Rhino 3D .3dm, choose the required Rhino version if the dialog provides that option, and save the file.

To reduce size before saving, delete hidden or unnecessary objects and materials. Rhino’s ReduceMesh lowers polygon count but can change the silhouette, fine detail, UV coordinates, and texture appearance, so compare the reduced mesh with the original.

Use a desktop converter

CAD Exchanger Desktop is an alternative when Rhino is unavailable and its installed version lists both OBJ import and 3DM export. Open the OBJ, include the associated MTL and texture files when prompted, select the 3DM output, and inspect the result in Rhino. Format support and material preservation vary by product version, so verify the current feature matrix before purchasing or processing a batch.

Use an online converter

CAD Exchanger Cloud can be used for non-confidential files when its current format list offers OBJ input and 3DM output. Upload the OBJ together with its MTL and texture files, select 3DM, download the result, and open it in Rhino for scale, mesh, and material checks. Online services may limit file size, omit textures, change mesh data, or remove unsupported scene information; use local software for proprietary, large, or production-critical models.

Quality and compatibility limits

The usual result is a polygon mesh inside a 3DM container, not a clean Rhino surface model. Rhino’s MeshToNurb converts mesh faces into individual NURBS faces; dense OBJ files can produce thousands of small, difficult-to-edit surfaces and a much larger file. For a usable CAD model, use QuadRemesh and ToSubD where suitable, or rebuild important surfaces from reference geometry. Reverse engineering is required when accurate dimensions, watertight solids, editable features, or high-quality NURBS continuity are needed.

Verify model units and a known measurement after conversion because correct proportions can still have the wrong absolute scale. Check vertex normals, UV coordinates, material assignments, texture paths, open edges, non-manifold regions, and polygon density. Renderer-specific shaders, cameras, lights, animation, rigging, application metadata, and unsupported material settings may not survive in 3DM.