If you open Grasshopper every day, Grasshopper 2 has probably been on your radar for years. David Rutten released the first public alpha in April 2022, and on July 30, 2026 McNeel announced it as an official feature of the Rhino BETA. If your work lives in GH1 definitions, that raises three questions. What changed, do my files and plugins still work, and when should I switch?
I teach Grasshopper to architects, so I went through McNeel's announcement, David Rutten's forum answers and the beta threads to answer them with sources. Where something is not confirmed yet, I say so.
Key Takeaways
- Grasshopper 2 is a ground-up rewrite. McNeel describes a new solver, a new data model and a new interface.
- It is a beta inside the Rhino BETA. It installs next to Grasshopper 1 and opens with the GH2 command.
- Grasshopper 1 plugins do not load in Grasshopper 2. Every plugin needs a GH2 version, and the SDK is still evolving.
- GH2 can open .gh files, but McNeel does not recommend it. RhinoAI adds tooling that can rebuild GH1 definitions in GH2.
- There is no fixed release date. The beta label goes away with the Rhino 9 release, which has no announced date.
- Keep production in Grasshopper 1 and learn Grasshopper 2 in parallel. The core concepts carry over.
What Grasshopper 2 Is
In its Grasshopper 2 beta announcement, McNeel calls GH2 "a ground-up rewrite of the visual programming environment you already know", with a new solver, a new data model and a new interface. Grasshopper 1's core architecture "can only stretch so far", so McNeel chose to rebuild the foundation instead of patching it further.
GH2 is written by David Rutten, who created Grasshopper. McNeel's Japhy called it "a single author (lots of help as of late), non-ai assisted production", and has since named a growing team helping with component parity, documentation and core development.
Like Grasshopper 1, it is part of Rhino rather than a separate plugin. Rutten says of GH2 that "it's shipped as part of Rhino9", and for now it lives in the Rhino BETA, which needs a Rhino 8 license. GH2 installs alongside Grasshopper 1, opens with the GH2 command, and both can run at the same time. Our guide to the Rhino 9 beta for architects covers the rest of the release.
Where Grasshopper 2 Stands in October 2026
McNeel is clear about what the beta label means. The announcement lists three limits:
- No feature parity yet. Components are still being added, so "keep production work in GH1".
- No GH1 plugins. They do not load in GH2, and the GH2 SDK is still evolving.
- GH1 files open, with a warning. You can open them, but it is "not a recommended workflow".
On timing, Japhy wrote in April 2026 that GH2 1.0 will follow an SDK that plugin developers can publish on, and that "There isn't a fixed date". In September he added that the beta designation will be removed with the Rhino 9 release, after which GH2 keeps developing on its own cadence. Rutten was more cautious in June, writing that there was "a very small and shrinking chance GH2 won't become production ready by the time R9 ships". McNeel has not announced a Rhino 9 date, so the best answer to "when" is together with Rhino 9.
What Changes on the Canvas
The canvas will feel familiar, with components, wires and sliders. McNeel lists redesigned components and icons, a zoomable interface that reveals more detail as you get closer, dark and light modes, and in-canvas widgets that put settings where you are working.
Help is the other big change. Every component has its own documentation page inside GH2, pressing ? searches components, and GH2 ships with over 120 example definitions and a glossary of more than 300 terms.
The Grasshopper 2 canvas with its example files and built-in help. Screenshot: McNeel, Rhino forum
Some habits will need relearning. Rutten renamed components for consistency, so List Item is now Item From Index and Domain is now Interval, the term Rhino uses. He admits the List Item change "does trip me up every time I need this component", and searching for "Domain" still finds the Interval components. The middle mouse menu will return at some point, and the Preferences window has not been written yet.
Grasshopper 2 component panels with Interval and Item From Index. Screenshot: McNeel, Rhino forum
Data Trees, Meta Data and the New Data Model
McNeel writes that in GH2 "Data trees have been redesigned", and two ideas stand out for architects.
Data modifiers in every parameter
In Grasshopper 1, flatten, graft and simplify are toggles on inputs and outputs, and most other tree operations need their own component. In GH2 every parameter carries thirteen data modifiers, so "flattening, grafting, sorting, and cleaning happen where the data already is instead of needing a component each." If your facade definitions have a Clean Tree or Sort List component every few steps, this could remove many of them.
Meta data on every item
Every item in GH2 can carry meta data, so you can attach names, values and tags to your data and filter, sort or assign by them further down the definition. McNeel's description of the problem it solves is "shuttling parallel trees around to keep track of what's what". Picture facade panels that carry their floor, orientation and type with them instead of living in three matching trees. Japhy also points to "Transformable MetaData that can go with your transforms". Rutten has planned this for a long time, writing in 2015 that "Grasshopper2 trees will support metadata dictionaries for all individual items".
A Grasshopper 2 example that splits one list into a tree with three branches. Screenshot: McNeel, Rhino forum
The good news is visible above. Data is still organized in branches with paths such as {0}, {1} and {2}, so if you understand data trees in GH1, you already have the foundation for GH2. If you do not yet, our Mastering Data Trees for Paneling mini course is a practical place to start.
Loops, Shout and Listen, and Other New Tools
In GH1, loops usually mean a plugin such as Anemone. In GH2 a cluster can feed its own output back into its input, with a Loop Repeats pin setting the number of iterations, "built in, no add-on required". A running solution can also be cancelled, so an accidental slider nudge no longer means waiting out the solve.
Shout publishes a named value, and any parameter expression downstream can read it by name, with no wire across the canvas. Move the slider and everything listening updates. Japhy says the shout and listen workflow "gives the potential to be more modular".
Shout and Listen pass a named value without a wire. Screenshot: McNeel, Rhino forum
Wires change too. Japhy explains that GH2 wires are "fundamentally different" and "more data aware". If you used to hide wires in GH1, the GH2 answer is Split Wire, which turns a connection into a Shout and Listen pair. The wire menu also has Navigate To Start and Navigate To End.
The Grasshopper 2 wire menu, with Split Wire. Screenshot: McNeel, Rhino forum
Display rules set preview color and visibility per object without baking, driven by meta data. For code, GH2 has C# and Python 3 script components on the new script editor.
Is Grasshopper 2 Faster Than Grasshopper 1?
McNeel says GH2 "computes across your cores" and that a running solution can be cancelled. The announcement gives no benchmark numbers, so test speed on your own definitions. Some beta testers report that the canvas feels slow with large definitions, and Japhy replied that the settings used to speed this up in GH1, such as turning off autosave, "haven't been fully developed in GH2 yet".
Will Your Grasshopper 1 Plugins Work in Grasshopper 2?
No. GH1 plugins do not load in GH2, and Rutten explains why. "The GH1 and GH2 apis are not compatible. They are similar on a conceptual level, but that's where it ends." Every plugin needs its own GH2 build.
Some have started. McNeel's Dale Fugier announced that Vectorize now supports GH2, and Robots in Architecture brought its experimental PRC robot plugin to GH2 as "a nearly 1:1 translation of the GH1 plugin". For Kangaroo, Daniel Piker wrote in 2022 that "the plan is to have an updated version included as part of GH2".
For the plugins most architects rely on, such as Ladybug, Kangaroo and Karamba3D, plan on staying in GH1 until their developers ship GH2 versions. Our list of the best Grasshopper plugins for architects is a good checklist. Japhy says that for computational drafting "GH1 is more suited, due to plugin availability and the Model Object workflow", and that it is "safe to assume both will be in Rhino for the foreseeable future".
Can Grasshopper 2 Open Your Grasshopper 1 Files?
Yes, with limits. Rutten explains that GH2 "is capable of hosting GH1 components in its files", so you can open a .gh or .ghx file or drag GH1 components onto the GH2 canvas. GH2 runs GH1 in the background to make that work. Rutten calls this "a bit of a hack", and components with special UI do not make it across.
The trip is one way. Opening a .ghx file creates a GH2 document that "attempts to mimic the behaviour" of the original, GH2 saves its own .ghz files, and you cannot export back to .ghx. In 2024 Rutten also wrote that auto-upgraders converting GH1 components to GH2 equivalents would keep being added, but would "never be a perfect conversion".
Converting definitions with RhinoAI
McNeel's RhinoAI announcement on September 30, 2026 lists GH1 and GH2 tooling and adds "You can even use this to convert GH1 scripts to GH2." According to the RhinoAI documentation, the assistant opens your GH1 definition, rebuilds it on a GH2 canvas and solves both to compare outputs. The same page warns that names and parameter types "don't always line up one-to-one", that plugin components without a GH2 build should be flagged and skipped, and suggests asking for a short "these need human eyes" list.
Grasshopper 1 vs Grasshopper 2 Side by Side
| Topic | Grasshopper 1 | Grasshopper 2 |
|---|---|---|
| Status | Production version in Rhino 8, also in the Rhino 9 beta | Beta in the Rhino BETA, label removed with the Rhino 9 release |
| Foundation | Original architecture, extended for over fifteen years | Ground-up rewrite with a new solver, data model and interface |
| Data | Data trees, most tree operations as separate components | Redesigned trees, thirteen modifiers in every parameter, meta data on every item |
| Iteration | Needs a plugin such as Anemone | Native looping clusters |
| Solver | Original solver | Computes across your cores, can be cancelled |
| Values without wires | Hidden wires or plugins | Built-in Shout and Listen |
| Help | Tooltips and online resources | Built-in documentation, 120+ examples, 300+ term glossary |
| Plugins | Large existing ecosystem | GH1 plugins do not load, SDK still evolving |
| Files | .gh and .ghx | .ghz, opens .gh and .ghx, cannot export to .ghx |
| Best for today | Production and plugin-based work | Learning, testing and feedback |
What to Do Now
Here is how I would handle the transition if you use Grasshopper 1 every day:
- Keep production in Grasshopper 1. McNeel says so directly, and your plugins only run there.
- Install the Rhino BETA and open GH2 next to GH1. They run side by side, so trying GH2 puts nothing at risk. Start by pulling apart the built-in examples.
- Rebuild one small definition. McNeel suggests you "Rebuild one of your small GH1 definitions in GH2 and see what the new data model does for it." Pick something without plugins, such as an attractor wall.
- Do not convert live projects. Keep the original .gh file and treat any GH2 version as a copy.
- List the plugins you depend on. A workflow built on Ladybug, Kangaroo or Karamba3D waits until those plugins ship GH2 builds.
- Report what breaks. McNeel says bug reports and opinions are what the beta is for.
So the right moment to switch depends on the project. A definition with no plugins can move once GH2 leaves beta, and the rest moves with its plugins.
What to Watch at Rhino World 2026
Rhino World 2026 runs from October 21 to 23 near Barcelona. McNeel promises "exclusive, insider information on the future Rhino and Grasshopper roadmap", and the agenda has separate Grasshopper 1 and Grasshopper 2 talks by McNeel's Brian Gillespie on the second day. I would listen for:
- A date or target for Rhino 9, since GH2 leaves beta with it.
- News on the GH2 SDK, the step McNeel puts before GH2 1.0.
- Which major plugins commit to GH2.
- Progress on converting GH1 definitions, through auto-upgraders or RhinoAI.
Learn Grasshopper Now and Carry It into Grasshopper 2
If you are wondering whether to wait for Grasshopper 2 before learning Grasshopper, do not wait. GH2 keeps the same canvas of components, wires and parameters, and data still flows through lists and trees with paths. Those concepts carry over, even where component names change.
Our Grasshopper Complete Course teaches them in Grasshopper 1, the version you will use in production for now. It covers the logic and math behind Grasshopper, more than 500 components explained through practical examples, and everything about data trees and data structure.
Frequently Asked Questions
Is Grasshopper 2 released?
Not as a final version. It is a beta inside the Rhino BETA. McNeel says the beta label will be removed with the Rhino 9 release, which has no fixed date yet.
Can I use Grasshopper 2 in Rhino 8?
Not in a useful way. Rutten says GH2 is only really available in the Rhino 9 WIP and BETA, and the old Rhino 8 alpha is years out of date. You need a Rhino 8 license to run the Rhino BETA.
Do Grasshopper 1 plugins work in Grasshopper 2?
No. The two APIs are not compatible, so each developer has to release a GH2 version, and the GH2 SDK is still evolving.
Can Grasshopper 2 open my .gh files?
Yes, by running GH1 in the background, but McNeel does not recommend it for real work, and you cannot export back to .ghx. RhinoAI can help rebuild a definition with native GH2 components.
Should I learn Grasshopper 1 or Grasshopper 2 in 2026?
Learn Grasshopper 1 for work and explore Grasshopper 2 alongside it. GH1 is what McNeel recommends for production, and the core concepts of components, wires and data trees carry over.
Related Resources
Grasshopper Complete Course
Give your architectural skills a boost with the Grasshopper Complete Course. Get over 50 hours of comprehensive Grasshopper training tailored for architects. Learn to generate and iterate designs faster. Click below for more information and streamline your workflows!
