Bria Fibo Edit Tools

This node is a Swiss army knife hiding behind a required dropdown. Bria's Fibo is a hosted image-editing model, and instead of shipping a separate node per operation, Runware exposes it as one node where the providerSettings.bria.edit dropdown picks which of seven workflows runs: colorize, relight, restore, blend, reseason, sketch_to_image, and expand. Same node, same IMAGE output, radically different jobs.

The two you'll reach for first:

• restore - old photo repair. This is the time machine. Feed it a battered, scratched, faded scan and it cleans it up. If you have a family-photo digitization backlog, this node is why the pack is on your disk.
• relight - re-light an existing image, with lightType (midday, blue hour, moonlight, spotlight, and more) and lightDirection (front, side, bottom, top-down) as companion dropdowns. It's the hosted cousin of the whole IC-Light genre, minus the local install.
• colorize - B&W to color, with color styles from "contemporary color" to "sepia vintage."
• blend, reseason (spring/summer/autumn/winter), sketch_to_image, and expand (outpainting-style) round out the set. expand is the only one that pairs with the outpaint socket.

The edit dropdown is required and there's no "auto" - you pick the operation and the node shows the relevant companion settings for it. positivePrompt and negativePrompt are optional and mostly matter for blend, sketch_to_image, and expand, where you're describing what the edit should add.

What to set

Pick providerSettings.bria.edit, then touch only the settings that belong to it. The providerSettings.bria.* fields that don't apply to your chosen operation are inert - the node sends what you configure, and the API ignores the irrelevant ones. Two always-on defaults to be aware of:

• providerSettings.bria.contentModeration (default true) and promptContentModeration (default true) - Bria scans inputs and prompts. On by default; this is a licensing-conscious commercial provider.
• providerSettings.bria.preserveAlpha - keep an existing alpha channel through the edit. Only matters if your input already has transparency, so leave it off otherwise.

numberResults up to 20 gives you takes per edit. outputFormat (JPG/PNG/WEBP - PNG if you care about alpha) and outputQuality are the usual tail.

How it works

The node sends bria:21@2 as an imageInference task through the Runware SDK with the edit and its settings embedded in providerSettings. The edited image comes back as a native IMAGE. It's cloud-only, pay-per-run, and the title bar logs cost plus content-check results.

Install and gotchas

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

Restart; API key via Settings → "Runware API key", RUNWARE_API_KEY, or runware auth login. Paid, minimum top-up.

The trap people hit: they expect each edit to read like a different node and get lost in the shared settings pile. The rule is - change the dropdown, then ignore every providerSettings field that isn't for that edit. And remember the moderation defaults are on: a prompt that trips Bria's filters returns nothing, and there's no graceful "blocked" message, just an empty result. Check contentModeration toggles before you assume the node is broken.