Adobe Substance 3D Painter 12.1 Ships With OpenPBR as Default Shader

Adobe has released Substance 3D Painter 12.1, and the headline change is that new projects now use OpenPBR as the default shading model instead of Adobe's own standard shader. The update shipped on 22 June 2026 and also adds Auto Rebake, skew map painting and improved UV unwrapping for hard surface models.
OpenPBR is an open shading standard backed by Adobe, Autodesk and other major players in the 3D and visual effects industry. The idea is straightforward: a material built with OpenPBR should look and behave the same whether it is opened in Substance, another DCC tool, or a game engine, rather than needing to be rebuilt or approximated each time it crosses a pipeline.
That matters more than it might sound for anyone who actually moves assets between tools day to day. Studios routinely build a material in one package, texture it in another, and render or bake it in a third or fourth. Every time a shading model does not match exactly between those tools, an artist has to either accept a slightly different result or spend time manually correcting it. A shared standard removes a whole category of that guesswork.
Adobe is not just switching the default for new work either. It is converting all of its existing Substance 3D Assets library, more than 14,000 materials and decals, over to OpenPBR, so the change applies retroactively to content people already rely on, not only to files created after the update.
The other additions in 12.1 are smaller but genuinely useful for day to day work. Auto Rebake removes a manual step that most texture artists have hit before: forgetting to rebake mesh maps after a small geometry change and only noticing once a bake looks wrong. Skew map painting and the improved hard surface UV unwrapping are aimed squarely at product and hard surface work, where clean, low distortion UVs matter for texture quality.
For studios working across multiple 3D pipelines, this is a practical release rather than a flashy one. OpenPBR as a default is the kind of change that saves time quietly, by removing friction between tools, rather than adding a feature you notice on day one.