← All ideas
  • Published 22 Feb 2026

Expose the Font option as a new socket type

With larger trees and multiple String to Curve nodes being used, making changes to the font is cumbersome. Moreover, conditionally choosing a font requires what i consider a workaround that can potentially get cluttered.

Having the Font property be exposed as a socket with accompanying constant input node would make things easier, a font could be defined in the modifiers tab instead of hunting for the specific node. It could also allow defining conditional fonts more easily.

Attached is an example as a visual aid (tho it probably doesnt add much)

Essentially, it follows the same logic as, for example, the Image or Object node, even tho there are not that many native node types that even have a font setting.

example.jpg

(The image also shows sockets for the remaining properties of the String to Curves node. This is another idea about exposing other types of node settings as sockets, in this case the menus. It also applies to some other nodes, GN, CN or SN, and socket types (booleans in shader nodes for example) but thats not what this proposal is about.)

100%

Development Status: Done

Upvote 1 Downvote 0 blender/pulls/151544
snens
22 Feb 2026

4 Comments

Enord

You get your wish! The font socket was merged a while ago and will be included in 5.1, along with every other input in the node as a socket.

1
snens Author

oh damn, good to know. looking at it its exactly what came to mind. better check the devlogs next time

samueloates

I think there will also be other data block sockets in 5.1 or 5.2, such as sound, scene, etc. They might not be usable in the built-in node trees, though (at least not yet)