Tools_ImageEncodeDecodeTest

Straight answer first, since this one's easy to misjudge from the name alone: this isn't a node you build a workflow around. It lives in the pack's images_test category alongside one sibling, and both are internal QA utilities - the kind of thing a team ships bundled with a big node pack for their own debugging, not something meant to be the centerpiece of your graph. If you landed here expecting an image-editing effect, this isn't it.

What it actually does

Almost the entire BizyAir pack works by shipping your images off to a cloud backend and getting results back - every generation, every matting call, every API pass-through moves pixels over the network. That transport has to encode and decode images somewhere along the way, and this node is a way to test that round trip in isolation: feed it an image, it encodes and decodes it through whatever codec BizyAir uses for cloud transport, and hands you back the result. Nothing generative happens here - the interesting question this node answers is "did the trip through the wire degrade my image," separate from whatever a downstream generation model might have done.

That's genuinely useful if you're ever debugging output that looks softer or more compressed than you'd expect from a BizyAir cloud node. Run your source image through this one first, with lossless toggled both ways, and you can tell whether quality loss is happening in transport before you go blaming the model.

Inputs and outputs that matter

• image - the image to round-trip.
• lossless (optional, default false) - the obvious read is a lossy-vs-lossless encode for the transport step: false gets you something smaller and faster, presumably at some quality cost; true should preserve the source exactly. The pack doesn't spell out which specific codec is behind either setting, so treat the practical effect - not the exact mechanism - as what you can verify by comparing outputs yourself.

Output is a single IMAGE, the round-tripped result.

How to install it

• ComfyUI Manager - search "BizyAir", install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/siliconflow/BizyAir.git, restart.
• Comfy CLI - comfy node install bizyair.

This particular node doesn't need an API key to load into your node list, but it's part of a pack whose real generative nodes do - set one up via the in-app login prompt or bizyair.siliconflow.cn if you're using the pack for anything beyond this diagnostic.

Common issues & troubleshooting

You're not sure why you'd ever use this. Fair - most people won't. It earns its keep specifically when a BizyAir cloud node's output looks visibly worse than you expected, and you want to isolate whether the transport or the model is responsible. Outside of that debugging scenario, there's no reason to leave it in a working graph.

Output with lossless on still looks slightly different from the input. Some codecs still do minor recompression even in a "lossless" mode depending on color space or bit depth handling. If you're chasing pixel-perfect round trips, compare histograms rather than eyeballing it.

The whole BizyAir pack showed up in your custom nodes and you're not sure why. Older versions of ComfyUI Manager occasionally mis-resolved a missing node from an unrelated workflow onto this pack, which is where a handful of "is this malware" threads about it online come from. It's a legitimate SiliconFlow pack, not malicious - safe to keep if you're using any of its real nodes, safe to remove through the Manager if you're not.