Connect ComfyUI
Connect ComfyUI
Connect Studio to the ComfyUI engine you want to use, then confirm that Studio can see it.
Before you start
You need either a supported Studio-managed ComfyUI installation or the URL of an engine you operate. A folder path lets Studio inspect local files and launch settings. The URL tells Studio where to send ComfyUI requests.
Choose the connection
Studio-managed local engine
Use one-click setup when you want Studio to install the supported ComfyUI tooling and launch it for this machine. Confirm the detected folder and launch target before changing arguments.
Existing local installation
Point Studio at the folder that contains the ComfyUI entrypoint, then enter only the launch arguments your installation needs. Keep model and custom-node locations consistent with that installation.
Remote engine
Enter the direct ComfyUI URL in Advanced settings. The remote service must be reachable from the machine running Studio, and Studio must be able to read its available nodes, queue, job history, and media. Protect the connection with the host’s authentication and network controls.
Verify the connection
- Open Settings → Setup → ComfyUI.
- Start or connect the selected engine.
- Wait for Studio to report that ComfyUI is connected.
- Open Pipes and revalidate a known workflow.
- Confirm that model and node-backed controls can load their runtime options.
Studio uses the active ComfyUI connection to validate workflows, load available choices, start generations, follow progress, read history, and transfer media. Project folders and the ComfyUI input folder are separate: projects hold your Studio files, while the engine input folder receives images or clips a workflow must read.
<!-- /guide:excerpt -->What Studio checks
A green connection means Studio can reach ComfyUI. Each Pipe still needs a supported workflow, its required models and nodes, valid inputs, and a selected project folder.
If the connection works but a Pipe does not
| What you see | Meaning | Next move |
|---|---|---|
| Engine unavailable | Network, process, URL, or authentication | Inspect engine startup and reachability |
| Engine connected; Pipe blocked | Workflow, model, or node issue | Open Install Missing Models and Nodes |
| Runtime options empty | Object information or model-folder mismatch | Revalidate and inspect Models/Nodes |
| Generate starts; no image or clip appears | Queue, ComfyUI error, history, or save folder | Use Troubleshooting |