Get Kontext Data (Texturaizer)

Flux Kontext works differently from most editing approaches - instead of injecting an embedding from a reference image, it concatenates the reference image directly into the model's context alongside your generation, so the model sees both at once and edits with that reference in view rather than just "in mind." This node retrieves the extra reference image Blender configured for a Kontext-driven render, plus whether it should be used at all.

Why Kontext specifically gets a getter

Kontext started the instruction-editing category - "change her dress to blue," "remove the watermark," that kind of prompt-driven edit with a reference image alongside it - and for a Blender-to-ComfyUI pipeline built around per-object and per-material control, that's a genuinely useful capability: an artist picks a reference in Blender's panel, and this node is how that choice reaches ComfyUI without manual re-wiring. Worth knowing going in: Qwen-Image-Edit has substantially overtaken Kontext as the community's default for this kind of instruction editing (outnumbering it roughly 4-to-1 in recent discussion), mostly on licensing grounds - Kontext's license restricts NSFW derivatives - rather than because it stopped working. If your workflow is built around Kontext specifically, this node is exactly what you want; if you're choosing an editing model from scratch today, it's worth knowing Kontext isn't the only or even the most-discussed option anymore.

How it works

Same read as every other Texturaizer getter - directory_optional, the addon's global directory if left blank, or an already-loaded dictionary via data_optional. What it pulls out here is narrow and specific: one extra reference image, and a flag saying whether to actually use it.

The outputs that matter

• kontext_extra_image - the reference image itself. Wire it into whatever your Kontext workflow uses as the reference/context image input alongside your main conditioning.
• use_extra_image - a boolean. Off means don't use the reference at all, even if one is present in the data - check this before assuming a missing edit result is an image problem.
• data_hash - the standard debug-only fingerprint the rest of the pack's getters output too.

Installing it

ComfyUI Manager → search Texturaizer → Install → restart, or:

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

then restart ComfyUI. This node only reports the image and the flag - the actual Flux Kontext checkpoint and whatever Kontext-specific sampling nodes your workflow uses are a separate install and a separate, fairly large model download, not something this pack provides.

Where people get burned

use_extra_image being off is the most likely reason a Kontext-driven edit "ignores" the reference you picked in Blender - check it before assuming the image itself failed to export. And because Kontext Dev is guidance-distilled from the proprietary Pro/Max tiers, it's noticeably behind them on consistency even when everything here is wired correctly - if results feel weaker than what you've seen in Kontext showcase posts online, some of that gap is simply which tier those posts were running, not a misconfiguration on your end.