Image Monitor

This is one of the simplest nodes in SP-Nodes, and also one of the least documented - it's part of the pack's "another nodes" grab-bag rather than one of the features the README shows a screenshot of. Going purely off the schema: one required input, image_path (a string), one output, IMAGE. It loads whatever image lives at the path you give it.

What it's for

The name - "Monitor," not "Load" - is the interesting part. A plain image loader in ComfyUI usually works off a fixed asset already sitting in your inputs folder, picked from a dropdown. ImageMonitor instead takes a raw path string, which is the shape you'd want if the image at that path is expected to change - something outside ComfyUI (a screen capture tool, another app, a folder something else is writing into) keeps updating the file, and you want your graph to pick up whatever's currently there each time you run it, rather than a snapshot baked in at workflow-build time. That's the practical use case the schema points to; the README doesn't spell out the exact watching behavior beyond that, so take "it loads the image at this path when the node runs" as the confirmed part and the "live monitoring" framing as the reasonable inference from the name.

The one input that matters

• image_path - a string path to the image file. Since this is a plain string field rather than a dropdown of known assets, you're responsible for getting the path right - full path, correct file extension, and a location ComfyUI's process actually has read access to.

Output is a single IMAGE, wired wherever a normal LoadImage output would go - into a preview node, a VAE encode, an upscaler, whatever your graph needs an image for.

Installing SP-Nodes

Through ComfyUI Manager: search "SP-Nodes," install, restart ComfyUI. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/bananasss00/ComfyUI-SP-Nodes

Restart after cloning. Nothing about a path-based image loader needs a model download or an extra dependency beyond what ComfyUI already uses to read images.

Where this trips people up

The most likely failure is the plainest one: a wrong or relative path. Since image_path is free text with no validation against a known folder, a typo, a missing file extension, or a path that's relative to the wrong working directory will fail to load rather than silently falling back to something else - double-check it's an absolute path the ComfyUI process can actually see, especially if you're running ComfyUI inside a container or on a remote machine where "the file is right there" on your desktop doesn't mean the server process can reach it.

If you're running this on a hosted ComfyUI instance rather than locally, remember that "a path on my computer" and "a path the server sees" are two different filesystems - this node is built for a local setup where something else on the same machine is dropping files for ComfyUI to pick up, and that assumption doesn't automatically carry over to a remote or containerized deployment.