Nodes/ComfyUI Level Pixel/Get ComfyUI Folder Path [LP]
ComfyUI Node

Get ComfyUI Folder Path [LP]

Resolving a real filesystem path from ComfyUI's model registry

By LevelPixel·Created 2 years ago·Updated 6 months ago· 31
Get ComfyUI Folder Path [LP]
    • folder_path
    folder_namecheckpoints

    This one isn't called out by name in the pack's README prose - it's one of the smaller IO utilities that just does its job quietly. What it does is unambiguous from its schema, though: pick a model category from a dropdown (checkpoints, loras, vae, controlnet, and so on - the same categories ComfyUI itself uses to populate every model-loading dropdown in the app), and it hands you back the real filesystem path for that category as a plain string.

    Why you'd want a path instead of just picking a file

    Most of the time you don't need this - you'd just use a normal checkpoint/LoRA loader with its own dropdown. This node earns its keep in automation workflows that need to read or write files directly, rather than load a model through ComfyUI's own loading machinery. Think a script-like graph that needs to know exactly where your loras folder lives on disk so it can hand that path to a file-listing node, rather than hardcoding something like /workspace/ComfyUI/models/loras by hand - a hardcoded path that breaks the moment you move the workflow to a different machine, a different container, or a different drive letter.

    The inputs and outputs that matter

    • folder_name - a dropdown pulled straight from ComfyUI's own model-folder registry: checkpoints, configs, loras, vae, text_encoders, diffusion_models, clip_vision, style_models, embeddings, diffusers, vae_approx, controlnet, and roughly 19 more categories beyond that.
    • Output - folder_path, a plain STRING of the resolved absolute path.

    A caveat worth knowing

    ComfyUI supports pointing a single model category at more than one folder at once (via extra_model_paths.yaml, if you've set that up - say, checkpoints split across two mounted drives). If your setup does that, don't assume this node hands you back every folder for that category - it's resolving to whichever one ComfyUI treats as primary. If you're building something that depends on getting the exact right path, verify it once against a Show Text node before trusting it inside an automated 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 - it's reading ComfyUI's own internal path registry.

    Common issues & troubleshooting

    The path doesn't match where you expected your models to live. Most likely you've got multiple search paths configured for that category (via extra_model_paths.yaml) and this node resolved to a different one than the folder you were thinking of. Check your ComfyUI path configuration rather than assuming the node is wrong.

    You want to combine this with a file-listing or file-loading node. This node pairs naturally with the pack's GetFilenameByIndexInFolder-LP, which takes a folder path and an index and returns a specific filename from inside it - feed this node's output straight into that one's folder_path input instead of typing an absolute path by hand.

    CategoryLevelPixel/IO

    Inputs (1)

    NameTypeDefaultDescription
    folder_nameCOMBOcheckpoints31 options: checkpoints, configs, loras, vae, text_encoders, diffusion_models, +25

    Outputs (1)

    NameTypeDescription
    folder_pathSTRING