Nodes/ComfyUI-N-Nodes/CLIP Text Encode Advanced [πŸ…-πŸ…’πŸ…€πŸ…˜πŸ…£πŸ…”]
ComfyUI Node Runs on cloud

CLIP Text Encode Advanced [πŸ…-πŸ…’πŸ…€πŸ…˜πŸ…£πŸ…”]

A1111-style prompt styles, straight in the graph β€” and it's still buggy

By Nuked88Β·Created 3 years agoΒ·Updated 2 years agoΒ· 237
CLIP Text Encode Advanced [πŸ…-πŸ…’πŸ…€πŸ…˜πŸ…£πŸ…”]
  • clip
  • positive
  • negative
β—„stylesβ–Ύβ–Ί
β—„positive_promptβ€”β–Ί
β—„negative_promptβ€”β–Ί

The pitch here is genuinely useful if you came from Automatic1111: a single node that combines a style preset with your own positive and negative prompts, and outputs both conditionings at once - no separate CLIP Text Encode for positive and another for negative. The catch, straight from the pack's own README: this one is explicitly marked experimental and "still has a lot of bugs." Worth knowing before you build a whole workflow around it.

How it works

It reads from a styles file - n-styles.csv, which lives in your ComfyUI/styles folder - following the same CSV format A1111's styles.csv uses. Pick a style, and the node pulls that style's predefined positive and negative text and combines it with whatever you typed into positive_prompt and negative_prompt. The result gets run through CLIP text encoding the normal way, and you get back two ready-to-use conditionings instead of building the combination yourself with a separate prompt-concatenation step.

The inputs and outputs that matter

clip is your standard CLIP model input, same as any text encoder. positive_prompt and negative_prompt are multiline text fields for your own prompt content. styles is a dropdown populated from your n-styles.csv file - which means the list you actually see depends entirely on what you've put in that file; it's not a fixed set of choices baked into the node.

Two outputs: positive and negative, both CONDITIONING - wire them straight into your sampler the same way you would the outputs of two separate standard CLIP Text Encode nodes.

Installing the pack and setting up styles

  • ComfyUI Manager - search "ComfyUI-N-Nodes," install, restart.
  • Manual - cd ComfyUI/custom_nodes && git clone https://github.com/Nuked88/ComfyUI-N-Nodes.git, then restart ComfyUI.

This node specifically needs one more thing: an n-styles.csv file in your ComfyUI/styles directory, in the same format as A1111's own styles file (name, prompt, negative_prompt columns). If you're migrating from A1111, you can often reuse your existing styles.csv directly by copying it in under the new filename. Without that file present, the styles dropdown has nothing to populate itself from.

Common issues & troubleshooting

The styles dropdown only shows one option, or nothing useful. Check that n-styles.csv actually exists in ComfyUI/styles and is populated - an empty or missing file means the node has nothing to offer beyond whatever placeholder entry it falls back to.

Output doesn't seem to reflect the style you picked, or behaves oddly. This is the exact behavior the README warns about - the node is labeled experimental with known bugs, and style application not landing the way you'd expect is a plausible symptom of that rather than something you're doing wrong. If it's not working reliably, falling back to a separate style-lookup node plus two standard CLIP Text Encode nodes is the safer, more predictable path until this one matures.

Uninstalling and the styles file lingers. If you ever remove the pack, the README's own uninstall notes call out n-styles.csv and its .backup file in ComfyUI/styles as files that don't get cleaned up automatically - delete them by hand if you want a clean slate.

CategoryN-Suite/Experimental

Inputs (4)

NameTypeDefaultDescription
stylesCOMBO1 options: NAI
positive_promptSTRINGβ€”
negative_promptSTRINGβ€”
clipCLIPβ€”

Outputs (2)

NameTypeDescription
positiveCONDITIONINGβ€”
negativeCONDITIONINGβ€”