Mepi Image Size

It does exactly what it says, which is refreshing

Mepi Image Size takes a width and a height, passes them through untouched, and outputs them as Width and Height. That's the node. The source is return (width, height,) - four words of logic. If you've been swimming through packs that wrap every tiny operation in ten configuration options, this is the other end of the spectrum.

Its purpose in life is to be the resolution slot for ComfyMepi, a small mobile frontend for ComfyUI by rhplus0831. The phone UI can't build a graph, so it edits values inside a template workflow and resubmits the JSON - and every Mepi node is a field the frontend writes into. Mepi Image Size is the "how big should this be?" box. The output wires straight into the width and height inputs of an Empty Latent Image node, which sets the canvas your sampler starts from.

What you set

Two inputs, two outputs:

• width (INT) - image width in pixels.
• height (INT) - image height in pixels.
• Width and Height (INT outputs) - wire them to Empty Latent Image.

Nothing else. There are no optional inputs, no presets, no aspect-ratio math hidden anywhere.

Install

Same trivial story as the rest of the pack. Via ComfyUI Manager, Manager → Install Custom Nodes → search "ComfyMepi", or:

cd ComfyUI/custom_nodes
git clone https://github.com/rhplus0831/ComfyMepi

Restart ComfyUI and you're done. No requirements.txt, no pip step, no model files to fetch - the node is pure plumbing over ComfyUI's own libraries.

Worth knowing before you use it

Because this node is a straight pass-through, it doesn't round, snap, or validate anything. Whatever you type goes straight to Empty Latent Image. Some resolution pickers silently nudge you to friendly multiples of 8 or 64; this one won't - if you hand it 833×711, the latent is 833×711, and you're on your own from there.

Also note the honest caveat about the pack: it's a personal project, essentially unknown in the community and lightly maintained. That matters less here than anywhere, since there's nothing to go wrong. If you're on desktop and never use the Mepi mobile UI, you can get the same result with a plain Empty Latent Image and skip this node entirely - it exists so the phone has a consistent knob to turn, not because ComfyUI needed another way to set dimensions.