Image Bounds to Console

This is a debug tap, not an effect. WAS Node Suite has a whole family of "X to Console" nodes for exactly this purpose - Dictionary to Console is the documented one, printing a dictionary input straight to the terminal so you can see what's actually flowing through your graph - and Image Bounds to Console does the same job for bounds data specifically: it takes the rectangle produced by Image Bounds or Inset Image Bounds and prints those coordinates to the console running ComfyUI, so you can confirm the box is where you think it is before it feeds into a crop.

Why this is worth having

Bounds data is invisible on the canvas. You can wire Image Bounds into Inset Image Bounds into Bounded Image Crop and never actually see a single number - you just see whether the final crop looks right or wrong, with no way to tell why it's wrong. Drop this node into that chain (it should pass the bounds through unmodified, the same way debug-print nodes typically do, so you're not rerouting anything to insert it) and suddenly you can see the box's coordinates directly: did the mask produce the region you expected, did the inset pad it the direction you meant, is the box even landing inside the image bounds at all. It turns a silent chain of geometry into something you can actually verify.

Where to look for the output

The one thing that trips people up with every "to Console" node in ComfyUI, not just this one: it prints to the terminal window running ComfyUI, not anywhere in the browser UI. If you're staring at the web page waiting for numbers to show up, you'll wait forever - alt-tab to the actual process console instead.

Installing it

Comes bundled with the full WAS Node Suite:

• ComfyUI Manager - search "WAS Node Suite", install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/WASasquatch/was-node-suite-comfyui, install requirements.txt against your ComfyUI Python (portable: python_embeded\python.exe -s -m pip install -r requirements.txt), restart.

No models, no heavy dependency for this one - it's a plain debug print.

Common issues & troubleshooting

A quick honest note: this exact node isn't listed by name in WAS's own README (the closest documented sibling is Dictionary to Console), so I'm describing its job from the naming convention and the pattern the rest of the "to Console" family follows, not a line I can point to. If its behavior differs from what's above once it's on your canvas, trust what you see over this description.

Beyond that, the whole-pack caveat still applies: WAS Node Suite has had no active development since December 2023, and the recurring failure mode is the entire suite refusing to import after a ComfyUI core update - usually a stale pinned dependency, not this node specifically. If nothing in the suite loads, reinstall requirements.txt inside the right Python environment (or run the bundled install.bat) and restart before assuming a debug node this simple is somehow the problem.