ConditioningToBase64

A CONDITIONING object in ComfyUI is opaque - it's just a wire between nodes, and there's no normal way to see what's actually inside it or get it out of the graph. ConditioningToBase64 fixes that by serializing whatever conditioning you feed it into a base64-encoded string and printing it directly in the UI, the same way a Show Text or Preview node does. You probably found this node because it showed up in a workflow someone shared for debugging, or because you're trying to move a conditioning outside of ComfyUI entirely.

How it works

It's an output node - is_output_node: true - so it doesn't need a downstream connection to do something useful; queue it and the encoded string displays in the node itself. Under the hood it's serializing the conditioning tensor and its metadata into base64 text, which is a way to represent binary data as a safe, copy-pasteable string.

The inputs and outputs that matter

• conditioning (CONDITIONING) - the only input, required. Whatever's wired in gets serialized as-is.

Output: string (STRING, a list) - the base64-encoded representation. It's a list because a conditioning can contain multiple entries (for example, from a batched conditioning), and each one gets its own string in the output.

The practical use case is narrower than it sounds. Most of the time you don't need to look inside a conditioning - you just trust the graph and judge the output image. This node earns its place when you're actually debugging: confirming that a node upstream (say, one of this pack's own conditioning-editing nodes) genuinely changed something rather than silently passing the input through unmodified, or when you're building tooling around ComfyUI and need conditioning data to leave the graph as plain text rather than as an in-memory Python object that only exists for the duration of a queue.

How to install it

Via ComfyUI Manager, search "RES4LYF". Or:

cd ComfyUI/custom_nodes
git clone https://github.com/ClownsharkBatwing/RES4LYF/
cd RES4LYF
pip install -r requirements.txt

then restart.

Common issues & troubleshooting

Don't expect to read your prompt back out of it. The output is an opaque blob - long, unstructured, not remotely human-readable. This is for machine round-tripping (confirming a conditioning changed between two points in a graph, or moving it somewhere outside ComfyUI) or basic "did this actually produce something" debugging, not for inspecting prompt content by eye.

Multiple strings in the output usually means a batched conditioning went in. If you were expecting one string and got several, check whether the conditioning feeding this node is itself a batch (from something like this pack's ConditioningBatch4/ConditioningBatch8) rather than a single conditioning.

There's no companion "Base64ToConditioning" node in this pack - if your goal is to round-trip a conditioning back into a usable form later, this node alone won't get you there; it's a one-way inspection/export tool as it ships.