Blender Input String Multiline

The single most useful node in the pack for most people, honestly. When you're working a shot in Blender and want to iterate on the prompt, you need room to read what you're writing - and BlenderInputStringMultiline is the multiline text box that ComfyUI-Blender puts on its Blender panel. A prompt crammed into a single line is a chore; a proper multi-line box you can actually scan is the difference between tweaking a prompt and fighting it.

Like BlenderInputString, it subclasses ComfyUI's built-in multiline string primitive and outputs its value straight through in a ComfyUI-only graph. The extra inputs configure the box the Blender add-on renders. This is the one to use for positive and negative prompts, tags blocks, or any string longer than a filename.

Inputs and outputs

• value - the string the node outputs. This is what you paste into your CLIP Text Encode.
• default - the starting text when the workflow loads. Put your baseline prompt here so every new import of the workflow starts from a known place.
• format_path - same toggle as the single-line version: if the string is a file path, it gets normalized to the OS where ComfyUI runs. For a prompt, leave it off - it does nothing useful there.
• order - panel position, lower first.

Optional group input for nesting inside a Blender Input Group box. Output is a single STRING.

Installing it

Same as the whole pack. ComfyUI side, ComfyUI Manager → search "ComfyUI-Blender", or:

cd ComfyUI/custom_nodes
git clone https://github.com/alexisrolland/ComfyUI-Blender

Restart ComfyUI. No extra Python dependencies, but you need a current ComfyUI - the pack is on the schema v3 custom-node system and the README warns older versions won't load it. The Blender add-on is a separate ZIP from the latest release, installed via Edit > Preferences > Add-ons > Install from Disk.

Where people get burned

The whole pack's gotcha applies hardest here: the box only appears after you export in API format and import into the add-on, and the node's title becomes the label above the box - call it "Positive Prompt", not "text". People also forget that this node and the single-line version are different classes; if your prompt keeps getting truncated to one line in Blender, you grabbed the wrong one. And a prompt-engineering reminder that's easy to lose mid-shot: the default value is a live starting point, so every workflow import re-seeds your box with whatever you hard-coded. If your prompt edits never survive a reload, that's expected - set default to your template and treat the box as scratch space. Same-GPU VRAM note as always: the box is free, the generation it feeds is what eats memory.