← All ideas
  • Published 18 Dec 2025

Rename “Shape Key” to “Blendshape” for Industry Alignment

Hi Blender community,

I’ll venture to propose renaming Blender’s “Shape Key” feature to “Blendshape.” This would align Blender with established industry terminology and ease communication of core concepts between DCC users.

“Blendshape” is used in most major 3D applications, including Maya, Houdini, Unreal, Unity, Godot, and Cascadeur. Using a different term in Blender introduces a recurring discrepancy for users moving between tools or learning from external material, where “shape key” and “blendshape” are sometimes used interchangeably. Conversations online illustrate this confusion (e.g., Godot forum and Right-Click Select ), as well as product names (e.g. 1 , 2 , 3 ).

Even within the Blender community, the feature is sometimes referred to as “Shape Key” and sometimes as “Blendshape”; and the Blender manual notes that “shape keys may be called ‘blend shapes’” in other terminology. Adopting a single term would make the feature clearer and more consistent to talk about.

This could be introduced gradually through dual-labeling in the UI and tooltips (e.g., “Blendshape (Shape Key)”) to ease the transition for existing users. On the Python side, shape_keys could remain as an alias to avoid breaking scripts or add-ons, while blendshapes is introduced as the preferred identifier.

The intent is partly to deconvolute the global pool of 3D terminology across applications and partly to make Blender more approachable for both newcomers to 3D and users coming from other DCC tools.

50%

Development Status: Open

Upvote 4 Downvote 4
hcederblad
18 Dec 2025

2 Comments

thorn

People will continue to call them shape keys. Every tutorial video that exists, will continue to discuss Shape Keys. Then you'll have a group of newbies asking "where's the shape key button? Why was this removed?"

I wouldn't be surprised if somewhere in the python API there are code lines that are called "shapekey". If so, those all have to be renamed too. Which will break the API again, and make all the third-party devs have to redo all their addons, again.

I still call "empties" a "null object", because that's what it was called in everything else I've used. People can either use their blues clues to figure out what I mean when I say "use a null", or ask. Or just wonder. Efforts to rename a feature with a decade or two of self-precedence, are well-intended but don't usually obseve the scope of the ramifications.

1
Lauloque

You mean locator, right? ... right?

1