Get ComfyUI HTTP Folder Path [LP]

Not to be confused with the pack's GetComfyUIFolderPath-LP - that one resolves filesystem paths across roughly thirty model categories (checkpoints, loras, vae, and so on). This node's dropdown only offers three choices: output, temp, and input. That narrow scope, plus the word "HTTP" in the name, is the tell: this isn't about where models live on disk, it's about the three directories ComfyUI itself serves over its own HTTP API.

Why this is a separate node from the folder-path one

ComfyUI exposes a /view endpoint that serves files straight out of those three directories, distinguished by a type query parameter (output, input, or temp). If you're building automation or tooling that talks to a running ComfyUI instance over HTTP - rather than reading files directly off the same disk - you need to reference these three folders the way the API refers to them, not as raw filesystem paths. This node exists to resolve that identifier programmatically instead of hardcoding the string "output" (or whichever) by hand everywhere you need it in your graph.

The inputs and outputs that matter

• folder_name - a dropdown with exactly three choices: output (default), temp, input.
• Output - folder_path, a STRING with the resolved value.

The exact string format returned (a bare folder name, a URL fragment, a query-parameter value) isn't spelled out in the README, so if you're wiring this into a URL-building step for real, verify the output once with a Show Text node before trusting the exact shape in a larger pipeline.

How to install it

ComfyUI Manager: search "ComfyUI Level Pixel" or ComfyUI-LevelPixel, install, restart - updates automatically via Manager's "Update ALL." Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/LevelPixel/ComfyUI-LevelPixel.git

Restart ComfyUI. No models, no extra dependencies.

Common issues & troubleshooting

You wired this in expecting a real filesystem path and got something that doesn't open as a file. That's the point of difference from GetComfyUIFolderPath-LP - this node is scoped to the HTTP-facing identity of these three folders, not a disk path. If you actually need a filesystem path to output, input, or temp, use the general folder-path node instead (its dropdown includes these same three among its full model-folder list).

You expected more than three options. This node deliberately only covers output, temp, and input - the folders ComfyUI's own /view API serves. Anything outside that set (a specific model category, a custom folder) isn't in scope here; that's what GetComfyUIFolderPath-LP is for.

You're building a URL to fetch a generated image and it's not resolving. Remember the /view endpoint also needs filename and typically subfolder alongside type - this node only gives you the type-equivalent piece of that URL, not the whole thing. You'll still need to supply the filename from wherever your workflow generated or saved it.