Grasshopper 3D is the visual programming environment included with Rhino for computational and parametric design. Architects, engineers, façade specialists, and fabricators connect components on a canvas to generate geometry, process data, and test design variables without building every option manually. It works directly with Rhino’s modeling environment and can extend into BIM, analysis, optimization, and fabrication workflows through official integrations, scripting, and plugins.
Grasshopper is the graphical algorithm editor included with Rhino 3D. McNeel describes it as a visual programming environment tightly integrated with Rhino’s modeling tools. The definition controls logic and relationships; Rhino supplies the geometry kernel, viewport, document, object attributes, file exchange, and downstream modeling environment.
Work is assembled from components with inputs and outputs connected by wires. Sliders, referenced Rhino objects, files, or other parameters feed operations that create geometry or transform data. When an input changes, dependent components recalculate and the Rhino viewport previews the result. Approved geometry can then be baked into the Rhino document for editing, annotation, exchange, or fabrication.
This feedback loop supports rapid iteration, but it does not make every model safely parametric. A useful definition exposes meaningful controls, groups related operations, names critical parameters, and separates temporary exploration from deliverable logic. A canvas that only its author can read becomes a project risk even when its final geometry looks correct.
Simple examples pass one item or one list between components. Production definitions often organize nested collections as data trees with paths, branches, and items. McNeel’s data-structure guide distinguishes single items, lists, and trees because components behave differently as input structure changes. Unexpected grafting, flattening, matching, or path operations can produce plausible but incomplete geometry, so teams should test data structure explicitly rather than debug only the viewport.
Architects can test massing constraints, panelize envelopes, place repeated elements, calculate quantities, organize drawing geometry, or prepare fabrication data. Engineers and specialist consultants can connect geometry to discipline analysis through supported plugins. Fabricators can translate controlled parameters into part geometry, naming, or machine-oriented outputs.
The core application does not automatically provide every environmental, structural, optimization, or BIM capability. Those workflows may rely on plugins, custom scripts, external solvers, and project-specific validation. The author must still check units, tolerances, constructability, design criteria, and whether generated outputs remain traceable to the approved inputs.
Revit workflows are supported through Rhino.Inside.Revit, which loads Rhino and Grasshopper inside the Windows application. Revit-aware components can query, analyze, create, or modify document content and provide access to Rhino, Grasshopper, and Revit APIs. This is more capable than a simple geometry export, but native BIM quality still depends on category, type, level, parameter, hosting, and update decisions.
Teams should agree which system owns each element and how reruns are controlled. An interactive graph that modifies a live BIM document needs selection safeguards, transaction awareness, version testing, and a recovery plan. Rhino.Inside.Revit is Windows-only even though Rhino and Grasshopper also run on Mac.
Rhino 8 supports RhinoCommon C# and CPython in Grasshopper on Windows and Mac. McNeel’s Grasshopper developer guides cover algorithms, data trees, Python, C#, components, and plugin development. The Package Manager and food4Rhino ecosystem add specialist tools for analysis, fabrication, interoperability, optimization, and visualization.
Dependencies need the same control as other production software. Record plugin names and versions, approved download sources, operating-system support, license terms, and replacement options. Keep a clean test environment for upgrades, and avoid distributing a GH file without its dependency list, sample inputs, expected outputs, and author or maintainer.
There is no separate current Grasshopper subscription or standalone price. It is included with Rhino 8, which McNeel sells through perpetual commercial and discounted educational licenses. Prices vary by region, currency, tax, license type, and reseller, so the official Rhino sales page is the correct source for a current figure. Purchased licenses do not expire; upgrades to later major versions are optional purchases.
McNeel also provides a one-time 90-day full-version Rhino evaluation that includes Grasshopper. After 90 days, saving and plugins stop working unless a license is purchased. That evaluation is a better description of access than calling Grasshopper independently free.
Grasshopper follows Rhino 8’s desktop support. McNeel’s current requirements cover Windows 10 or 11 and supported macOS releases, with at least 8 GB RAM recommended. Windows guidance also recommends an OpenGL 4.5-capable graphics card and 4 GB video memory. Computationally heavy definitions, large meshes, analysis solvers, and several linked applications can require substantially more capacity.
Plugin availability, UI behavior, file paths, scripting packages, and integrations may differ between operating systems. A team should validate the entire definition and dependency set on the target platform rather than treating Rhino compatibility as proof that every component will run identically.
Grasshopper fits teams that repeatedly explore or generate geometry and can invest in computational-design standards. It is less suitable when a one-off manual edit is faster, when project partners cannot run the dependencies, or when no one owns the definition after handover. Alternatives include native Rhino modeling, scripting directly in Python or C#, BIM-platform automation, and other node-based environments.
For project use, review a definition like production code: document inputs and outputs, organize the canvas, control dependencies, test edge cases, compare generated results with design criteria, and archive a known working environment. The value is not the number of components; it is a reliable method that another team member can understand and rerun.
Grasshopper is the graphical algorithm editor included with Rhino 3D. McNeel describes it as a visual programming environment tightly integrated with Rhino’s modeling tools. The definition controls logic and relationships; Rhino supplies the geometry kernel, viewport, document, object attributes, file exchange, and downstream modeling environment.
Work is assembled from components with inputs and outputs connected by wires. Sliders, referenced Rhino objects, files, or other parameters feed operations that create geometry or transform data. When an input changes, dependent components recalculate and the Rhino viewport previews the result. Approved geometry can then be baked into the Rhino document for editing, annotation, exchange, or fabrication.
This feedback loop supports rapid iteration, but it does not make every model safely parametric. A useful definition exposes meaningful controls, groups related operations, names critical parameters, and separates temporary exploration from deliverable logic. A canvas that only its author can read becomes a project risk even when its final geometry looks correct.
Simple examples pass one item or one list between components. Production definitions often organize nested collections as data trees with paths, branches, and items. McNeel’s data-structure guide distinguishes single items, lists, and trees because components behave differently as input structure changes. Unexpected grafting, flattening, matching, or path operations can produce plausible but incomplete geometry, so teams should test data structure explicitly rather than debug only the viewport.
Architects can test massing constraints, panelize envelopes, place repeated elements, calculate quantities, organize drawing geometry, or prepare fabrication data. Engineers and specialist consultants can connect geometry to discipline analysis through supported plugins. Fabricators can translate controlled parameters into part geometry, naming, or machine-oriented outputs.
The core application does not automatically provide every environmental, structural, optimization, or BIM capability. Those workflows may rely on plugins, custom scripts, external solvers, and project-specific validation. The author must still check units, tolerances, constructability, design criteria, and whether generated outputs remain traceable to the approved inputs.
Revit workflows are supported through Rhino.Inside.Revit, which loads Rhino and Grasshopper inside the Windows application. Revit-aware components can query, analyze, create, or modify document content and provide access to Rhino, Grasshopper, and Revit APIs. This is more capable than a simple geometry export, but native BIM quality still depends on category, type, level, parameter, hosting, and update decisions.
Teams should agree which system owns each element and how reruns are controlled. An interactive graph that modifies a live BIM document needs selection safeguards, transaction awareness, version testing, and a recovery plan. Rhino.Inside.Revit is Windows-only even though Rhino and Grasshopper also run on Mac.
Rhino 8 supports RhinoCommon C# and CPython in Grasshopper on Windows and Mac. McNeel’s Grasshopper developer guides cover algorithms, data trees, Python, C#, components, and plugin development. The Package Manager and food4Rhino ecosystem add specialist tools for analysis, fabrication, interoperability, optimization, and visualization.
Dependencies need the same control as other production software. Record plugin names and versions, approved download sources, operating-system support, license terms, and replacement options. Keep a clean test environment for upgrades, and avoid distributing a GH file without its dependency list, sample inputs, expected outputs, and author or maintainer.
There is no separate current Grasshopper subscription or standalone price. It is included with Rhino 8, which McNeel sells through perpetual commercial and discounted educational licenses. Prices vary by region, currency, tax, license type, and reseller, so the official Rhino sales page is the correct source for a current figure. Purchased licenses do not expire; upgrades to later major versions are optional purchases.
McNeel also provides a one-time 90-day full-version Rhino evaluation that includes Grasshopper. After 90 days, saving and plugins stop working unless a license is purchased. That evaluation is a better description of access than calling Grasshopper independently free.
Grasshopper follows Rhino 8’s desktop support. McNeel’s current requirements cover Windows 10 or 11 and supported macOS releases, with at least 8 GB RAM recommended. Windows guidance also recommends an OpenGL 4.5-capable graphics card and 4 GB video memory. Computationally heavy definitions, large meshes, analysis solvers, and several linked applications can require substantially more capacity.
Plugin availability, UI behavior, file paths, scripting packages, and integrations may differ between operating systems. A team should validate the entire definition and dependency set on the target platform rather than treating Rhino compatibility as proof that every component will run identically.
Grasshopper fits teams that repeatedly explore or generate geometry and can invest in computational-design standards. It is less suitable when a one-off manual edit is faster, when project partners cannot run the dependencies, or when no one owns the definition after handover. Alternatives include native Rhino modeling, scripting directly in Python or C#, BIM-platform automation, and other node-based environments.
For project use, review a definition like production code: document inputs and outputs, organize the canvas, control dependencies, test edge cases, compare generated results with design criteria, and archive a known working environment. The value is not the number of components; it is a reliable method that another team member can understand and rerun.
See Grasshopper in action through screenshots and short videos.
These are the firms already using Grasshopper on their projects.
Verified reviews from AEC professionals who use Grasshopper.
See how Grasshopper stacks up against similar tools before you decide.
Rhino 3D (Rhinoceros) is professional NURBS-based 3D modeling software from Robert McNeel & Associates, used by architects, industrial designers, engineers, and digital fabrication specialists. It creates accurate freeform surfaces and parametric geometry for conceptual design, facade engineering, and fabrication-ready models. Grasshopper's visual programming environment is included for computational and generative design workflows.
Raven is the AI agent inside Rhino and Grasshopper. Describe what you want in plain language, with sketches, images or files, and Raven builds and edits Rhino geometry, Grasshopper definitions and scripts. Every change appears as a diff preview you accept or reject, and you can lock parts of a canvas so Raven only works where you allow. Reven includes the strongest AI models and 200+ generative media models with nothing to set up, plus team-wide sharing of skills and files. Runs on Rhino 8 and 9, Windows and macOS.
Rhino.Inside.Revit is a free add-on from Robert McNeel & Associates that embeds Rhino and Grasshopper directly inside Autodesk Revit. It gives architects and engineers a translation API and new Grasshopper components for converting geometry and data between Rhino and Revit, enabling custom parametric and free-form design workflows without leaving Revit.
