Load Latent (URL)

This is the actual mechanism behind ComfyUI_NetDist's "remote latents" idea: instead of decoding to an image, sending it across, and re-encoding on the other side, you hand the raw latent tensor between two live ComfyUI instances over HTTP. LoadLatentUrl is the fetching end - it pulls a latent from a URL rather than a local file, which is what lets two separate instances trade latents without you manually copying files between machines.

How it works

Per the README, the intended pattern is: save a latent on the source instance with SaveLatentNumpy, which hands you back the filename it used. String-replace that filename into a template URL pointing at the source instance's own view endpoint:

http://127.0.0.1:8188/view?filename=ComfyUI_00001_.latent&type=output

(swap type=output for type=input if you saved into the input folder instead). LoadLatentUrl on the receiving end fetches from that URL and decodes it into a LATENT.

Unlike LoadLatentNumpy, this doesn't read a pre-existing local file - it's a live HTTP fetch against a running ComfyUI instance's own API, so that source instance has to still be up and the file still has to exist under its output or input folder when this node runs.

The inputs and outputs that matter

• url (STRING) - the full view URL, filename and type parameter included, pointing at the source instance.

Output: LATENT - feed straight into your sampler or wherever the latent needs to go next.

How to install it

Via ComfyUI Manager: search ComfyUI_NetDist. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/city96/ComfyUI_NetDist
pip install requests

Restart ComfyUI. requests is the entire dependency list.

Common issues & troubleshooting

Fetch fails or returns a 404. Double-check the type parameter matches where the latent was actually saved - SaveLatentNumpy's default filename_prefix (latents/ComfyUI) writes to the output folder, so type=output is usually right unless you deliberately redirected it.

Source instance has gone down or the file's been cleared. This node needs the source ComfyUI instance to still be running and the file to still be sitting there - there's no caching or retry, it's a straight fetch at execution time.

Cross-machine setup, nothing connects. Same reachability rules as every other remote node in this pack: the source instance needs --listen and an open port if it's on a different machine, and you need its actual IP, not 127.0.0.1. If you're bridging your LAN, remember an unauthenticated --listen instance is reachable by anything else on that network - keep it off anything you don't trust.