CLIPTextEncode with BREAK syntax:
CLIPTextEncodeWithBreak turns a prompt with separate sections into conditioning for image generation. It divides the prompt wherever it finds the standalone, uppercase word BREAK, encodes each section separately, then concatenates the results in their original order. This gives you a way to organize a longer prompt into distinct sections while producing a single conditioning result. It does not, by itself, assign different weights to those sections or guarantee how strongly each idea will appear in the image.
CLIPTextEncode with BREAK syntax Input Parameters:
text
The prompt to encode. This is a required, multiline string. Write ordinary prompt text to encode it as one section, or place the standalone, uppercase word BREAK between sections, such as portrait of a traveler BREAK snowy mountain background. Spaces around BREAK are optional. Each section is encoded separately before the results are concatenated, so the placement of each separator changes how the prompt is processed. No minimum length, maximum length, or default value is specified in the node source. Consecutive separators, or a separator at the beginning or end, create empty sections; avoid them unless you have confirmed that your connected encoder handles empty text as intended.
clip
The required CLIP object used to encode every section of the prompt. Connect the CLIP output from the model or CLIP loader you are using for the workflow. The same connected CLIP object processes every section, so this node does not provide a way to select a different encoder for each section. No default value or selectable options are specified in the node source.
CLIPTextEncode with BREAK syntax Output Parameters:
conditioning
The single CONDITIONING result produced from the prompt. Without BREAK, it is the result of encoding the full text once. With one or more separators, it is the result of encoding each section separately and concatenating those results in order. Connect it to a workflow component that accepts conditioning, such as the appropriate conditioning input of a sampler. It is one output socket, not a separate output for each prompt section.
CLIPTextEncode with BREAK syntax Usage Tips:
- Put
BREAKon its own between meaningful prompt sections. For example,close-up portrait, soft lighting BREAK garden background, morning mistcreates two sections in that order. - Use uppercase
BREAKexactly. The source splits on that case-sensitive, standalone word; lowercasebreakand the letters inside a longer word do not serve as separators. - Keep the CLIP connection consistent with the model setup in your workflow. Every section is encoded through that same connection.
- Remove accidental leading, trailing, or repeated
BREAKseparators if you see unexpected results. They can introduce empty sections rather than additional visual instructions. - Compare a prompt with and without a separator when refining an image. The node changes the encoding and concatenation process, but the source does not establish that adding more separators will improve image quality.
CLIPTextEncode with BREAK syntax Common Errors and Solutions:
Missing required input: text
- Explanation: The node requires a
textvalue. The exact validation message depends on the host application; no error string is defined in this node’s source. - Solution: Enter prompt text in the multiline field or connect a valid string source.
Missing required input: clip
- Explanation: The node requires a
CLIPconnection to encode the prompt. The exact validation message depends on the host application. - Solution: Connect a compatible CLIP output from the model or CLIP loader used by your workflow.
Type mismatch on the clip connection
- Explanation: A connection that does not provide a
CLIPobject cannot satisfy this input. This node’s source does not specify the host’s exact type-mismatch message. - Solution: Disconnect the incompatible output and connect a socket labeled
CLIP.
BREAK does not split the prompt
- Explanation: The separator must be the standalone, uppercase word
BREAK. For example,breakdoes not match because the split is case-sensitive. - Solution: Write
BREAKas a separate word between the sections you want to encode individually.
Unexpected result after an empty prompt section
- Explanation: Starting or ending the text with
BREAK, or using repeated separators, can pass an empty section to the connected encoder. Whether that causes an error or an unexpected result depends on the encoder; this node defines no specific message for it. - Solution: Give each section meaningful text and remove unintended extra separators.
Encoding or concatenation fails
- Explanation: This node delegates encoding and concatenation to other nodes. An error from those operations may appear while CLIPTextEncodeWithBreak runs, but the supplied source does not define or expose their exact error messages.
- Solution: Check the full error shown by your application, confirm that the connected CLIP works with a simple prompt, and test one prompt section at a time to isolate the section that triggers the failure.
