LoRA Downloader

If your loras folder has grown into a pile of cryptically-named files with no idea what half of them actually do, LoRA Downloader is the batch fix. It scans a subdirectory of your loras folder and, for each file it finds, pulls down metadata and example images from an online model repository. It's part of silveroxides' ComfyUI-ModelUtils - the odd one out in a pack that's mostly about editing and merging files locally, since this node reaches out to the network instead.

What it's actually talking to. The node's own inputs give it away even though the pack doesn't name the source outright: an api_key field for "the model repository," and an nsfw_level filter - that combination is the exact shape of a CivitAI metadata puller, the same pattern you'll recognize from various "Civitai Helper" extensions across different UIs. Treat that as a strong inference rather than a documented fact, but it's the sensible assumption going in.

Inputs that matter. subdirectory (default /) picks which folder under your loras directory to scan - a dropdown built from what's actually there. recursive (on by default) decides whether it walks subfolders too. nsfw_level (default "All") filters what gets pulled based on the content rating in the repository's own metadata. max_examples (0-100, default 0) caps how many preview images get downloaded per LoRA - note the default of 0, which likely means "none" unless you raise it. threads (1-32, default 4) controls concurrency. api_key is required to actually talk to the repository - leave it blank and you're likely to hit rate limits or get nothing back at all. The single output is status, a summary string; check your ComfyUI console for the real per-file detail since one string can't carry much.

Installing it. ComfyUI Manager, search "Model Utility Toolkit" - or cd ComfyUI/custom_nodes && git clone https://github.com/silveroxides/ComfyUI-ModelUtils and restart. The README doesn't mention this node's networking dependencies specifically, but functionally it needs outbound internet access and a valid API key to do anything useful.

How to not get rate-limited on your first run. This node is marked as a workflow output, so it runs standalone the moment you hit Queue - no need to wire anything downstream. That also means it's easy to accidentally point it at a huge, deeply-nested loras folder with recursive on, threads maxed at 32, and max_examples set high, and hammer whatever API it's hitting all at once. Start small: point subdirectory at a folder with a handful of files, keep threads low, and confirm it's actually finding and matching your LoRAs before you scale up to your whole collection.

What to expect it can't do. It scans files you already have and enriches them with metadata pulled by whatever matching logic the repository's API uses - it's not a search or discovery tool, and it won't tell you anything about a LoRA the repository itself doesn't know (an obscure or removed listing, a locally-trained file with no public counterpart, anything uploaded somewhere other than the source this node hits). If a specific LoRA comes back empty, that's very likely the repository not having a match, not a bug in the node. And if you're pulling metadata for anything outside your standard ComfyUI models folder layout - a separate drive, a download staging folder - this pack's Manual Path Downloader is the sibling node built for exactly that, since this one only scans inside your configured loras directory.