We’re excited to announce that the Next-Gen Speckle Blender Connector has officially hit stable release with version 3.2.0!
After two months of open beta testing and invaluable community feedback, our completely rewritten Blender connector is now production-ready and brings Blender fully in line with the capabilities of our other connectors like Rhino, Revit and Archicad.
What’s New in 3.2.0
This stable release represents a complete rewrite with our next-generation connector architecture, bringing several key improvements:
Model cards are in
When you publish or load a model, corresponding model card is created. From these model cards, you can:
- Publish a new version of the same model
- Overwrite what gets published (e.g. make a different selection and publish that instead)
- Load a new version of the loaded model
- Overwrite what gets loaded in Blender (e.g. pick a different version)
- Select published/loaded objects
What happens when you load a new version of the same model? Each loaded model comes with its own collection structure. That collection structure and all the loaded objects get removed, and gets created again with the new collection structure + objects.
Blender models looking good in the viewer
We had a known limitation of legacy Blender connector: when you publish a Blender model, famous Blender cube, to Speckle, hard edges wouldn’t look good.
With the next-gen Blender connector, we’ve resolved that issue. Now, vertex normals are included so Blender models looks as good as how they look in Blender.
Loading Blocks options
When blocks from other CAD apps, (like Rhino, SketchUp etc.), now you have the option for controlling how they are created in Blender.
Linked Duplicates: Creates multiple instances of the same block that share identical mesh data in Blender’s memory.
Collection Instances: Converts each block into a Blender collection instance, which is preserving the hierarchical structure of the blocks.
Applying Modifiers
Modifiers, we all love them. They are an inseparable part of Blender. Blender connector now has the option for applying modifiers on publish so your models look identical to how they are in Blender.
Sign in within connector
If this is your first time using Blender connector, you now can sign in to your Speckle account directly within Blender.
The stable connector supports Blender 4.2, 4.3, and 4.4, ensuring compatibility with the latest Blender releases.
Migration from Legacy (V2) Connector
Ready to make the switch? Here’s what you need to know:
- Download and install the Next-Gen Blender connector from connectors page.
- Uninstall the legacy V2 connector (it will remain available but won’t receive updates)
Note that some workflows from the legacy connector are no longer supported
We encourage all users to migrate to the stable 3.2.0 release and let us know if you discover any missing features.
Thank You, Beta Community! 
A huge thanks to our open beta testers who provided crucial feedback over the past two months. Your input directly shaped the features we prioritized and helped us achieve true feature parity with our other connectors.
What’s Next?
Property Support
We’re thinking on adding support for loading properties from other models and publishing custom properties from Blender. This could open up powerful workflows for data-driven visualization and parametric animations.
Community Poll: We’d love to hear from you! Would property support be valuable for your workflows?
- YAY
- NAY
- IDK
Tell us more: Drop a comment below and let us know:
- What types of properties would you want to load from other applications into Blender?
- How would you use custom Blender properties in your collaborative workflows?
- Any specific use cases or scenarios where this would be a game-changer?
Your input helps us prioritize what to build next!
As always, the Blender connector remains open source, continuing our commitment to transparent, community-driven development.
Get Started Today
Download the Next-Gen Blender Connector
Try it out and let us know what you think is missing - your feedback continues to drive our development priorities.