ezXY Assemble Plot

ezXY Assemble Plot is the finishing move of the whole pack - the node that takes everything ezXY Driver, your per-cell image outputs, and String to Label produced, and turns it into one labeled comparison image you'd actually post or save. If you've used Automatic1111's XY plot script or Efficiency Nodes' XY Plot before and wondered what a DIY ComfyUI equivalent looks like, this is the last node in that chain.

How it works

It takes three image inputs: images (your assembled grid of results - the README points at Plot Images as the node that builds this), and x_labels / y_labels, the axis-label strips you build with String to Label. Per the README, this node "works best with ezXY Driver and String to Label" - the intended pipeline is: Driver generates your grid coordinates, your value-picker nodes and sampler produce one image per cell, Plot Images tiles those into a single grid canvas, String to Label renders your axis values as text images, and Assemble Plot lays the labels alongside the grid to produce the final Plot - a labeled image comparable to a spreadsheet with row/column headers.

Inputs and outputs

• images (IMAGE) - the assembled grid of your per-cell outputs.
• x_labels (IMAGE) - label images for the column axis, built with String to Label.
• y_labels (IMAGE) - label images for the row axis, same source.
• Plot - the final combined, labeled image.

Installing ComfyUI_ezXY

ComfyUI Manager: search "ComfyUI_ezXY", install, restart. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/GMapeSplat/ComfyUI_ezXY.git

No models, no heavy dependencies - the whole pack, this node included, is pure image/logic manipulation.

Common issues & troubleshooting

Because this node depends entirely on what you feed it, mismatched dimensions are the number one problem: if your label images (from String to Label) aren't sized or rotated consistently with your grid's actual row/column count, the assembled plot will look wrong rather than error outright - worth checking range from ezXY Driver against how many labels you actually rendered before assuming this node is at fault.

It also carries the same pack-wide risk as every other node here, and this one's arguably the most exposed to it since it's downstream of everything else: the README opens with "Does not work with current version of Comfyui," and there's a documented case of the pack going unmaintained for a stretch - a 2025 GitHub issue shows a user asking to fork a single node out of the repo because it had broken and stayed that way. If your whole plot pipeline works right up until this final assembly step and then fails, check the repo's issues first; this is exactly the kind of "final node that stopped working" complaint others have hit too.

One redditor summed up the whole DIY approach fairly: compared to fighting Efficiency Nodes' XY Plot, ezXY is "not sooo simple," but it worked for them once they'd wired it the way the pack's sample workflows show - worth opening those examples on GitHub rather than reinventing the pipeline from the node names alone.