Browser Download

If you run ComfyUI on your own desktop, this node is a mild convenience. If you run it on a rented GPU box, a server in the closet, or any machine where output/ isn't a folder you can reach from your chair, BrowserDownload is a small quality-of-life miracle: it saves your images to the server's output directory and triggers a browser download straight to your local Downloads folder. Remote or headless ComfyUI setups are exactly what its docstring names, and it's the correct answer to "how do I get this render onto my laptop without SCPing a folder."

It's an output node - the kind that always runs and anchors the graph. You wire images in, and on execution it writes the batch (with ComfyUI's standard metadata embedding, same as SaveImage) and pushes the files at your browser. The filename follows filename_prefix, which is not a literal string: it supports ComfyUI's format templates, so %date:yyyy-MM-dd% gets interpolated - the same templating convention the SaveImage node uses.

The knobs that matter

• filename_prefix - default download. Use a date token or a project name so you don't get six identical download_00001_.png files. The tooltip calls out %date:yyyy-MM-dd% as the example.
• format - png, jpg, or webp. The tooltip's framing is the useful one: "JPG/WebP are smaller for faster download." If you're pulling results over a slow connection or a metered VPN, webp is dramatically faster to transfer than png for the same content.
• quality - 1–100, default 95, applied to JPG/WebP and ignored for PNG. Lower it for preview-grade pulls; keep it high if you're grabbing the actual deliverable.

There are no outputs - it's a sink, like SaveImage. Everything it does is write-and-push.

Gotchas

The realistic ones:

• It writes to the server's output folder too. This isn't a "download only" node; it saves and downloads. If your remote box's disk is precious, that's double storage. There's no setting to skip the save, so factor it in.
• The download is browser-mediated. It relies on the browser session that's attached to the workflow. If you're hitting ComfyUI purely through its API with no browser open, the save half still happens but there's no browser to receive the push - you'll have to pull the file from output/ the old way.
• Metadata survives. Since it writes PNG with ComfyUI's embedded workflow chunks (see the image I/O notes in the KB), the file that lands in your Downloads still carries the graph - drag it back onto the canvas later and the whole pipeline reconstructs. That's a feature, but only if you don't re-save the PNG through a tool that strips chunks.

It installs with TrentNodes: ComfyUI Manager (search "Trent Nodes"), or

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

No models, no downloads, no extra deps beyond the pack core. For anyone living on a headless render box it quietly removes the most annoying two minutes of every session.