Rhino 3D Tip: Managing Rhino Units for Accurate File Exchange

When exchanging Rhino files with clients, consultants, fabricators, or other CAD applications, unit management is not a minor setup detail—it is essential for protecting the intended scale of the model.

Rhino stores model geometry in the document’s current unit system. If a file created in millimeters is opened or imported into a document working in inches, an incorrect unit decision can make a part appear 25.4 times too large or too small. That discrepancy can affect tolerances, annotation, blocks, rendering assets, layouts, and downstream manufacturing data.

• Verify units before modeling. Run Units and confirm the Model units setting before creating geometry. Architectural projects may use feet, inches, millimeters, or meters; product and fabrication workflows commonly use millimeters or inches. Establish the standard at the beginning of the project rather than attempting to correct scale later.
• Distinguish “unit change” from “unit conversion.” In the Units dialog, Rhino asks whether existing geometry should be scaled when changing units. This decision matters:
  • Choose Yes when the model is correctly sized and you are converting its measurement system—for example, changing a 100 mm object to inches. It should become 3.937 in, not 100 in.
  • Choose No only when the geometry was created with the wrong unit label and its numeric dimensions need to remain unchanged. For example, a model intended to represent 100 inches but labeled as 100 millimeters may require a unit reassignment without scaling.
• Check imported files immediately. DWG, DXF, STEP, IGES, SAT, STL, and other formats may carry unit information differently. After importing, measure a known feature with Distance or use BoundingBox to compare the result with an expected real-world size. A standard door width, fastener diameter, sheet thickness, or overall part dimension can quickly expose a scaling error.
• Do not use Scale as the first fix. Scaling imported objects may visually correct the size, but it can introduce confusion when blocks, annotations, layouts, tolerances, or linked reference files are involved. First identify the source and destination units; then use Rhino’s unit conversion intentionally. Use Scale only when you have confirmed that the source geometry itself was modeled at an incorrect scale.
• Coordinate with collaborators. Before exchanging files, state the units explicitly in the file name, transmittal note, or layer documentation: ProjectName_MM.3dm is more informative than ProjectName_Final.3dm. This is especially helpful when sharing files across Rhino, AutoCAD, Revit, SolidWorks, CAM, and 3D-printing workflows.
• Inspect tolerances after conversion. Document absolute tolerance is unit-dependent. A tolerance that is appropriate in millimeters may be impractical when interpreted in inches or meters. Review it under File > Properties > Units, particularly before joining surfaces, running booleans, exporting manufacturing geometry, or meshing for printing.

For reliable handoffs, make unit verification part of your export checklist: confirm document units, measure a known feature, review tolerance, save a copy, and communicate the intended unit system. This small discipline prevents expensive downstream corrections and keeps everyone working from the same scale.

For Rhino software, training, and workflow resources, visit NOVEDGE’s Rhino collection.

You can find all the Rhino products on the NOVEDGE web site at this page.