Ideogram 4 reports alpha-channel bugs and INT errors in ComfyUI

• Ideogram's own product pages say Ideogram 4.0 ships as open weights with editable outputs, while Ideogram's transparency docs say native transparency is supported where available, but Adam_alone_'s Reddit post shows a local ComfyUI run baking the checkerboard into the image instead of returning a real alpha channel.
• In the same Reddit thread, the Stable Diffusion discussion surfaces the main uncertainty fast: commenters could not tell whether transparency is missing in the local model, missing in ComfyUI's implementation, or gated behind a different workflow.
• ComfyUI's Ideogram 4 pull request confirms the app only added Ideogram 4 support on June 3, and MasterYard7541's error report shows at least one prompt-builder workflow already tripping over an INT conversion failure.
• The rough edges are broader than alpha handling. nomadoor's Node 2.0 export post says one workflow export extension needed a Chromium-only workaround for ComfyUI's new UI, which is the kind of compatibility debt that tends to surface right after a new model lands.

Ideogram's own site says you can generate and edit transparent images, and the official docs frame that as a native workflow. On Reddit, though, users were already posting a baked checkerboard bug, a separate INT conversion error, and a handful of Node 2.0 compatibility questions within hours of the local ComfyUI rollout.

Adam_alone_'s post is the clearest symptom report: the prompt explicitly asked for a transparent background, but the local ComfyUI output came back with a gray-and-white checkerboard rendered into the image.

That clashes with Ideogram's public messaging. The Ideogram 4.0 model page says the release is built for design workflows with editable outputs, while Ideogram's transparent image editor page says creators could already generate transparent backgrounds before the new editing flow shipped. The docs add one caveat, saying native transparency is available "where available," which leaves room for product-surface gaps like local ComfyUI support.

A separate Reddit report from MasterYard7541's Stable Diffusion post says an Ideogram 4 Prompt Builder workflow failed with Failed to convert an input value to a INT value even after updating ComfyUI and KJNodes. ComfyUI's Ideogram 4 support PR shows how fresh the integration is, with new scheduler, guider, and conditioning nodes landing less than a week earlier.

There is not enough evidence yet to pin that failure on ComfyUI core, KJNodes, or one broken community workflow. What is clear is that early local Ideogram 4 use is already splitting into two bug classes: image output quirks and node-graph type errors.

The ComfyUI friction is not limited to Ideogram-specific nodes. In nomadoor's ComfyUI post, the developer behind ComfyUI-Workflow-Image-Export said Node 2.0 was hard enough to capture that the extension switched to Chromium screen-capture APIs, which means the experimental support only works in Chromium-based browsers and still drops some legacy options.

That lines up with StacksGrinder's Node 2.0 question, which asks whether older workflow breakage and missing custom nodes have actually settled down. For people sharing or archiving local Ideogram 4 setups, even the screenshot-and-export tooling is still catching up.