Blender at
Volkswagen Group

"We address specific challenges in applying Blender to technical workflows and present a custom-developed add-on as a targeted solution."

Enterprise software adoption stories tend to follow a familiar pattern: a tool is evaluated, piloted in a low-stakes context, gradually expanded, and eventually either institutionalised or quietly dropped. What makes the Volkswagen Group's relationship with Blender interesting is that it doesn't fit this pattern cleanly. Blender is open-source in an environment built around proprietary CAD and visualisation tools. It is free in an organisation where software licensing is a line item rather than a constraint. And it is community-developed in a context that typically requires vendor support contracts.

This talk from Blender Conference 2025 presents the honest version of that story. Ali Varol and Alina Schubert, who work with Blender inside the VW Group, describe where it is currently being used, where it creates friction relative to established tools, and how they addressed one specific technical gap — diagnostic shading — by building a custom add-on rather than waiting for a general solution.

What the Talk Covers

• Where Blender currently fits in the VW Group workflow The presentation maps out the specific use cases where Blender has been adopted — not as a replacement for the CAD tools that handle engineering data, but as a visualisation and presentation layer. Understanding which part of a large technical workflow Blender occupies is prerequisite to understanding both why it works and where it struggles.
• Comparing Blender to established automotive visualisation tools The automotive industry has its own established 3D software ecosystem — VRED, KeyShot, ICEM Surf — optimised for specific aspects of vehicle design and review. Varol and Schubert provide a direct comparison of how Blender measures up against these tools in the tasks that matter for their context: material accuracy, render speed, CAD data import and review-ready output.
• Technical challenges specific to automotive workflows Automotive 3D work has requirements that general-purpose software doesn't always anticipate: extremely large polygon counts from CAD imports, strict surface quality standards, lighting setups calibrated to real-world showroom conditions, and material accuracy that can affect design decisions. The talk is specific about where Blender handles these well and where workarounds are currently required.
• The Diagnostic Shading add-on Rather than treating gaps as blockers, the team built a targeted solution: a custom Blender add-on for Diagnostic Shading. Diagnostic shading is a technique used in automotive design to evaluate surface quality — using specific reflective patterns to reveal curvature continuity issues that are invisible under standard lighting. The add-on brings this capability into Blender's viewport, enabling review workflows that previously required a different application.
• Open-source in an enterprise context The talk addresses the structural questions that come with using open-source tools inside a large organisation: how updates are managed, how add-on maintenance is handled, what happens when a needed feature doesn't exist yet, and how the organisation relates to the upstream Blender project. These are questions that anyone bringing Blender into a professional context at scale will eventually face.
• Future potential and where development is needed The presentation closes with an honest assessment of where Blender would need to develop to become more deeply embedded in VW Group workflows — and which of those developments the team considers realistic given Blender's current trajectory. This section is useful both as a roadmap indicator and as a practical guide to Blender's current ceiling in demanding industrial contexts.

Why This Talk Is Worth Watching

Enterprise adoption stories are useful data points precisely because the constraints are different. An independent artist choosing Blender optimises for capability and learning curve. A large organisation optimises for reliability, integration, support and the ability to maintain consistent output across many users over long time periods. When Blender works in that context, the reasons are instructive. When it doesn't, those reasons are equally instructive.

The Diagnostic Shading add-on is also a useful example of a broader pattern: rather than waiting for a feature to appear in core Blender, a team with a specific need built it themselves and made it work within the existing architecture. This is exactly the kind of contribution that the open-source model is supposed to enable, and seeing it happen at enterprise scale is a meaningful signal about where Blender's development model can go.

For anyone working in technical visualisation, product design, or any field where 3D tools need to integrate with engineering data, this presentation offers a rare look at what that integration actually looks like in production.

About the Speakers

Ali Varol and Alina Schubert work within the Volkswagen Group on 3D visualisation and tooling. Their involvement in Blender development and adoption at enterprise scale represents a growing presence of large industrial organisations in the Blender community — bringing both significant use cases and the resources to address them. Their BCON25 presentation was one of the more technically specific talks of the conference, grounded in the particular demands of automotive production.

About Blender Conference 2025

Blender Conference is the annual gathering of the Blender community, held in Amsterdam. All sessions are recorded and released under Creative Commons licensing through the Blender Foundation's PeerTube instance at video.blender.org. More information about BCON25 at conference.blender.org/2025.

#b3d  #BCON25  #blender  #foss  #peertube  #blender3d