Rhino STL export: keep the right size and the detail you need

Before exporting an STL from Rhino, identify the geometry you are sending and choose a physical dimension to check in the slicer. These two decisions help you separate mesh-detail problems from a file that arrives at the wrong scale.

Work on a copy, inspect the mesh, export only the intended objects, then open the saved STL and compare it with the source. Check its structure as well as its shape. A smooth-looking part can still have an open boundary, and a closed mesh can still be the wrong size.

Scope: Rhino 8 for Windows. Receiver steps use the documented PrusaSlicer 2.9 interface, which Prusa labels Legacy; check your own version before following those controls. This documentation-based guide was prepared with AI assistance. No export, slicer operation or physical print was performed for this article.

Choose the route that matches your source

Keep the editable source and give the export copy a clear revision name. Select an object and run What to identify its type. Viewport shading alone won't tell you which route you need.

Scroll the table horizontally to read every column.

Rhino can mesh NURBS during STL export, or you can create a separate polygon object with Mesh and inspect it first. McNeel's older export discussion explains why those NURBS controls are unavailable for an existing mesh. It supports the distinction, rather than current Windows interface placement.

If the surfaces have unresolved faults, use the geometry QA guide. If the mesh has holes, non-manifold connections or inconsistent normals, use the mesh repair guide and the documented MeshRepair panel. Choose export settings after you understand the input. If you are considering reconstruction, the ShrinkWrap guide explains its settings and the features to compare.

Pick a dimension and a feature to check twice

Choose a distance with clear endpoints, such as the outside width of the part. Write down its expected physical size and units. Also identify a feature that must survive: an opening, curved edge or small relief. Agree the allowable differences with the designer or supplier before judging the result. If a limit is missing, flag that question for them.

Rhino's Units properties distinguish model units and document tolerance. Changing units prompts a decision about scaling the geometry; check the known dimension after any change. Document tolerance is used by geometry operations. Mesh approximation and finished-part tolerances answer different questions.

State the intended units with the STL and compare the known distance in the receiver. McNeel's units explanation describes why the file alone is insufficient. Don't assume that every slicer interprets its numbers in the same units.

For a hypothetical 50 mm wide plate with an opening that must remain clear, write “50 mm” and name that opening before export. Leave the observed width, opening check and decision blank until you inspect the file. Those example inputs do not establish a meshing value, an allowable error or a passing result.

Choose mesh controls for the feature you need

For NURBS, select the intended objects, run Mesh, open Detailed Controls and preview the output. Keep the original available for comparison. The Document Mesh properties govern global render-mesh quality; a pleasant shaded view is not a check of the saved STL.

Use FlatShade to make individual facets visible without smoothing. Compare the curved edge or opening you identified. This helps reveal faceting; it does not measure the mesh's maximum deviation from the source.

The following controls are documented in the Rhino 8 Mesh reference. Use the inspection targets to choose what to investigate for your part.

Scroll the table horizontally to read every column.

Refinement is disabled for extrusions and ruled surfaces. Keep that exception in mind if a setting seems ineffective. The midpoint criterion is not a certified error bound for every point of the output.

Density and Maximum aspect ratio also affect the result. Smaller positive aspect-ratio limits generally produce more evenly shaped polygons at the cost of more polygons and slower meshing; see the Mesh properties reference. Keep the full settings with the export notes. Change one relevant control at a time and compare the same feature, so you can see what the change achieved. More facets are useful when they resolve a visible or measured shortfall; a larger file alone is not an improvement.

When exporting NURBS directly, the STL dialog offers Tolerance for the source-to-mesh approximation and a Preview button. Refresh Preview after changing settings. That approximation setting is separate from the allowable error in the finished part; layer height alone does not establish acceptable mesh error in every direction.

Save only the objects you intend to send

Select the output you inspected and use Export Selected, choosing STL. Choose binary or ASCII to suit the recipient; the documented PrusaSlicer formats support both. Encoding is not a geometric-accuracy control.

Rhino displays a warning if the STL mesh is open. Export Anyway saves it without closing it, as the STL help explains. Investigate an unexpected warning before sending the file. If an open boundary is intentional, confirm that the receiving task permits it.

Give the saved STL an identifiable revision. Keep its encoding, file size, settings and warning notes with that filename so later checks refer to the exact file you send.

Open the saved STL and check its structure

Reimport the saved file into a separate Rhino document. Note the import units, weld angle and Split disjoint meshes choice; the STL import options explain how these affect the imported object. Compare the known distance and required features with the retained source.

Then inspect the imported mesh:

• Run Check for reported data-structure errors. A passing report does not detect every geometric problem.
• Use ShowEdges to locate naked and non-manifold edges. Require closure when the receiving process needs a closed mesh.
• Use Check Mesh in the MeshRepair panel to examine findings such as inconsistent normals and disjoint pieces. Also compare face orientation and connected pieces with the intended model: consistent normals alone do not establish the intended outward side.

Resolve unexpected findings before accepting the file. These checks answer structural questions; they do not establish that the opening is the correct size. If you repair the inspection copy, save a new export revision and repeat the saved-file and receiving checks. The previous STL on disk has not changed merely because the reimported copy was edited.

Check the same file in the slicer

In the documented PrusaSlicer 2.9 workflow, import the saved STL with Add, drag and drop, or File → Import. Note the actual application version and any conversion, scaling, repair or warning. Inspect orientation before slicing and choose the intended printer, material and print setup.

Use the Measurement tool to compare the known distance. It recognizes vertices, edges, circles and planes within one object. Overlapping parts can expose hidden internal planes while intersection edges are missed; negative volumes also have limitations. Choose references that represent the outside width or feature you actually need. The tool can scale an object from its measurement, so distinguish reading a distance from changing it.

If the size differs, check units, scale and measurement references before altering the model. Per-axis scaling and Scale to fit change its size. Fitting the bed does not establish the correct physical dimensions. After any deliberate correction, compare the same distance again and keep the scale change with the file's notes.

Click Slice now, then inspect the overall shape and the layers through the required opening or relief. Prusa's preview instructions describe the layer slider. Check whether the feature remains in the toolpath preview, and investigate unexpected warnings or geometry changes. Keep the relevant preview with the printer/profile information. A physical print is a separate test.

Keep a short worksheet with the STL

Use the worksheet to keep the export settings, dimension checks and reviewer notes with the file. Fill observed values only after carrying out the check.

Scroll the table horizontally to read every column.

Before sending the STL, have the reviewer compare its dimensions, required features, structure and slice preview with the agreed specification. Resolve unexplained differences against the exact revision being sent. Keep those notes with the file; the Rhino handoff guide covers the wider packaging and ownership questions.