Bria Text2Image HD

Bria Text2Image HD is the quality tier of the same trick as its Fast sibling: an official BRIA pack node that doesn't generate anything on your machine. You give it a prompt and an API token, it calls Bria's hosted text-to-image/hd/2.2 endpoint, and it returns a finished IMAGE tensor. Your GPU naps. Your wallet, however, stays awake - this is a paid hosted API, and HD runs cost more than Fast runs because it's doing more work on Bria's side.

If you're wondering why a local-generation tool ships a node that does nothing locally, that's the "Partner/API nodes" wave ComfyUI added in v0.25 - Bria, Krea, Runway, Gemini all got in-core or popular wrappers. The use case is companies and freelancers who need a defensible commercial license, or anyone on hardware that can't run a serious checkpoint. Bria's models are trained on 100% licensed data with an eye to avoiding copyrighted characters and trademarks, which is the actual reason most people get told "use Bria" at work.

The difference from Fast

Where Fast is distilled to 8 default steps for speed, HD defaults to 30 steps, and it exposes the knobs Fast hides. Concretely, the inputs that matter:

• prompt and negative_prompt - yes, HD actually has a negative prompt; Fast doesn't. Use it for the usual suspects ("blurry, low quality, watermark") or leave it empty.
• steps_num (default 30) and text_guidance_scale (default 5) - the CFG-analogue. This is the closest you get to "sampler settings" in an API node; dial guidance up if it's not obeying the prompt.
• medium - photography, art, or none. The pick that does the most work per click; photography biases toward a photoreal look, art toward illustration. It only gets sent to the API when it isn't none.
• aspect_ratio - same nine ratios as Fast (1:1 through 16:9), default 4:3.
• seed (-1 = random), prompt_enhancement (1 = let Bria rewrite your prompt), content_moderation (1 = safety filter on output).

Only api_key is required, and it's worth repeating the trap: the field is a placeholder until you paste a real token, and the whole pack refuses to run on the placeholder string.

The output is output_image - a standard IMAGE tensor. Save it, preview it, feed it into a VAE or an upscaler, it behaves exactly like a locally generated image from this point on.

Installing and running

Identical to every node in this pack - ComfyUI Manager, search "BRIA API":

cd path_to_comfyui/custom_nodes
git clone https://github.com/Bria-AI/ComfyUI-BRIA-API

Restart, then grab a token from platform.bria.ai. No model downloads, no requirements beyond requests and the torch/PIL stack ComfyUI already has. The node is synchronous: it POSTs, waits, downloads the resulting image, and hands it back.

The honest caveats

Three things before you build a whole workflow on this. First, it's Bria's legacy V1 pipeline - the README points new projects at the V2 "FIBO" nodes for the real quality jump, and HD is mostly the "best of V1" option. Second, quality expectations: the community thread that kicked off "BRIA from ComfyUI" (r/comfyui, 2024) featured someone forced onto Bria at work complaining that the V1 output needed "lots of upscaling" to be usable. That's a generation quality complaint, not a node bug - you can't prompt your way out of the model's ceiling, though the medium and guidance knobs help. Third, every call is billable, and HD being heavier means it's the pricier of the two text-to-image nodes - don't brute-force 200 variations through it.

Verdict: reach for HD when you need the licensed, commercial-safe image and Fast's 8-step shortcut isn't cutting it. It's the "slow but better" button on the same rented machine - and for a corporate deliverable, that's often exactly the right tool.