Beeble Download Image Test

The last step of every Beeble image job, in isolation: Beeble Download Image Test takes a render URL, downloads the bytes, loads them as a normal ComfyUI IMAGE tensor, and hands you a previewable, saveable image. It's the mirror image of the Upload test node - pixels went up, pixels come down - and like the rest of these test nodes, it exists so you can verify this one step before trusting the full pipeline.

You'll reach for it in the manual debug chain: Start Image Generation Test → Wait Job Test → this node, wired with render_uri_or_url from Wait into render_url here, and then a Preview or Save node on the image output. If that chain works, the upload, generation, and download plumbing are all sound, and any remaining problems live in prompt or mask territory.

How it works

It downloads render_url to a temp PNG (with the pack's usual two-retry network handling), reads it back as a float tensor shaped [1, H, W, C] - ComfyUI's standard IMAGE - and returns it. The temp file is cleaned up after, so there's no disk litter to manage.

One trap worth knowing: the input is a URL, and the code only accepts http/https schemes. The beeble_uri you got from the Upload node is not a URL - it's an internal asset reference. Don't paste it here. What belongs here is the render_uri_or_url from the Wait node, which is Beeble's actual render URL.

Inputs and outputs

• render_url (STRING) - required. An http(s) URL to the finished render, normally from Wait Job Test.
• image (IMAGE) - the downloaded render, ready for PreviewImage / SaveImage / anything downstream.
• debug_json (STRING) - the URL and the local file path it was written to.

Installing

cd ComfyUI/custom_nodes
git clone https://github.com/albert999-pixel/comfyui-beeble-switchx.git

Or search Beeble in ComfyUI Manager, restart, and set BEEBLE_API_KEY via .env, an env var, or ComfyUI Desktop's env-variables panel. No extra dependencies - the pack ships with an empty requirements.txt and no model files.

Common issues

• "Unsupported download source … Expected an http(s) URL" - you pasted a Beeble URI, not a URL. Use the Wait node's render output.
• HTTP 4xx on download - the render URL expired or never existed. Beeble render links may be time-limited; re-run the job or grab a fresh URL.
• Network error after retries - transient connection trouble; retried twice and gave up. Check your connection before blaming the node.
• Image looks wrong - remember the pack's MVP habit: single images only, first frame of any batch. For a single render that's a non-issue, but keep it in mind if you're chaining batch outputs.