Flux Kontext Resolution

This is a plumbing node, and it's fine that it's a plumbing node. Flux Kontext Resolution is a dropdown of resolutions - things like 672x1568 • 3:7 (~1.05MP) (custom) - that hands you the matching width and height as two INT outputs. No model, no network, no math on your part. You pick the aspect ratio, it gives you the numbers.

Why does that deserve a node? Because Flux Kontext (BFL's 12B instruction editor) is a picky eater. It consumes reference images in-context, and its native training resolutions are a specific set of shapes, not "whatever your base image happens to be." When you're wiring up an ETUR workflow that uses Kontext as the refiner or reference path, you want your EmptyLatentImage or your resize to land on a resolution the model actually likes. This node encodes that list so you don't have to keep a wiki tab open.

How it works

About as deep as a light switch. The node ships with a hardcoded list of Kontext-friendly resolutions, formats each into a label like the one above, and when you pick one it splits the label back into width and height integers:

• resolution (dropdown) - pick the aspect ratio you want. The label tells you the exact pixel dimensions and the approximate megapixels, so "3:7" being 672x1568 is right there in the name.
• width / height (INT outputs) - wire these into an EmptyLatentImage (via an INT→LATENT path), an ImageScale, or anything else that takes plain integers.

There are no other inputs, no optional hooks, no hidden state. It's the kind of node that looks trivial until you've hand-typed 1568 for the fourth time and fat-fingered it.

Installing it

Part of the TBG ETUR pack. ComfyUI Manager → search "TBG" → install TBG_Enhanced Tiled Upscaler & Refiner FLUX PRO, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/Ltamann/ComfyUI-TBG-ETUR
cd ComfyUI-TBG-ETUR
pip install -r requirements.txt

You're installing the whole pack (with its chunky requirements: opencv-contrib, triton, transformers, bitsandbytes…) to use a dropdown. If that bothers you, know that this node is the "takeaway" version of a resolution list that ETUR's refiner used internally - the pack's whole 1.2.x design is extracting small useful pieces like this into standalone nodes. You're not doing it wrong; this is the intended way to get it.

Notes

Watch the label's (custom) tag. Some of the listed resolutions are official Kontext native sizes, some are ETUR's own hand-tuned picks - both are fine, but the custom ones are tuned for the tiled refiner, not for text-to-image generation. If you're using this in a straight Kontext edit pass rather than an ETUR pipeline, prefer the official aspect ratios.

Also worth knowing: the dropdown defaults to the first entry, so if you're not paying attention you'll generate at 672x1568 thinking you set 16:9. Read the label, then pick. And since Kontext is a character-consistency workhorse in the Flux 1 era (and the license is what pushed a lot of people to Qwen-Image-Edit), a resolution helper like this is the boring-but-necessary glue those workflows are built on.