Nodes/BB Downloader/Download Summary Parser
ComfyUI Node

Download Summary Parser

The translator that turns download logs into text you can read

By codewithbernard·Created 18 days ago·Updated 18 days ago· 0
Download Summary Parser
  • summary
  • text

This is the pack's tiny translator, and honestly, it exists because of a quirk. The Downloader node outputs a custom type called DOWNLOAD_SUMMARY - a list only the pack itself understands. Nothing else in ComfyUI can read it. Download Summary Parser converts that opaque list into a plain STRING, which means it can finally meet a text display node and show you what actually happened.

It's a one-trick node, but the trick is useful once you're chaining a few Downloaders. You wire several of them together by feeding each one's summary output into the next one's summary input - every Downloader appends its own line to the shared list. Without the parser, that list is invisible to the rest of your graph. With it, you get a readable log of every file the run touched.

How it works. The mechanism is nearly trivial: it iterates the summary list and joins each entry onto its own line prefixed with a dash. Each entry is a string the Downloader wrote - either downloaded <url> to <path> or <path> present. So the rendered output reads like a bullet list of what got fetched and what was already there. That's the whole node: one input, one output, no settings to fiddle with.

Inputs and outputs. The only input is summary (DOWNLOAD_SUMMARY). The only output is text (STRING), which you feed to any text sink - Show Text (pythongosssss), a display node, or anything that takes a string. It's not a "display text" node itself; it only prepares the text.

Where people get burned. A couple of small things:

  • The output is purely cosmetic. The parser changes nothing about the downloads; it just formats the record. If a Downloader failed, the error shows up in the console, not here.
  • If nothing has downloaded yet, the output is essentially an empty newline. Don't wire it into something that parses the text - it's a log for human eyes, not a data source.
  • The list grows with every Downloader that shares it, and there's no per-node attribution beyond the path embedded in each line. If you have twenty downloaders, you get twenty lines; there's no filtering.

Installing. Same pack as the Downloader - it's stavsap/comfyui-downloader. In ComfyUI Manager, search "comfyui-downloader"; or:

cd ComfyUI/custom_nodes
git clone https://github.com/stavsap/comfyui-downloader

Restart and you're done. The pack's only dependencies are requests and tqdm, so there's nothing heavy lurking behind this node. It ships in the same lightweight one-person utility pack as its siblings, and like the rest of that pack, it's worth a skim of the source before you rely on it - but for a formatting helper, there's very little to go wrong.

The verdict: if you're only using one Downloader, you can skip this node entirely and just watch the console. Add it when you've chained several downloads and want a single readable summary at the end of the run - that's the one job it does well.

CategoryDownloader

Inputs (1)

NameTypeDefaultDescription
summaryDOWNLOAD_SUMMARY

Outputs (1)

NameTypeDescription
textSTRING