Get VAE Name (Texturaizer)

The simplest node in the whole pack, and there's not much to dress it up with: it retrieves the VAE filename from the directory you point it at, or from Texturaizer's global directory if you don't specify one. One job, one output that matters.

How it works

Like the rest of the Texturaizer "Get" family, it either reads a JSON file off disk (via directory_optional, or the addon's configured global directory if that's left blank) or accepts an already-parsed dictionary through data_optional - the second path is how you avoid re-reading the same export file once per node when you've got a dozen of these getters in one graph. Whichever way the data arrives, this node pulls exactly one field out of it: the VAE name Blender's export specified for the current render.

The outputs that matter

• vae_name - the VAE filename, straight from the tooltip. It's typed as a wildcard on the node's schema, which in practice just means it plugs into whatever loader expects a VAE filename string - most commonly a Load VAE node, feeding its output into your KSampler's decode step or a VAE Decode node further downstream.
• data_hash - the same debug-only fingerprint every getter in this pack outputs. Useful for confirming a downstream node actually picked up new data after a change in Blender; not something you wire into your generation graph.

That's the entire node. If you're wondering why a one-output node gets its own class instead of being folded into Get Model Name - it's the same reason Get Clip Model Names is separate: VAE, CLIP and the diffusion model can each be swapped independently on a split-loading setup, so Texturaizer keeps a dedicated getter per model component rather than bundling everything behind one giant output list.

Installing it

ComfyUI Manager → search Texturaizer → Install → restart, or clone it directly:

cd ComfyUI/custom_nodes
git clone https://github.com/LatentSpaceDirective/ComfyUI-Texturaizer

Restart ComfyUI after either method. No extra dependencies flagged in the README, and no VAE file ships with the pack - this node reports a name, your ComfyUI/models/vae folder has to actually contain a file that matches it.

Where people get burned

Because this node returns a bare string rather than validating anything, a typo or a stale entry in Blender's export just shows up as "VAE not found" downstream, several nodes away from where the actual problem is - worth remembering when you're debugging a chain that starts here. And the standing caveat for this whole pack applies just as much to the smallest node in it: without the Blender addon actually running and writing an export, directory_optional left blank points this node at a "global directory" that has nothing in it. If you're assembling a workflow entirely inside ComfyUI with no Blender involved, a plain Load VAE node with the filename typed in directly will get you there faster than trying to feed this one manually constructed data.