Rhino Model Rendering Service, No Modeling Needed
Quick answer: Send the .3dm file with layers left as you built them and a note on which layers are final. Rhino geometry is mathematical surfaces, so it has to be converted to a mesh to render, and the quality of that conversion separates a smooth facade from a faceted one.
Why Rhino models render beautifully, once they are meshed correctly
Rhino builds geometry from mathematics. A curve is defined by control points and a degree, and a surface is defined by a grid of them. The result is smooth at any zoom, which is why architects use Rhino for shells, facades and forms that other software struggles with.
A renderer, however, does not work with mathematical surfaces. It works with triangles. Before a Rhino model can be rendered, every surface is converted into a mesh of small flat faces. How fine that mesh is decides whether a curved wall looks like a perfect curve or a faceted approximation. It also decides how heavy the file becomes. Too coarse and curves show polygon edges. Too fine and the scene becomes unwieldy. Getting this conversion right is the most important technical step in rendering a Rhino model.
This is a job for someone who has done it many times. It is also the reason a Rhino model sent to a general rendering service can come back with visible facets on exactly the surface you were proudest of.
Layers do the organizing, so leave them as you built them
In Rhino, layers are how a project stays understandable. A well built model has one layer per building element or material: walls, glazing, roof, structure, site. That structure is gold for rendering, because materials can be assigned per layer.
A less tidy model has construction curves, alternate options and old versions scattered among the final geometry. In that case, the useful thing you can do is tell us which layers hold the final design and which to hide. You do not need to reorganize. A short list is enough: "Final is layers 01 to 12. Hide Option A, Option B and Sketches."
Grasshopper and parametric forms
Many Rhino projects are driven by Grasshopper definitions. The form, the facade pattern or the structure is computed from parameters. For rendering, what matters is the baked geometry, meaning the actual surfaces in the file. The definition itself is not needed, and we do not render from it.
Two things help. First, bake the final version of the geometry into the model, on its own layers. Second, if the definition has produced several variants during design, tell us which one is the approved design. Otherwise we may render an intermediate variant that happens to be in the file.
Six checks before you send a Rhino file
- Run SelBadObjects. It finds surfaces with problems. Fix or tell us about the ones that cannot be fixed.
- Check for naked edges. Use ShowEdges, and pick Naked Edges. Open edges cause light leaks and holes in the render.
- Join surfaces that belong together into closed polysurfaces. Closed solids render more predictably.
- Confirm the units. Check Document Properties, Units. A model in millimeters treated as meters produces wrong scale and wrong light.
- Remove duplicates. Use SelDup to find geometry stacked on itself.
- Name your views. Save named views for the camera positions you want.
None of this is required for us to start, but each item you do saves a round of questions.
Where Rhino projects need extra care
Certain kinds of Rhino geometry deserve attention because they are the reason people use Rhino in the first place.
- Curved glass and shells. Their quality depends on the meshing detail and on realistic glass. Facets in a reflection are visible immediately.
- Perforated screens and patterns. Thousands of holes are heavy. If only some will be visible, we optimize the rest.
- Tensile structures and membranes. Their thin surfaces need thickness to avoid rendering artifacts.
- Complex trims. Trimmed surfaces with tiny slivers can produce visible cracks after meshing. Reporting them early helps.
Telling us which parts matter most in the images lets us focus effort where the viewer will look.
Mesh density, in practice: where fine matters and where coarse is fine
Meshing is a budget. You have a limited number of triangles you can afford across a scene, and the skill lies in spending them where the eye goes. A curved glass wall seen head-on needs a very fine mesh, because a faceted reflection is immediately visible. A flat plaza seen from a distance needs almost none. A roof that curves away from the camera can be meshed more coarsely along its far edge, where the silhouette is small.
The practical consequence for you is simple: tell us which views are the most important. A hero image of the facade justifies a finer mesh on the facade. A background view of the rear elevation does not. This is the kind of information that never appears in a file but changes the quality of the result.
Solids, surfaces and why closed geometry renders better
Rhino lets you keep single surfaces, open polysurfaces and closed solids in the same file. A renderer handles closed solids best, because it knows what is inside and what is outside. A wall built as a single surface with no thickness is a paper-thin sheet. It can leak light along its edges, look wrong from the back and confuse glass or subsurface materials.
If your design holds thin sheets for walls or roofs, that is fine for drawing but worth mentioning. We can give them thickness in the render copy, following the wall thickness you specify. That is a small, honest translation, and it is not a change to your design. What matters is that you tell us the intended thickness so that we match your drawings rather than invent something.
Materials for Rhino projects: from intent to surface
Rhino users often come from the design side, so they arrive with material intent rather than a schedule: warm timber, raw concrete, brushed metal, fritted glass. That is enough. We translate intent into physically based materials with the right roughness, reflectivity and grain direction, and we send previews so that you can react to the actual look. Where a specific product matters, such as a particular cladding, send a photo or a link. Where it does not, describe the mood, and we will propose options that you can compare side by side.
Grain direction is a small example of why this matters. A timber roof that follows a double curve has grain that follows the curve. Getting that right depends on how the surface parameterization was built in the model, and it is one of those details that separates a convincing image from a decorated one.
Blocks, instances and repeated elements in Rhino
Rhino handles repeated elements through block instances: one definition placed many times. Blocks are ideal for render preparation, because they let us change a material or replace an object once and see it update everywhere. If your model contains hundreds of identical panels, columns or louvers, keep them as blocks instead of exploding them. An exploded block is just a pile of geometry, and it makes the file heavier and harder to manage without any benefit to the design. If some have already been exploded, tell us, and we can often recognize and rebuild the repetition on our side.
A worked example: a curved facade pavilion
A design firm has a small pavilion modeled in Rhino: a double-curved timber roof, glazed walls and a stepped plaza. The roof was generated with Grasshopper, and the definition produced eleven variants during the design phase. The model holds the baked final version on one layer and the previous ten on hidden layers, named only by number.
The firm sends the .3dm with a note: "Final roof is layer 07. The others are history." The file check finds two naked edges on the glazing frames and a trim sliver on one roof panel. We report them. The firm fixes one, and we repair the other in the render copy. The roof is meshed at a fine density, since it is the most visible surface, and the plaza at a coarser one, since it is mostly flat.
The result is a set of images where the roof reads as a single continuous curve, timber grain follows the surface direction, and the glass reflects the sky without visible facets. The firm did not redraw a line.
What we keep and what we do not change
Rhino is often used for early, expressive design, so it is worth being explicit. We do not fair curves, tidy surfaces or reinterpret a form. If a surface has a kink, it stays a kink unless you tell us otherwise. The intent is that the image shows your design, not our version of it. When we find something that looks like an accident, we point it out and you decide.
What to send
- The .3dm file, with layers as you built them.
- A note of which layers are final and which to hide.
- The units and, if relevant, the Rhino version.
- Named views or a list of the shots you want.
- Material intent: timber, concrete, metal, glass types, even in rough words.
- The purpose of the images and the deadline.
Questions worth asking any studio about Rhino files
- How do you mesh curved surfaces, and can I see an example of a curved facade you rendered?
- Do you work from the baked geometry, and will you tell me about problems instead of rounding them off?
- Can you handle heavy parametric patterns without simplifying what is visible?
- Will I get a preview to check the curves before final output?
Frequently asked questions
Do you need the Grasshopper file?
No. The baked geometry in the .3dm is what we render. Bring the final variant onto its own layer and tell us which it is.
Will curved surfaces look smooth?
Yes, when they are meshed at a suitable density. That conversion is part of the setup, and visible surfaces get the finest detail.
Can you keep my layer names?
Yes. Layer structure helps us assign materials and is preserved.
What if my surfaces have gaps or naked edges?
We report them. Small repairs are part of file review, larger ones are quoted as modeling work.
Which Rhino versions work?
Recent versions are fine. Tell us the version if the file is older, and we will check before starting.
Can you render from a mesh export instead of the .3dm?
Yes, though the native file is better because we control the meshing quality ourselves.
Will you change my form to make it render better?
No. The geometry stays exactly as you built it. We flag problems and you decide what to do.
Can the same model also produce an animation?
Yes. A clean model can be reused for animated flythroughs. Say so at the start so the scene is prepared for it.
Related guides
This guide is part of our series on rendering when the 3D model already exists. Start with the overview, rendering only when you already have the model. Related: ArchiCAD model rendering, Blender file rendering, OBJ and FBX file rendering. When you are ready, send the file and the deadline through our quote request.