load Image with metadata

Most nodes in ComfyUI produce something you wire onward. This one doesn't - its outputs list is empty. It's marked as an output node, which in ComfyUI terms means it's a terminal step: it does its job as a side effect of running, not by handing data to the next node in the graph. That puts it in the same family as SaveImage or PreviewImage - nodes whose real output isn't a wire, it's whatever gets pushed back through the execution API.

What it's actually for

This pack exists to bridge ComfyUI with the Auto-Photoshop-SD plugin, and the README spells out the mechanism the plugin relies on: you save your ComfyUI workflow in "API Format," the plugin loads that JSON and fires requests at ComfyUI over HTTP. Somewhere in that loop, the finished render has to get handed back to Photoshop so it lands on a new layer. That's this node's job - given a path to an image file, it loads it (metadata and all - A1111/ComfyUI-style PNGs carry the prompt and workflow baked into their chunks) and surfaces it through the API response rather than to a downstream node.

There's a real community report of exactly this handoff going wrong: a user's generation would finish, hit 100%, and the resulting image would simply never appear on a new Photoshop layer - no error, just nothing landing. Whatever's on the far side of this node's output is precisely where that kind of failure lives.

The one input

image_path - a plain string, defaulting to the placeholder text "Hello World!". That default is obviously never meant to survive into a real workflow; treat it as a reminder that you must overwrite it with an actual path before this node does anything useful.

When you'd actually touch this

Almost never, if you're just running ComfyUI workflows the normal way - there's no reason to drop this into a generation graph you're driving from the ComfyUI UI yourself. It earns its keep specifically inside Auto-Photoshop-SD workflow templates, or if you're building your own client against the ComfyUI API and want a stable node to point a finished file at.

Installing it

ComfyUI Manager: search "Comfy-Photoshop-SD", install, restart. By hand:

cd ComfyUI/custom_nodes
git clone https://github.com/AbdullahAlfaraj/Comfy-Photoshop-SD

then restart.

Where people get burned

The path has to resolve on the machine actually running ComfyUI, not the machine running Photoshop - if your ComfyUI instance is remote or containerized (which describes a lot of cloud-hosted ComfyUI setups), a path that's valid on your desktop is meaningless to the server process trying to open it. That mismatch is the leading suspect any time this node "does nothing": the file it's looking for doesn't exist from its own point of view, even though it obviously exists from yours. Second, remember the placeholder default above - if a workflow you inherited from someone else still has "Hello World!" sitting in this field, that's not a real path either.