From Photoshop

Honest headline before anything else: From Photoshop is a node that can't do anything yet. It's part of Pomfy, a "Photoshop and ComfyUI 2-way sync" pack whose entire README is three lines - and the last one is a warning in caps: THIS PLUGIN IS STILL BEING DEVELOPED, IT DOESN'T WORK YET. The companion Photoshop plugin it depends on isn't even published (the linked repo returns a 404 as of this writing). So if you install it and nothing arrives, you're not broken. There's simply nothing to receive from.

Here's what it's supposed to be when it ships: the "read" half of the roundtrip. You tell it the name of a layer in an open Photoshop document, and it pulls that layer's pixels into your graph as an IMAGE - the same data type every sampler, VAE encoder, and upscaler eats. The idea is to make Photoshop the canvas and ComfyUI the engine. You keep the composition, the text, the layout you actually want in the PSD, then hand the relevant layer to the pipeline for an img2img pass, an upscale, or a targeted inpaint.

That's a genuinely appealing pitch, and it's not hard to see why someone builds it. The community's long-standing gripe is that ComfyUI's graph is where the power lives but there's no canvas to paint on - the KB's ecosystem essay calls the UI "the source of most complaints" about the tool. Photoshop's advantage, as the inpainting literature puts it, is the integrated editing environment: select, mask, fill without leaving the canvas. Nodes like this are the bridge between those two worlds. A1111 had a "send to img2img" Photoshop plugin ages ago; people are still building fresh Photoshop-and-Krita bridges to ComfyUI as of 2026, which tells you the demand is real even if most attempts stay half-finished.

How it's meant to work

ComfyUI and Photoshop don't talk to each other natively - no shared clipboard, no API, nothing. Pomfy's design is that a companion plugin (Pomfy-Plugin) installed inside Photoshop is the bridge. The node on your side calls out to that plugin, the plugin reads the document, and pixels come back into the graph. No API key, no cloud, no model downloads. The plugin repo isn't published yet, so the mechanism is more a plan than a pipeline - but the architecture (local plugin as the socket, node as the socket on the graph side) is the sane one for this job.

The input that matters

The schema is a skeleton, and that's kind of the point: there's exactly one thing you'd set.

• layerName (STRING, required, default "") - the name of the layer to pull. There's no tooltip and no picker, so whatever you type has to match the layer name in the document exactly. Missing or mistyped and the node has nothing to grab.

Output: image (IMAGE) - wire it anywhere a Load Image output plugs in: into a VAE Encode for img2img, into an upscale model, into an IPAdapter, into a ControlNet preprocessor. It's a plain IMAGE, so it's interchangeable with any other image in the graph.

Install

Standard custom-node install. In ComfyUI Manager, search "Pomfy" (the pack title is "Pomfy - Photoshop and ComfyUI 2-way sync") and hit install. Or from the terminal:

cd ComfyUI/custom_nodes
git clone https://github.com/Millyarde/Pomfy

Then restart ComfyUI. There are no heavy dependencies and no model files to download - the README lists none, and the only real dependency is the Photoshop plugin itself.

Troubleshooting (read this before you pull your hair out)

• "Nothing comes through." Expected. The README says the plugin isn't done, and the plugin repo isn't public. Until both halves exist, From Photoshop will never return pixels. This is not a config error.
• git clone fails / Manager can't find it. The repo is currently returning 404, so the clone step may fail outright today. If that happens, the pack is unavailable - that's the state of things, not a network issue on your end.
• Wrong or blank layer name. Once it does work, layerName is the one knob, and a default of "" means an empty string gets sent unless you type something. Match the layer exactly.

Want Photoshop-to-ComfyUI roundtrips today? Look at the Krita-based ComfyUI plugin or the other actively-developed Photoshop bridges instead of betting on Pomfy. This one is a promising scaffold that hasn't shipped yet - worth keeping an eye on, not worth basing a workflow on.