EmAySee Image Passthrough

This node takes an image in and returns the exact same image out. No processing, no resizing, no color correction - a literal pass-through. It exists so that input_image and output_image are distinct named ports you can work with in the graph. And yes, that's a real use case: ComfyUI lets you rename connection labels, but some people find it easier to drop in a node whose input and output are clearly named than to fight the renamer or keep track of which wire is which in a busy graph.

How it works

The function body is return (input_image,). That's it. The class docstring in the source is refreshingly honest about it: "A simple passthrough node for images... Useful for renaming input connections in the workflow." It takes an IMAGE tensor and returns it untouched - the same object, no copies. No caching tricks, no side effects, nothing to configure.

Inputs and outputs

• input_image (IMAGE) - any image tensor.

Output: output_image (IMAGE) - identical to the input.

Where it's actually useful

Three honest cases:

• Organization. In a sprawling graph, a named passthrough can act as a labeled segment break - "this is where the image leaves the sampling section and enters the post section" - without changing data.
• Renaming. If you want a cleaner label on a wire than the source node's output name, route through this and the new output name is right there.
• Placeholder. Building a workflow top-down, you can drop a passthrough where a real node will go later, then replace it without rewiring the downstream connections.

Install

Part of ComfyUI_EmAySee_CustomNodes. ComfyUI Manager → search "EmAySee" → install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/EmAySee/ComfyUI_EmAySee_CustomNodes

No dependencies, no models, no requirements file - this node can't install anything because it does nothing. Restart and you'll see the pack's "SPECTRE v5.0" banner in the console.

The honest take

This is the pack's most "why does this exist" node, and the honest answer is: it's a habit from someone who builds lots of graph automation, where named waypoints genuinely help. If you never feel the need for a labeled no-op, skip it - ComfyUI's own reroute node does the same job with less ceremony. But if you've ever squinted at a wall of wires trying to remember which strand is which, you'll get why it's here. It won't fix your graph's performance (it can't - it does nothing), but it can fix your graph's readability.