Crop Image Settings (JPS)

The Settings half of a Settings/Pipe pair, built for workflows juggling two images at once - a "source" and a "support" image, which shows up as a recurring pattern across this pack's ControlNet Settings nodes (they let you choose the pose/edge/depth reference from either one). This node holds the crop configuration for both images in a single wire, so you set it once and route the actual values out downstream with the matching Crop Image Pipe (JPS) node rather than dragging five separate connections across your graph.

The inputs that matter

• source_crop_pos and support_crop_pos - center, top, bottom, left, or right, one for each image. Same idea as a manual crop-to-square anchor: pick which part of each frame survives if it's not already square.
• source_crop_offset and support_crop_offset (-2048 to 2048, default 0) - fine-tune each anchor by a pixel amount, independently for the two images. Handy when "top" is close but not quite right for one image and needs a nudge, without affecting the other.
• crop_intpol - lanczos, nearest, bilinear, bicubic, area, or nearest-exact. A single interpolation method shared by both crops. Lanczos is the safe default for most downscaling; nearest is what you'd want if you're cropping something like a segmentation map where blending pixel values would corrupt the labels.

Output: cropimage_settings, typed BASIC_PIPE - worth knowing this is JPS's own reused label (a plain bundle under the hood, not Impact Pack's object of the same type name), and it only makes sense wired into the matching Pipe node.

Installing it

Through ComfyUI Manager, search JPS Custom Nodes for ComfyUI. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/JPS-GER/ComfyUI_JPS-Nodes.git

Restart ComfyUI afterward. Remove any prior install of the pack first - the author's own README flags this as a real source of conflicts. Pure logic node, no models to fetch.

Where people get tripped up

This node holds settings for two images and doesn't actually crop anything itself - the crop offsets and positions only take effect once you've pulled them back out with Crop Image Pipe (JPS) and wired them into an actual crop node downstream. If you only need to crop one image, this is more machinery than you need; Crop Image Square (JPS) does a single-image square crop directly and is the simpler tool for that job. Reach for this pair specifically when you're already working with a source/support image setup elsewhere in the workflow (the ControlNet Settings nodes in this pack use exactly that pattern) and want the crop config to live alongside it in one place.

Note also that this node crops to whatever aspect ratio the anchor position implies rather than forcing a square, unlike Crop Image Square - it's a general positioning crop, not specifically built for CLIP Vision-style square inputs. If square-and-resized is what you actually need for an IP-Adapter or Revision reference, that's the other node's job.